Domain-based Message Authentication, Reporting, and Conformance (DMARC): Revision history

Diff selection: Mark the radio buttons of the revisions to compare and hit enter or the button at the bottom.
Legend: (cur) = difference with latest revision, (prev) = difference with preceding revision, m = minor edit.

curprev 23:3523:35, 11 June 2024‎ Sebastian talk contribs‎ 7,760 bytes +100‎ No edit summary

curprev 14:0414:04, 3 September 2023‎ Sebastian talk contribs‎ 7,660 bytes +171‎ No edit summary

curprev 23:4523:45, 2 September 2023‎ Sebastian talk contribs‎ 7,489 bytes +22‎ No edit summary
curprev 23:1323:13, 2 September 2023‎ Sebastian talk contribs‎ 7,467 bytes +16‎ No edit summary
curprev 23:0323:03, 2 September 2023‎ Sebastian talk contribs‎ 7,451 bytes +22‎ No edit summary

curprev 00:2900:29, 9 June 2023‎ Sebastian talk contribs‎ 5,942 bytes −48‎ No edit summary
curprev 00:2400:24, 9 June 2023‎ Sebastian talk contribs‎ 5,990 bytes +812‎ No edit summary
curprev 00:0900:09, 9 June 2023‎ Sebastian talk contribs‎ 5,178 bytes +3,016‎ No edit summary

curprev 21:4521:45, 8 June 2023‎ Sebastian talk contribs‎ 2,162 bytes +28‎ No edit summary
curprev 21:0421:04, 8 June 2023‎ Sebastian talk contribs‎ 2,134 bytes +2,134‎ Created page with "A '''DMARC record''' is a '''DNS TXT''' record for a '''subdomain''' named '''_dmarc''' on any senderdomain. DMARC records can be placed on the organisational domain as well as on subdomains. A subdomain that has no DMARC record inherits its DMARC record from the organisational domain. It is recommended to place a DMARC record on every organisational domain. Example: <pre> # host -t txt _dmarc.senderdomain.TLD _dmarc.senderdomain.TLD descriptive text "v=DMARC1; p=reje..."

Domain-based Message Authentication, Reporting, and Conformance (DMARC): Revision history

7 October 2024

11 June 2024

3 September 2023

2 September 2023

31 August 2023

30 August 2023

9 June 2023

8 June 2023

Navigation menu

Search