Apa itu DMARC?
1 min read
Apa itu DMARC?
1 min read
Domain-based Message Authentication, Reporting, and Conformance, atau DMARC, adalah standar teknis yang membantu melindungi pengirim dan penerima email dari spam, penipuan, dan phishing.
Business in a box.
Temukan solusi kami.
Bicaralah kepada tim penjualan kami
Memahami DMARC
Domain-based Message Authentication, Reporting, and Conformance, or DMARC, is a technical standard that helps protect email senders and recipients from spam, spoofing, and phishing. DMARC allows an organization to publish a policy that defines its email authentication practices and provides instructions to receiving mail servers for how to enforce them. In this edition of “DMARC Explained” you’ll learn what DMARC is and how it works.
Specifically, DMARC establishes a method for a domain owner to:
Publish its email authentication practices
State what actions should be taken on mail that fails authentication checks
Enable reporting of these actions taken on mail claiming to be from its domain
DMARC itself is not itself an email authentication protocol, but it builds on key authentication standards SPF and DKIM. With them, it supplements SMTP, the basic protocol used to send email, because SMTP does not itself include any mechanisms for implementing or defining policies for email authentication.
Domain-based Message Authentication, Reporting, and Conformance, or DMARC, is a technical standard that helps protect email senders and recipients from spam, spoofing, and phishing. DMARC allows an organization to publish a policy that defines its email authentication practices and provides instructions to receiving mail servers for how to enforce them. In this edition of “DMARC Explained” you’ll learn what DMARC is and how it works.
Specifically, DMARC establishes a method for a domain owner to:
Publish its email authentication practices
State what actions should be taken on mail that fails authentication checks
Enable reporting of these actions taken on mail claiming to be from its domain
DMARC itself is not itself an email authentication protocol, but it builds on key authentication standards SPF and DKIM. With them, it supplements SMTP, the basic protocol used to send email, because SMTP does not itself include any mechanisms for implementing or defining policies for email authentication.
Domain-based Message Authentication, Reporting, and Conformance, or DMARC, is a technical standard that helps protect email senders and recipients from spam, spoofing, and phishing. DMARC allows an organization to publish a policy that defines its email authentication practices and provides instructions to receiving mail servers for how to enforce them. In this edition of “DMARC Explained” you’ll learn what DMARC is and how it works.
Specifically, DMARC establishes a method for a domain owner to:
Publish its email authentication practices
State what actions should be taken on mail that fails authentication checks
Enable reporting of these actions taken on mail claiming to be from its domain
DMARC itself is not itself an email authentication protocol, but it builds on key authentication standards SPF and DKIM. With them, it supplements SMTP, the basic protocol used to send email, because SMTP does not itself include any mechanisms for implementing or defining policies for email authentication.
Bagaimana cara kerja DMARC?
DMARC mengandalkan standar SPF dan DKIM yang sudah ada untuk otentikasi email. Ini juga bergantung pada Sistem Nama Domain (DNS) yang sudah mapan. Secara umum, proses validasi DMARC bekerja seperti ini:
Seorang administrator domain mempublikasikan kebijakan yang mendefinisikan praktik otentikasi emailnya dan bagaimana server mail penerima harus menangani email yang melanggar kebijakan ini. Kebijakan DMARC ini terdaftar sebagai bagian dari catatan DNS keseluruhan domain.
Ketika server mail masuk menerima email yang masuk, server tersebut menggunakan DNS untuk melihat kebijakan DMARC untuk domain yang terkandung dalam header "From" pesan (RFC 5322). Server masuk kemudian mengevaluasi pesan untuk tiga faktor kunci:
Apakah tanda tangan DKIM pesan tersebut divalidasi?
Apakah pesan tersebut berasal dari alamat IP yang diizinkan oleh catatan SPF domain pengirim?
Apakah header dalam pesan menunjukkan "penyelarasan domain" yang tepat?
Dengan informasi ini, server siap untuk menerapkan kebijakan DMARC domain pengirim untuk memutuskan apakah akan menerima, menolak, atau menandai pesan email tersebut.
Setelah menggunakan kebijakan DMARC untuk menentukan disposisi yang tepat untuk pesan tersebut, server mail penerima akan melaporkan hasilnya kepada pemilik domain pengirim.
DMARC mengandalkan standar SPF dan DKIM yang sudah ada untuk otentikasi email. Ini juga bergantung pada Sistem Nama Domain (DNS) yang sudah mapan. Secara umum, proses validasi DMARC bekerja seperti ini:
Seorang administrator domain mempublikasikan kebijakan yang mendefinisikan praktik otentikasi emailnya dan bagaimana server mail penerima harus menangani email yang melanggar kebijakan ini. Kebijakan DMARC ini terdaftar sebagai bagian dari catatan DNS keseluruhan domain.
Ketika server mail masuk menerima email yang masuk, server tersebut menggunakan DNS untuk melihat kebijakan DMARC untuk domain yang terkandung dalam header "From" pesan (RFC 5322). Server masuk kemudian mengevaluasi pesan untuk tiga faktor kunci:
Apakah tanda tangan DKIM pesan tersebut divalidasi?
Apakah pesan tersebut berasal dari alamat IP yang diizinkan oleh catatan SPF domain pengirim?
Apakah header dalam pesan menunjukkan "penyelarasan domain" yang tepat?
Dengan informasi ini, server siap untuk menerapkan kebijakan DMARC domain pengirim untuk memutuskan apakah akan menerima, menolak, atau menandai pesan email tersebut.
Setelah menggunakan kebijakan DMARC untuk menentukan disposisi yang tepat untuk pesan tersebut, server mail penerima akan melaporkan hasilnya kepada pemilik domain pengirim.
DMARC mengandalkan standar SPF dan DKIM yang sudah ada untuk otentikasi email. Ini juga bergantung pada Sistem Nama Domain (DNS) yang sudah mapan. Secara umum, proses validasi DMARC bekerja seperti ini:
Seorang administrator domain mempublikasikan kebijakan yang mendefinisikan praktik otentikasi emailnya dan bagaimana server mail penerima harus menangani email yang melanggar kebijakan ini. Kebijakan DMARC ini terdaftar sebagai bagian dari catatan DNS keseluruhan domain.
Ketika server mail masuk menerima email yang masuk, server tersebut menggunakan DNS untuk melihat kebijakan DMARC untuk domain yang terkandung dalam header "From" pesan (RFC 5322). Server masuk kemudian mengevaluasi pesan untuk tiga faktor kunci:
Apakah tanda tangan DKIM pesan tersebut divalidasi?
Apakah pesan tersebut berasal dari alamat IP yang diizinkan oleh catatan SPF domain pengirim?
Apakah header dalam pesan menunjukkan "penyelarasan domain" yang tepat?
Dengan informasi ini, server siap untuk menerapkan kebijakan DMARC domain pengirim untuk memutuskan apakah akan menerima, menolak, atau menandai pesan email tersebut.
Setelah menggunakan kebijakan DMARC untuk menentukan disposisi yang tepat untuk pesan tersebut, server mail penerima akan melaporkan hasilnya kepada pemilik domain pengirim.
Apa itu catatan DMARC?
A DMARC record is included in an organization’s DNS database. An DMARC record is a specially-formatted version of a standard DNS TXT record with a particular name, namely “_dmarc.mydomain.com” (note the leading underscore). A DMARC record looks something like this: _dmarc.mydomain.com. IN TXT “v=DMARC1\; p=none\; rua=mailto:dmarc-aggregate@mydomain.com\; ruf=mailto:dmarc-afrf@mydomain.com\; pct=100”
Reading left-to-right in plain English, this record says:
v=DMARC1 specifies the DMARC version
p=none specifies the preferred treatment, or DMARC policy
rua=mailto:dmarc-aggregate@mydomain.com is the mailbox to which aggregate reports should be sent
ruf=mailto:dmarc-afrf@mydomain.com is the mailbox to which forensic reports should be sent
pct=100 is the percentage of mail to which the domain owner would like to have its policy applied
Additional configuration options are available for a domain owner to use in its DMARC policy record as well, but these are the basics.
A DMARC record is included in an organization’s DNS database. An DMARC record is a specially-formatted version of a standard DNS TXT record with a particular name, namely “_dmarc.mydomain.com” (note the leading underscore). A DMARC record looks something like this: _dmarc.mydomain.com. IN TXT “v=DMARC1\; p=none\; rua=mailto:dmarc-aggregate@mydomain.com\; ruf=mailto:dmarc-afrf@mydomain.com\; pct=100”
Reading left-to-right in plain English, this record says:
v=DMARC1 specifies the DMARC version
p=none specifies the preferred treatment, or DMARC policy
rua=mailto:dmarc-aggregate@mydomain.com is the mailbox to which aggregate reports should be sent
ruf=mailto:dmarc-afrf@mydomain.com is the mailbox to which forensic reports should be sent
pct=100 is the percentage of mail to which the domain owner would like to have its policy applied
Additional configuration options are available for a domain owner to use in its DMARC policy record as well, but these are the basics.
A DMARC record is included in an organization’s DNS database. An DMARC record is a specially-formatted version of a standard DNS TXT record with a particular name, namely “_dmarc.mydomain.com” (note the leading underscore). A DMARC record looks something like this: _dmarc.mydomain.com. IN TXT “v=DMARC1\; p=none\; rua=mailto:dmarc-aggregate@mydomain.com\; ruf=mailto:dmarc-afrf@mydomain.com\; pct=100”
Reading left-to-right in plain English, this record says:
v=DMARC1 specifies the DMARC version
p=none specifies the preferred treatment, or DMARC policy
rua=mailto:dmarc-aggregate@mydomain.com is the mailbox to which aggregate reports should be sent
ruf=mailto:dmarc-afrf@mydomain.com is the mailbox to which forensic reports should be sent
pct=100 is the percentage of mail to which the domain owner would like to have its policy applied
Additional configuration options are available for a domain owner to use in its DMARC policy record as well, but these are the basics.
Apa arti keselarasan domain DMARC?
“Domain alignment” is a concept in DMARC that expands the domain validation intrinsic to SPF and DKIM. DMARC domain alignment matches a message’s “from” domain with information relevant to these other standards:
For SPF, the message’s From domain and its Return-Path domain must match
For DKIM, the message’s From domain and its DKIM d= domain must match
The alignment can be relaxed (matching base domains, but allowing different subdomains) or strict (precisely matching the entire domain). This choice is specified in the published DMARC policy of the sending domain.
“Domain alignment” is a concept in DMARC that expands the domain validation intrinsic to SPF and DKIM. DMARC domain alignment matches a message’s “from” domain with information relevant to these other standards:
For SPF, the message’s From domain and its Return-Path domain must match
For DKIM, the message’s From domain and its DKIM d= domain must match
The alignment can be relaxed (matching base domains, but allowing different subdomains) or strict (precisely matching the entire domain). This choice is specified in the published DMARC policy of the sending domain.
“Domain alignment” is a concept in DMARC that expands the domain validation intrinsic to SPF and DKIM. DMARC domain alignment matches a message’s “from” domain with information relevant to these other standards:
For SPF, the message’s From domain and its Return-Path domain must match
For DKIM, the message’s From domain and its DKIM d= domain must match
The alignment can be relaxed (matching base domains, but allowing different subdomains) or strict (precisely matching the entire domain). This choice is specified in the published DMARC policy of the sending domain.
Apa itu kebijakan DMARC p=?
The DMARC specification provides three choices for domain owners to use to specify their preferred treatment of mail that fails DMARC validation checks. These “p= policies” are:
none: treat the mail the same as it would be without any DMARC validation
quarantine: accept the mail but place it somewhere other than the recipient’s inbox (typically the spam folder)
reject: reject the message outright
Remember that the domain owner can only request, not force, enforcement of its DMARC record; it’s up to the inbound mail server to decide whether or not to honor the requested policy.
The DMARC specification provides three choices for domain owners to use to specify their preferred treatment of mail that fails DMARC validation checks. These “p= policies” are:
none: treat the mail the same as it would be without any DMARC validation
quarantine: accept the mail but place it somewhere other than the recipient’s inbox (typically the spam folder)
reject: reject the message outright
Remember that the domain owner can only request, not force, enforcement of its DMARC record; it’s up to the inbound mail server to decide whether or not to honor the requested policy.
The DMARC specification provides three choices for domain owners to use to specify their preferred treatment of mail that fails DMARC validation checks. These “p= policies” are:
none: treat the mail the same as it would be without any DMARC validation
quarantine: accept the mail but place it somewhere other than the recipient’s inbox (typically the spam folder)
reject: reject the message outright
Remember that the domain owner can only request, not force, enforcement of its DMARC record; it’s up to the inbound mail server to decide whether or not to honor the requested policy.
Apa itu laporan DMARC?
DMARC reports are generated by inbound mail servers as part of the DMARC validation process. There are two formats of DMARC reports:
Aggregate reports, which are XML documents showing statistical data about the messages received that claimed to be from a particular domain. Date reported includes authentication results and message disposition. Aggregate reports are designed to be machine-readable.
Forensic reports, which are individual copies of messages which failed authentication, each enclosed in a full email message using a special format called AFRF. Forensic report can be useful both for troubleshooting a domain’s own authentication issues and for identifying malicious domains and web sites.
DMARC reports are generated by inbound mail servers as part of the DMARC validation process. There are two formats of DMARC reports:
Aggregate reports, which are XML documents showing statistical data about the messages received that claimed to be from a particular domain. Date reported includes authentication results and message disposition. Aggregate reports are designed to be machine-readable.
Forensic reports, which are individual copies of messages which failed authentication, each enclosed in a full email message using a special format called AFRF. Forensic report can be useful both for troubleshooting a domain’s own authentication issues and for identifying malicious domains and web sites.
DMARC reports are generated by inbound mail servers as part of the DMARC validation process. There are two formats of DMARC reports:
Aggregate reports, which are XML documents showing statistical data about the messages received that claimed to be from a particular domain. Date reported includes authentication results and message disposition. Aggregate reports are designed to be machine-readable.
Forensic reports, which are individual copies of messages which failed authentication, each enclosed in a full email message using a special format called AFRF. Forensic report can be useful both for troubleshooting a domain’s own authentication issues and for identifying malicious domains and web sites.
Bagaimana DMARC terkait dengan SPF, DKIM, atau standar lainnya?
DKIM, SPF, and DMARC are all standards that enable different aspects of email authentication. They address complementary issues.
SPF allows senders to define which IP addresses are allowed to send mail for a particular domain.
DKIM provides an encryption key and digital signature that verifies that an email message was not faked or altered.
DMARC unifies the SPF and DKIM authentication mechanisms into a common framework and allows domain owners to declare how they would like email from that domain to be handled if it fails an authorization test.
DKIM, SPF, and DMARC are all standards that enable different aspects of email authentication. They address complementary issues.
SPF allows senders to define which IP addresses are allowed to send mail for a particular domain.
DKIM provides an encryption key and digital signature that verifies that an email message was not faked or altered.
DMARC unifies the SPF and DKIM authentication mechanisms into a common framework and allows domain owners to declare how they would like email from that domain to be handled if it fails an authorization test.
DKIM, SPF, and DMARC are all standards that enable different aspects of email authentication. They address complementary issues.
SPF allows senders to define which IP addresses are allowed to send mail for a particular domain.
DKIM provides an encryption key and digital signature that verifies that an email message was not faked or altered.
DMARC unifies the SPF and DKIM authentication mechanisms into a common framework and allows domain owners to declare how they would like email from that domain to be handled if it fails an authorization test.
Apakah saya perlu DMARC?
Jika Anda adalah bisnis yang mengirim email komersial atau transaksional, Anda pasti perlu menerapkan satu atau lebih bentuk autentikasi email untuk memverifikasi bahwa email benar-benar berasal dari Anda atau bisnis Anda. Mengonfigurasi DMARC dengan benar membantu server email penerima menentukan bagaimana mengevaluasi pesan yang mengklaim berasal dari domain Anda, dan ini adalah salah satu langkah terpenting yang dapat Anda ambil untuk meningkatkan deliverability Anda.
Namun, standar seperti DMARC hanya sebatas itu; MessageBird dan ahli email lainnya merekomendasikan penerapan kebijakan autentikasi email DMARC dalam konteks dari strategi pesan yang lengkap.
Jika Anda adalah bisnis yang mengirim email komersial atau transaksional, Anda pasti perlu menerapkan satu atau lebih bentuk autentikasi email untuk memverifikasi bahwa email benar-benar berasal dari Anda atau bisnis Anda. Mengonfigurasi DMARC dengan benar membantu server email penerima menentukan bagaimana mengevaluasi pesan yang mengklaim berasal dari domain Anda, dan ini adalah salah satu langkah terpenting yang dapat Anda ambil untuk meningkatkan deliverability Anda.
Namun, standar seperti DMARC hanya sebatas itu; MessageBird dan ahli email lainnya merekomendasikan penerapan kebijakan autentikasi email DMARC dalam konteks dari strategi pesan yang lengkap.
Jika Anda adalah bisnis yang mengirim email komersial atau transaksional, Anda pasti perlu menerapkan satu atau lebih bentuk autentikasi email untuk memverifikasi bahwa email benar-benar berasal dari Anda atau bisnis Anda. Mengonfigurasi DMARC dengan benar membantu server email penerima menentukan bagaimana mengevaluasi pesan yang mengklaim berasal dari domain Anda, dan ini adalah salah satu langkah terpenting yang dapat Anda ambil untuk meningkatkan deliverability Anda.
Namun, standar seperti DMARC hanya sebatas itu; MessageBird dan ahli email lainnya merekomendasikan penerapan kebijakan autentikasi email DMARC dalam konteks dari strategi pesan yang lengkap.
Bergabunglah dengan Newsletter kami.
Tetap terinformasi dengan Bird melalui pembaruan mingguan ke kotak masuk Anda.
Dengan mengirimkan, Anda setuju Bird dapat menghubungi Anda tentang produk dan layanan kami.
Anda dapat berhenti berlangganan kapan saja. Lihat Pernyataan Privasi Bird untuk detail tentang pemrosesan data.
Bergabunglah dengan Newsletter kami.
Tetap terinformasi dengan Bird melalui pembaruan mingguan ke kotak masuk Anda.
Dengan mengirimkan, Anda setuju Bird dapat menghubungi Anda tentang produk dan layanan kami.
Anda dapat berhenti berlangganan kapan saja. Lihat Pernyataan Privasi Bird untuk detail tentang pemrosesan data.
Bergabunglah dengan Newsletter kami.
Tetap terinformasi dengan Bird melalui pembaruan mingguan ke kotak masuk Anda.
Dengan mengirimkan, Anda setuju Bird dapat menghubungi Anda tentang produk dan layanan kami.
Anda dapat berhenti berlangganan kapan saja. Lihat Pernyataan Privasi Bird untuk detail tentang pemrosesan data.
Mari hubungkan Anda dengan pakar Bird.
Lihat kekuatan penuh dari Bird dalam 30 menit.
Dengan mengirimkan, Anda setuju Bird dapat menghubungi Anda tentang produk dan layanan kami.
Anda dapat berhenti berlangganan kapan saja. Lihat Pernyataan Privasi Bird untuk detail tentang pemrosesan data.
G
Grow
M
Marketing
M
Manage
A
Automate
Newsletter
Tetap terinformasi dengan Bird melalui pembaruan mingguan ke kotak masuk Anda.
Mari hubungkan Anda dengan pakar Bird.
Lihat kekuatan penuh dari Bird dalam 30 menit.
Dengan mengirimkan, Anda setuju Bird dapat menghubungi Anda tentang produk dan layanan kami.
Anda dapat berhenti berlangganan kapan saja. Lihat Pernyataan Privasi Bird untuk detail tentang pemrosesan data.
G
Grow
M
Marketing
M
Manage
A
Automate
Newsletter
Tetap terinformasi dengan Bird melalui pembaruan mingguan ke kotak masuk Anda.
Mari hubungkan Anda dengan pakar Bird.
Lihat kekuatan penuh dari Bird dalam 30 menit.
Dengan mengirimkan, Anda setuju Bird dapat menghubungi Anda tentang produk dan layanan kami.
Anda dapat berhenti berlangganan kapan saja. Lihat Pernyataan Privasi Bird untuk detail tentang pemrosesan data.
R
Reach
G
Grow
M
Manage
A
Automate
Newsletter
Tetap terinformasi dengan Bird melalui pembaruan mingguan ke kotak masuk Anda.