diff --git a/DANE-for-SMTP-how-to.md b/DANE-for-SMTP-how-to.md index 0591c7f..d78f147 100644 --- a/DANE-for-SMTP-how-to.md +++ b/DANE-for-SMTP-how-to.md @@ -1,3 +1,5 @@ + + # DANE for SMTP how-to This how-to is created by the Dutch Internet Standards Platform (the organization behind [Internet.nl](https://internet.nl)) in cooperation with industry experts (hosters and vendors) and is meant to provide practical information and guidance on implementing DANE for SMTP. diff --git a/DKIM-how-to.md b/DKIM-how-to.md index 23952da..c994b21 100644 --- a/DKIM-how-to.md +++ b/DKIM-how-to.md @@ -1,4 +1,9 @@ -- [Introduction](#introduction) + + +# DKIM how-to +This how-to is created by the Dutch Internet Standards Platform (the organization behind [internet.nl](https://internet.nl)) and is meant to provide practical information and guidance on implementing DKIM. + +# Table of contents - [What is DKIM?](#what-is-dkim-) - [Why use DKIM?](#why-use-dkim-) - [Tips, tricks and notices for implementation](#tips--tricks-and-notices-for-implementation) @@ -20,9 +25,6 @@ Table of contents generated with markdown-toc -# Introduction -This how-to is created by the Dutch Internet Standards Platform (the organization behind [internet.nl](https://internet.nl)) and is meant to provide practical information and guidance on implementing DKIM. - # What is DKIM? DKIM stands for **D**omain**K**eys **I**dentified **M**ail and is described in [RFC 6376](https://tools.ietf.org/html/rfc6376) with updates in [RFC 8301](https://tools.ietf.org/html/rfc8301) and [RFC 8463](https://tools.ietf.org/html/rfc8463). It is meant to provide the owner of a domain with the means to claim that a message has actually been send by the domain's e-mail server and should therefore be considered legitimate. It works by signing every individual e-mail message with a specific key (private key), so that the receiving party can use a corresponding key (public key) published in the sending domain's DNS record to validate the e-mail authenticity and to check whether the e-mail has not been tampered with. diff --git a/DMARC-how-to.md b/DMARC-how-to.md index 923f101..7143dab 100644 --- a/DMARC-how-to.md +++ b/DMARC-how-to.md @@ -1,5 +1,9 @@ + + +# DMARC how-to +This how-to is created by the Dutch Internet Standards Platform (the organization behind [internet.nl](https://internet.nl)) and is meant to provide practical information and guidance on implementing DMARC. + # Table of contents -- [Introduction](#introduction) - [What is DMARC?](#what-is-dmarc-) - [Why use DMARC?](#why-use-dmarc-) - [Tips, tricks and notices for implementation](#tips--tricks-and-notices-for-implementation) @@ -16,9 +20,6 @@ Table of contents generated with markdown-toc -# Introduction -This how-to is created by the Dutch Internet Standards Platform (the organization behind [internet.nl](https://internet.nl)) and is meant to provide practical information and guidance on implementing DMARC. - # What is DMARC? DMARC is short for **D**omain based **M**essage **A**uthentication, **R**eporting and **C**onformance and is described in [RFC 7489](https://tools.ietf.org/html/rfc7489). With DMARC the owner of a domain can, by means of a DNS record, publish a policy that states how to handle e-mail (deliver, quarantine, reject) which is not properly authenticated using SPF and/or DKIM. Because DMARC depends on the security of DNS, the use of DNSSEC is highly recommended. diff --git a/SPF-how-to.md b/SPF-how-to.md index 6958749..20c6be5 100644 --- a/SPF-how-to.md +++ b/SPF-how-to.md @@ -1,5 +1,9 @@ + + +# SPF how-to +This how-to is created by the Dutch Internet Standards Platform (the organization behind [internet.nl](https://internet.nl)) and is meant to provide practical information and guidance on implementing SPF. + # Table of contents -- [Introduction](#introduction) - [What is SPF?](#what-is-spf-) - [Why use SPF?](#why-use-spf-) - [Tips, tricks and notices for implementation](#tips--tricks-and-notices-for-implementation) @@ -14,10 +18,6 @@ Table of contents generated with markdown-toc - -# Introduction -This how-to is created by the Dutch Internet Standards Platform (the organization behind [internet.nl](https://internet.nl)) and is meant to provide practical information and guidance on implementing SPF. - # What is SPF? SPF is short for "**S**ender **P**olicy **F**ramework" and is described in [RFC 7208](https://tools.ietf.org/html/rfc7208). It offers domain owners that use their domains for sending e-mail, the possibility to use the DNSSEC infrastructure to publish which hosts (mail servers) are authorized to use their domain names in the "MAIL FROM" and "HELO" identities. So basically SPF is a whitelist which lists all servers that are allowed to send e-mail on behalf of a specific domain. The receiving mail server may use the information (a SPF record) published in the DNS zone of a specific mail sending domain. diff --git a/parked-domain-how-to.md b/parked-domain-how-to.md index 1d42a95..e4cc283 100644 --- a/parked-domain-how-to.md +++ b/parked-domain-how-to.md @@ -1,4 +1,9 @@ -- [Introduction](#introduction) + + +# Introduction +This how-to is created by the Dutch Internet Standards Platform (the organization behind [internet.nl](https://internet.nl)) and is meant to provide practical information and guidance on explicitly configuring a parked domain not to use e-mail. + +# Table of contents - [What is a parked domain?](#what-is-a-parked-domain-) - [Domain without e-mail](#domain-without-e-mail) * [Null MX](#null-mx) @@ -9,9 +14,6 @@ Table of contents generated with markdown-toc -# Introduction -This how-to is created by the Dutch Internet Standards Platform (the organization behind [internet.nl](https://internet.nl)) and is meant to provide practical information and guidance on explicitly configuring a parked domain not to use e-mail. - # What is a parked domain? [Domain parking](https://en.wikipedia.org/wiki/Domain_parking) is the registration of an Internet domain name without that domain being associated with any services such as e-mail or a website.