{"id":21798,"date":"2026-03-16T00:00:00","date_gmt":"2026-03-16T00:00:00","guid":{"rendered":"https:\/\/www.mailgun.com\/blog\/autenticacion-emails-documento-identidad-envios\/"},"modified":"2026-09-15T16:27:59","modified_gmt":"2026-09-15T16:27:59","slug":"autenticacion-emails-documento-identidad-envios","status":"publish","type":"blog","link":"https:\/\/www.mailgun.com\/es\/blog\/deliverability\/autenticacion-emails-documento-identidad-envios\/","title":{"rendered":"Autenticaci\u00f3n de emails: tu documento de identidad para realizar env\u00edos"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Email authentication lets mailbox providers know that you\u2019re a trusted sender \u2013 that you are who you say you are. As a Technical Account Manager at Mailgun, I\u2019m constantly talking to my customers about how to protect against fraud, spoofing, phishing scams, and how to stay out of the spam folder. One of best practices is securing your email marketing program with email authentication.<\/p>\n\n<p class=\"wp-block-paragraph\">But there\u2019s another key reason why email marketers should go through the process with SPF, DKIM, DMARC, and BIMI. (Don\u2019t worry, I\u2019ll explain those acronyms in a minute.) Big-name inbox providers like <a href=\"\/blog\/deliverability\/gmail-and-yahoo-inbox-updates-2024\/\" target=\"_tabs\" rel=\"noopener noreferrer\">Gmail, Yahoo<\/a>, and now <a href=\"\/blog\/deliverability\/microsoft-sender-requirements\/\" target=\"_tabs\" rel=\"noopener noreferrer\">Microsoft<\/a> will require bulk senders \u2013 defined as sending more than 5,000 messages per day \u2013 to authenticate their email. If you want to send email to subscribers that use these popular services, proper email authentication is no longer optional \u2013 it\u2019s essential.<\/p>\n\n<p class=\"wp-block-paragraph\">When we asked senders about their authentication practices for our <a href=\"\/resources\/research\/state-of-deliverability-2023\/\" target=\"_tabs\" rel=\"noopener noreferrer\">State of email deliverability report<\/a>, we found that around 40% are either unsure or not implementing both SPF and DKIM, and among those using DMARC, 40% are not sure what their policy is. Let\u2019s fix that. In this post, we\u2019ll guide you through the email authentication process so you can protect your email marketing program and improve your deliverability:<\/p>\n\r\n    <nav data-content-type=\"longform\" class=\"toc-block longform-spacings px-5 py-6 px-md-6 px-lg-7 py-md-7 bg-light fs-sm rounded-lg\" aria-labelledby=\"toc-title-8722\"><p class=\"h5 m-0\" id=\"toc-title-8722\">\u00cdndice<\/p><div class=\"d-flex mt-3\"><div class=\"w-auto fw-bold text-accent d-flex me-2\">01<\/div><div class=\"d-flex flex-column\"><a class=\"fw-bold scrollme link-body-color text-accent\" href=\"#what-is-email-authentication\">What is email authentication?<\/a><a class=\"scrollme link-body-color\" href=\"#how-email-authentication-works\">How email authentication works<\/a><\/div><\/div><div class=\"d-flex mt-3\"><div class=\"w-auto fw-bold text-accent d-flex me-2\">02<\/div><div class=\"d-flex flex-column\"><a class=\"fw-bold scrollme link-body-color text-accent\" href=\"#email-authentication-methods\">Email authentication methods<\/a><a class=\"scrollme link-body-color\" href=\"#how-sender-policy-framework-spf-works\">How Sender Policy Framework (SPF) works<\/a><a class=\"scrollme link-body-color\" href=\"#how-domain-keys-identified-mail-dkim-works\">How Domain Keys Identified Mail (DKIM) works<\/a><\/div><\/div><div class=\"d-flex mt-3\"><div class=\"w-auto fw-bold text-accent d-flex me-2\">03<\/div><div class=\"d-flex flex-column\"><a class=\"fw-bold scrollme link-body-color text-accent\" href=\"#how-domain-message-authentication-reporting-and-conformance-dmarc-works\">How Domain Message Authentication Reporting and Conformance (DMARC) works<\/a><a class=\"scrollme link-body-color\" href=\"#setting-your-dmarc-policy\">Setting your DMARC policy<\/a><a class=\"scrollme link-body-color\" href=\"#establishing-reverse-dns-pointer-ptr-records\">Establishing reverse DNS\/Pointer (PTR) Records<\/a><a class=\"scrollme link-body-color\" href=\"#choose-your-reporting-structure\">Choose your reporting structure<\/a><\/div><\/div><div class=\"d-flex mt-3\"><div class=\"w-auto fw-bold text-accent d-flex me-2\">04<\/div><div class=\"d-flex flex-column\"><a class=\"fw-bold scrollme link-body-color text-accent\" href=\"#how-brand-indicators-for-message-identification-bimi-works\">How Brand Indicators for Message Identification (BIMI) works<\/a><\/div><\/div><div class=\"d-flex mt-3\"><div class=\"w-auto fw-bold text-accent d-flex me-2\">05<\/div><div class=\"d-flex flex-column\"><a class=\"fw-bold scrollme link-body-color text-accent\" href=\"#email-authentication-the-last-defense\">Email authentication: The last defense<\/a><\/div><\/div><\/nav>\n<h2 class=\"wp-block-heading\">What is email authentication?<\/h2>\n\n<p class=\"wp-block-paragraph\"><b>Email authentication verifies sender identity using multiple methods to separate messages sent by real senders from forged ones. <\/b>Taking ownership and authority of your email and server shows mailbox providers that you\u2019re legit. And it makes it that much more difficult for spammers to impersonate you in the inbox. It\u2019s like a virtual ID card for your domain, as Jonathan Torres explains in this video. <\/p>\n\t<div class=\"custom-video\">\r\n\t\t\t\t\t                    <div class=\"iframe-responsive-container lazy-video rounded-lg overflow-hidden \">\r\n                <a href=\"https:\/\/www.youtube.com\/watch?v=NMOr3BFVu1w\" class=\"lazy-video-link\" data-lazy-video=\"NMOr3BFVu1w\" target=\"_blank\" rel=\"nofollow\" role=\"button\" data-source=\"youtube\" data-language=\"es\" data-thumb=\"https:\/\/img.youtube.com\/vi\/NMOr3BFVu1w\/maxresdefault.jpg\" title=\"V\u00eddeo de Sinch\">\r\n                    <div class=\"btn btn-light btn-light-social btn-play btn-play-circle\">\r\n                                                    <svg aria-hidden=\"true\" data-url=\"https:\/\/www.mailgun.com\/wp-content\/plugins\/sinch-core\/assets\/icons\/sinch\/play.svg\"><\/svg>\r\n                                            <\/div>\r\n                    <img decoding=\"async\"  src=\"https:\/\/img.youtube.com\/vi\/NMOr3BFVu1w\/maxresdefault.jpg\" alt=\"What is email authentication? The secret handshake that gets you to the inbox\">\r\n                <\/a>\r\n            <\/div>\r\n                        <script type=\"application\/ld+json\">\r\n            {\n    \"@context\": \"http:\/\/schema.org\",\n    \"@type\": \"VideoObject\",\n    \"@id\": \"https:\/\/www.youtube.com\/watch?v=NMOr3BFVu1w#VideoObject\",\n    \"thumbnailUrl\": \"https:\/\/img.youtube.com\/vi\/NMOr3BFVu1w\/maxresdefault.jpg\",\n    \"embedUrl\": \"https:\/\/www.youtube.com\/embed\/NMOr3BFVu1w\",\n    \"contentUrl\": \"https:\/\/www.youtube.com\/watch?v=NMOr3BFVu1w\",\n    \"name\": \"What is email authentication? The secret handshake that gets you to the inbox\",\n    \"description\": \"What exactly is email authentication? Email authentication is one of the most misunderstood and technical aspects of email deliverability. Yet, it\\u2019s also one of the most important. While many senders simply add a few DNS records and assume they\\u2019re done, email authentication is far more complex and essential for protecting your reputation as an email sender.  \\n\\nIn this video, we\\u2019ll explain why authentication isn\\u2019t just about SPF, DKIM, and DMARC, it\\u2019s about building trust with mailbox providers while protecting your customers and subscribers from bad actors who send malicious messages. That includes spam, phishing, and email brand spoofing. \\n\\nJonathan Torres, one of our email authentication experts, breaks down the differences between these protocols and explains why each one plays a crucial role in safeguarding your domain. The truth is, SPF, DKIM, and DMARC work best as a team. Think of email authentication like your virtual ID card, If the details don\\u2019t match, you won\\u2019t get in.  \\n\\nMailbox providers use these protocols to verify your emails\\u2019 legitimacy, and improper implementation can trigger red flags, sending your messages straight to the spam folder. Learn how these authentication layers work together to protect your domain and your sender reputation. \\n\\nSee trends in email authentication usage in our free, ungated report: \\nhttps:\/\/www.mailgun.com\/resources\/research\/email-authentication-requirements\/  \\n\\nGet the basics of email authentication to gain a deeper understanding of these protocols: \\nhttps:\/\/www.mailgun.com\/blog\/deliverability\/email-authentication-your-id-card-sending\/\",\n    \"uploadDate\": \"2024-11-20T16:56:50+00:00\",\n    \"duration\": \"PT1M55S\"\n}        <\/script>\r\n        \t\t\r\n\t\t\t<\/div>\r\n\r\n\t\r\n\n<p class=\"wp-block-paragraph\">Establishing brand legitimacy with email authentication isn\u2019t the most glamorous part of sending email. It\u2019s not as fancy as building templates or copywriting the overall email message, but without it, your emails are more likely to land in the spam folder. Better email deliverability starts all the way at the beginning with initial setup and authentication.<\/p>\n\n<p class=\"wp-block-paragraph\">Different providers may require different authentication setups. Required details like which authentication protocols you need and what conditions you need to configure can vary but going without authentications can get you marked as a fake sender even if you\u2019re not. (And we recommend checking all the boxes, anyway.)<\/p>\n\n<p class=\"wp-block-paragraph\">Plus, having the right email authentication in place lets mailbox providers like Gmail catch phishers and fake emails faster \u2013 something we can all get behind.<\/p>\n\n<h3 class=\"wp-block-heading\">How email authentication works<\/h3>\n\n<p class=\"wp-block-paragraph\"><b>Email authentication works by using DNS records to verify different aspects of your sender identity.<\/b> Some records let the receiving server validate the hosts that are allowed to send messages from a specific domain, and others verify sender identity with public-keys and electronic signatures. The policy you set is up to you and the record types you choose.<\/p>\n\n<p class=\"wp-block-paragraph\">The authentication process works like this:<\/p>\n\n<ol class=\"wp-block-list\">\n<li>A business develops a policy to manage how email sent from its domain name is authenticated.<\/li>\n\n\n\n<li>The email sender configures its mail servers to implement and enforce the policy.<\/li>\n\n\n\n<li>The recipient\u2019s server authenticates the message it receives against the business&#8217;s authentication policy.<\/li>\n<\/ol>\n\n<p class=\"wp-block-paragraph\">If authenticated, the recipient\u2019s server accepts the message. If it fails authentication the message is managed based on the policy in place:<\/p>\n\n<ol class=\"wp-block-list\">\n<li>Deliver it to the inbox anyway<\/li>\n\n\n\n<li>Allow the message through but send it to the spam folder<\/li>\n\n\n\n<li>Reject the message (blocking it from deliver)<\/li>\n<\/ol>\n\n<p class=\"wp-block-paragraph\">Doing this improves your deliverability by signaling to mailbox providers that you\u2019re sending legitimate emails, because you\u2019ve gone through the proper email authentication protocols. That means your message should sail through to the inbox instead of landing in the spam folder, unless the subscriber has marked you as such.<\/p>\n\n<p class=\"wp-block-paragraph\">Senders have several different authentication methods to choose from to make this happen. Our recommendation? Doing them all completely secures your email marketing program, improves your deliverability, and helps you comply with new inbox regulations. The authentication processes build off one another to close any gaps one authentication method might leave open. <\/p>\n\n<p class=\"wp-block-paragraph\">Here\u2019s how to do each one:<\/p>\n\n<h2 class=\"wp-block-heading\">Email authentication methods<\/h2>\n\n<p class=\"wp-block-paragraph\"><b>An email authentication method is any technical standard that makes domain-based email authentication possible<\/b>. The elements that are being verified can vary from method to method, but they were all designed as standards to support <a href=\"\/blog\/email\/difference-between-smtp-and-api\/\" target=\"_tabs\" rel=\"noopener noreferrer\">Simple Mail Transfer Protocol (SMTP)<\/a> \u2013 the main protocol (other than API) used to send email. SMTP works well, but it doesn\u2019t have built-in security which is why authentication methods exist.<\/p>\n\n<p class=\"wp-block-paragraph\">Right now, mailbox providers like Gmail, Yahoo, and Microsoft will require you to complete SPF, DKIM, and DMARC. But there\u2019s a fourth email authentication protocol that\u2019s worth checking out, called BIMI. Here\u2019s how to complete the process for each one:<\/p>\n\n<h3 class=\"wp-block-heading\">How Sender Policy Framework (SPF) works<\/h3>\n\n<p class=\"wp-block-paragraph\"><a href=\"\/blog\/deliverability\/spf-records-basics\/\" target=\"_tabs\" rel=\"noopener noreferrer\"><b>Sender Policy Framework (SPF)<\/b><\/a><b> was the first real attempt at an email authentication protocol,<\/b> devised in the early 2000, SPF utilizes a Domain Name System (DNS) TXT record to specify which email sources are valid email senders for the given domain and what to do with the messages that don\u2019t originate from those sources. It acts as a digital bouncer; if you aren\u2019t cool enough to be on the list, you\u2019re likely to get kicked to the curb (or land in the spam folder).<\/p>\n\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" class=\"wp-image-4388\" width=\"2412\" height=\"1086\" src=\"https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/SPF.png\" alt=\"Image shows the SPF authentication flow from the sender, to the inbound mail server and DNS, to the authentication policy.\" srcset=\"https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/SPF.png 2412w, https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/SPF-1024x461.png 1024w, https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/SPF-768x346.png 768w, https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/SPF-1536x692.png 1536w, https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/SPF-2048x922.png 2048w, https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/SPF-300x135.png 300w\" sizes=\"(max-width: 2412px) 100vw, 2412px\" \/><\/figure>\n\n<p class=\"wp-block-paragraph\">An SPF record consists of a collection of mechanisms and qualifiers that tell mailbox providers who should be sending mail on behalf of a domain. The mechanisms identify the email servers while the qualifiers tell us what to do with them. Most ESPs cover your SPF requirements \u2013 we do here at Mailgun.<\/p>\n\n<p class=\"wp-block-paragraph\">When you establish your SPF records, keep these in mind:<\/p>\n\n<ul class=\"wp-block-list\">\n<li><b>Only one valid SPF record is allowed per domain.<\/b> Multiple records can confuse recipient systems.<\/li>\n\n\n\n<li>SPF implementation <b>MUST<\/b> limit the number of mechanisms and modifiers that do DNS lookups to at most 10 per SPF check. (This does take into account INCLUDE and REDIRECT mechanisms.)<\/li>\n\n\n\n<li>We recommend using <code>~all<\/code> as the final entry in the record, but we certainly accept <code>-all<\/code> as well.<\/li>\n\n\n\n<li>We do support SPF recording chaining for whitelisting. <a href=\"\/blog\/deliverability\/white-labeling-dns-records-your-customers-tips-tricks\/\" target=\"_tabs\" rel=\"noopener noreferrer\">See this blog<\/a> for details.<\/li>\n<\/ul>\n    <div data-content-type=\"longform\"  class=\"callout text-body-color px-5 py-6 px-md-6 px-lg-7 py-md-7 longform-spacings rounded-lg bg-light\" data-theme=\"light\">\r\n\r\n        <div class=\"content-body\"> SPF records consist of a collection of mechanisms and qualifiers that tell mailbox providers who should be sending mail on behalf of a domain.<\/div>\r\n    <\/div>\r\n\n<p class=\"wp-block-paragraph\">While SPF works great in most situations, there are some circumstances where it doesn\u2019t quite hold up, like with forwarded messages. <b>Forwarded messages will have the same original sending domain, but it will likely be sent by a server that isn\u2019t specified in the sending domain\u2019s SPF record.<\/b> The likely outcome is messages being tagged as spam unintentionally or the messages being dropped altogether.<\/p>\n\n<p class=\"wp-block-paragraph\">But the biggest problem with SPF authentication is that bad actors can exploit it with a fake domain in the Return Path address and forging the From address to make the email look legitimate. That means <a href=\"https:\/\/powerdmarc.com\/why-spf-not-good-to-stop-spoofing\/\" target=\"_tabs\" rel=\"noopener noreferrer\">SPF not the most effective way to stop brand spoofing<\/a>.<\/p>\n\n<p class=\"wp-block-paragraph\">Bottom line: While you definitely should authenticate your emails with SPF, you should also make sure to complete the other email authentication protocols to fill this gap<\/p>\n\n<h3 class=\"wp-block-heading\">How Domain Keys Identified Mail (DKIM) works<\/h3>\n\n<p class=\"wp-block-paragraph\"><a href=\"\/blog\/deliverability\/understanding-dkim-how-it-works\/\" target=\"_tabs\" rel=\"noopener noreferrer\">DKIM authentication<\/a> is an email authentication protocol that matches a public key with a private key to verify the message was authorized by the owner of the domain it was sent from. It uses this private key to create a DKIM signature, an encrypted header added to your email that receiving mail servers can verify using the corresponding public key to confirm the message was sent from your domain and hasn&#8217;t been altered.<\/p>\n\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" class=\"wp-image-4442\" width=\"1261\" height=\"843\" src=\"https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/DKIM.png\" alt=\"Image shows DKIM authentication flow an email with DKIM signature (private key), to the receiving mail server and DNS server, to the authentication policy (public key) to authentication.\" srcset=\"https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/DKIM.png 1261w, https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/DKIM-300x201.png 300w, https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/DKIM-768x513.png 768w, https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/DKIM-1024x685.png 1024w\" sizes=\"(max-width: 1261px) 100vw, 1261px\" \/><\/figure>\n\n<p class=\"wp-block-paragraph\">DKIM is an excellent resource for an email service provider (ESP) to track a domain\u2019s reputation because signing messages via DKIM is considered authoritative. As an ESP, we take care of a lot of the DKIM heavy lifting on your behalf; however, there are some customization options you should know about.<\/p>\n\n<p class=\"wp-block-paragraph\">At Mailgun, our standard recommendation is to have your sending domain be a subdomain off your main root domain. As such, our customers have the option of <a href=\"https:\/\/documentation.mailgun.com\/docs\/mailgun\/api-reference\/openapi-final\/tag\/Domains\/\" target=\"_tabs\" rel=\"noopener noreferrer\">setting the DKIM authority<\/a> to either be that subdomain or the root (with the caveat that both domains are set up within your Mailgun account.)<\/p>\n\n<p class=\"wp-block-paragraph\">Let\u2019s say your main root domain name is catzrule.org (because cats indeed rule), but you\u2019ve set your Mailgun sending domain name as mg.catzrule.org. By default, our system will want to set the DKIM authority for both domains to catzrule.org. You can overrule that using our API and have mg.catzrule.org have its own value instead. This value can be changed at any time, but be aware that it can have ramifications for your domain reputation.<\/p>\n\n<p class=\"wp-block-paragraph\">When you\u2019re creating your DKIM record, in the signature, you can specify specific message header fields and components that you would like to sign against. However, the \u201cFrom\u201d field is the one message aspect that must be included in the signature. When in doubt, <b>longer DKIM keys equal more protection from spammers.<\/b> Our current default key size is 1024 bits, but we have recently updated our system to be able to generate and utilize 2048 bit keys. 2048 bit keys offer stronger encryption but will generate a larger TXT record as a result, so you may need to consult with your DNS service provider about formatting.<\/p>\n    <div data-content-type=\"longform\"  class=\"callout text-body-color px-5 py-6 px-md-6 px-lg-7 py-md-7 longform-spacings rounded-lg bg-light\" data-theme=\"light\">\r\n\r\n        <div class=\"content-body\"> Creating your DKIM record varies by ESP, so that\u2019s the best place to start. <a href='https:\/\/documentation.mailgun.com\/docs\/mailgun\/api-reference\/openapi-final\/tag\/Domains\/'>Here\u2019s how to do it in Mailgun.<\/a><\/div>\r\n    <\/div>\r\n\n<h2 class=\"wp-block-heading\">How Domain Message Authentication Reporting and Conformance (DMARC) works<\/h2>\n\n<p class=\"wp-block-paragraph\">There wasn\u2019t anything to tie SPF and DKIM together until DMARC entered the picture. <a href=\"\/blog\/deliverability\/implement-dmarc\/\" target=\"_tabs\" rel=\"noopener noreferrer\">Domain-based Message Authentication Reporting and Conformance (DMARC)<\/a> gives domain owners better control over SPF and DKIM and makes these policies easier to handle.<\/p>\n\n<p class=\"wp-block-paragraph\">DMARC builds off the security protocols of SPF and DKIM and takes it a step further by giving domain owners the ability to outline how receiving servers should handle messages that fail authentication. You can\u2019t set up a DMARC policy without first doing SPF and DKIM. The good news? Most ESPs cover the fundamentals of SPF and DKIM (you\u2019re welcome!).<\/p>\n\n<p class=\"wp-block-paragraph\">DMARC records cover three main areas: <\/p>\n\n<ul class=\"wp-block-list\">\n<li><b>Authentication: <\/b>Signals whether SPF and\/or DKIM authentication is in place for the domain. <\/li>\n\n\n\n<li><b>Conformance: <\/b>Suggests how to handle messages that fail to align with those protocols. <\/li>\n\n\n\n<li><b>Reporting: <\/b>Directs how to give feedback to the sender. <\/li>\n<\/ul>\n\n<p class=\"wp-block-paragraph\">We\u2019ll talk about each one:<\/p>\n\n<h3 class=\"wp-block-heading\">Setting your DMARC policy<\/h3>\n\n<p class=\"wp-block-paragraph\">A DMARC policy is principally concerned with the alignment of the \u201cFrom:\u201d field with the authentication mechanisms listed in the SPF or DKIM policy for the domain. In other words, DMARC helps ensure recipients know exactly what to do with a message that fails either SPF or DKIM, while also letting the recipient notify the sender via the reporting function as to how the message performed.<\/p>\n\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" class=\"wp-image-4318\" width=\"2502\" height=\"1230\" src=\"https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/DMARC.png\" alt=\"Image shows how a DMARC policy works from an email with SPF\/DKIM through the mailbox provider, to verifying DMARC implementation, passing DMARC authentication, and applying the DMARC policy to deliver to sender.\" srcset=\"https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/DMARC.png 2502w, https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/DMARC-1024x503.png 1024w, https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/DMARC-768x378.png 768w, https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/DMARC-1536x755.png 1536w, https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/DMARC-2048x1007.png 2048w, https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/DMARC-300x147.png 300w\" sizes=\"(max-width: 2502px) 100vw, 2502px\" \/><\/figure>\n\n<p class=\"wp-block-paragraph\"><a href=\"\/blog\/deliverability\/dmarc-insights-from-dmarcian\/\" target=\"_tabs\" rel=\"noopener noreferrer\">DMARC<\/a> is a line of code added to your DNS record that is designed to help mailbox providers clean more spammers out of the recipient\u2019s inbox. Email marketers have three options when implementing a DMARC policy:<\/p>\n\n<ul class=\"wp-block-list\">\n<li><code><b>p=none<\/b><\/code>, which ensures that messages are scanned according to your DMARC policy alignment specifications, but no action is taken on them. In other words, the none policy tells your recipient\u2019s email provider not to take action against your message if DMARC fails.<\/li>\n\n\n\n<li><code><b>p=quarantine<\/b><\/code>, which separates suspicious emails by placing them somewhere like a spam folder, instead of the inbox.<\/li>\n\n\n\n<li><code><b>p=reject<\/b><\/code>,<b> <\/b>which tells the provider to block any email that fails DMARC. With the reject policy, a message failing DMARC will never see the inside of the inbox.<\/li>\n<\/ul>\n\n<p class=\"wp-block-paragraph\">If this is your first time implementing DMARC, start with <code>p=none<\/code> as you QA. The value in using the none policy is that reports will still be generated for those domains. You can use reports to verify the SPF and DKIM alignment policies. <b>Once you confirm DMARC is working as it should, you must update the policy and instruct receiving mail servers to either quarantine or reject failures moving forward.<\/b><\/p>\n\n<p class=\"wp-block-paragraph\">According to <a href=\"https:\/\/dmarc.org\/stats\/dmarc\/\" target=\"_tabs\" rel=\"noopener noreferrer\">dmarc.org<\/a>, more than two-thirds of active DMARC policies are set to p=none. A relaxed p=none policy does nothing to make your authentication stronger or make the inbox a safer place for subscribers. With <a href=\"\/blog\/deliverability\/gmail-yahoo-webinar-key-takeaways\/\" target=\"_tabs\" rel=\"noopener noreferrer\">Gmail and Yahoo\u2019s new authentication protocol requirements<\/a> \u2013 <a href=\"\/blog\/deliverability\/microsoft-sender-requirements\/\" target=\"_tabs\" rel=\"noopener noreferrer\">and even newer ones in 2025 from Microsoft<\/a> \u2013 the industry is moving to a<b> p=reject<\/b> policy norm.<\/p>\n\n<p class=\"wp-block-paragraph\">Setting your policy to <code>p=reject<\/code> signals to mailbox providers that you mean business. It\u2019s the best way to protect your subscribers from spam and your brand from being spoofed. If you\u2019ve set up your other authentication policies like SPF and DKIM, <a href=\"\/blog\/deliverability\/domain-reputation-and-dmarc\/\" target=\"_tabs\" rel=\"noopener noreferrer\">in addition to DMARC<\/a>, then a <code>p=reject<\/code> shouldn\u2019t hurt your chances of getting to the inbox. If anything, it will help.<\/p>\n    <div data-content-type=\"longform\" class=\"quote hub-quote longform-spacings d-flex flex-column rounded-lg px-5 py-6 px-md-6 py-md-7 p-lg-7 shadow-sm bg-primary\" data-theme=\"light\">\r\n\r\n        <div class=\"quote-logo mb-3\">\r\n                            <svg height=\"40\" class=\"quote-icon quote-icon-color\" aria-hidden=\"true\" data-url=\"https:\/\/www.mailgun.com\/wp-content\/plugins\/sinch-core\/assets\/icons\/custom-icons\/quotes-right.svg\"><\/svg>\r\n                    <\/div>\r\n\r\n        <blockquote class=\"quote-content content-body m-0 text-body-color\" id=\"quote-block-21c438655d2c02745443514d1bf104b0\">\r\n            The end goal is ideally a policy of p=reject. That&#x27;s what DMARC is for. Ensuring that your domain cannot be spoofed and protecting our mutual customers from abuse.        <\/blockquote>\r\n\r\n                    <div class=\"d-flex gap-3 mt-5\">\r\n                                    <div>\r\n                        <img decoding=\"async\" width=\"72\" height=\"72\" class=\"rounded-lg quote-author\" src=\"https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/06\/Marcel-Becker.png\" alt=\"Foto de Marcel Becker\">\r\n                    <\/div>\r\n                                <div class=\"d-flex flex-column align-self-center fs-sm\">\r\n                    <cite class=\"mb-0 fw-bold text-accent fst-normal\" aria-describedby=\"quote-block-21c438655d2c02745443514d1bf104b0\">\r\n                        Marcel Becker                    <\/cite>\r\n                                            <span class=\"mb-0 text-body-color\">Senior Director of Product at Yahoo<\/span>\r\n                                    <\/div>\r\n            <\/div>\r\n            <\/div>\r\n\n<h3 class=\"wp-block-heading\">Establishing reverse DNS\/Pointer (PTR) Records<\/h3>\n\n<p class=\"wp-block-paragraph\"><b>Setting up your reverse DNS\/PTR records is step one when implementing DMARC. <\/b>Reverse DNS works by resolving a domain\u2019s DNS (name) to an IP address, rather than resolving an IP address to a domain name. The last point of authentication comes at the server end of things with <a href=\"\/blog\/deliverability\/reverse-dns-white-labeling-hello-my-name-is\/\" target=\"_tabs\" rel=\"noopener noreferrer\">Reverse DNS or Pointer (PTR) records.<\/a><\/p>\n\n<p class=\"wp-block-paragraph\">All mail servers will have a sending IP address that is used to talk to other servers, but we also recommend that a human-friendly name is attached to that IP address. <b>Reverse DNS records and PTR records make it easy to identify the server when looking at mail logs and email headers<\/b>, so you don\u2019t have to memorize IP addresses.<\/p>\n\n<p class=\"wp-block-paragraph\">At Mailgun, all of our shared and dedicated IP space comes with a preconfigured PTR record. So, no matter your account or IP type, you are covered by default.<\/p>\n    <div data-content-type=\"longform\"  class=\"callout text-body-color px-5 py-6 px-md-6 px-lg-7 py-md-7 longform-spacings rounded-lg bg-light\" data-theme=\"light\">\r\n\r\n        <div class=\"content-body\"> For accounts with dedicated IPs <a href='\/products\/inbox\/deliverability-services\/'>we offer assistance<\/a> setting up a custom PTR record with your sending domain. This allows for a final layer of authentication at the IP level.<\/div>\r\n    <\/div>\r\n\n<h3 class=\"wp-block-heading\">Choose your reporting structure<\/h3>\n\n<p class=\"wp-block-paragraph\">There are two types of DMARC reports that recipients can send to DMARC-authenticated domain owners:<\/p>\n\n<ul class=\"wp-block-list\">\n<li><b>Aggregate reports<\/b> will usually be sent daily by recipient servers and collect various statistics for a sending domain. A typical aggregate report will be in XML format and include details on the sending IP, SPF\/DKIM alignment passes or failures, and the header FROM domain, along with counts of each message.<\/li>\n\n\n\n<li><b>Forensic reports<\/b> show real-time DMARC message alignment failures, including a redacted copy of the original message which triggered the failure. Domain owners should utilize these \u2018failure reports\u2019 to understand their failures (message failures, not personal\/professional) and address any issues uncovered.<\/li>\n<\/ul>\n\n<p class=\"wp-block-paragraph\">Unlike SPF and DKIM, DMARC gives senders more insight into their deliverability \u2013 so regardless of what kind of reporting you choose, pay attention to what\u2019s going on with your DMARC so you can address any issues before they hurt your sender reputation.<\/p>\n    <div data-content-type=\"longform\"  class=\"callout text-body-color px-5 py-6 px-md-6 px-lg-7 py-md-7 longform-spacings rounded-lg bg-light\" data-theme=\"light\">\r\n\r\n        <div class=\"content-body\"> Implementing DKIM and DMARC is more important now than ever. Gmail and Yahoo began enforcing stricter sender requirements in early 2024, and Microsoft is following suit with similar policies for Outlook in 2025. These updates make email authentication checks \u2013 specifically passing SPF, DKIM, and DMARC authentication \u2013 mandatory for bulk senders. Want help navigating the new email authentication requirements? Join us live for a Deliverability Academy session focused on authentication \u2013 plus tips to meet the latest mandates from <a href='\/blog\/deliverability\/gmail-and-yahoo-inbox-updates-2024\/'>Gmail, Yahoo<\/a>, and <a href='\/blog\/deliverability\/microsoft-sender-requirements\/'>Microsoft<\/a>. <a href='https:\/\/s.sinch.com\/4mer791'>Register now<\/a>.<\/div>\r\n    <\/div>\r\n\n<h2 class=\"wp-block-heading\">How Brand Indicators for Message Identification (BIMI) works<\/h2>\n\n<p class=\"wp-block-paragraph\">Unlike SPF, DKIM, and DMARC, BIMI is not required by Gmail, Yahoo, and Microsoft (yet.) But wait! Don\u2019t go \u2013 BIMI is one of the newest forms of authentication and the one that can help your brand in the inbox the most.<\/p>\n\n<p class=\"wp-block-paragraph\">BIMI allows you to include a branded <a href=\"\/blog\/product\/including-a-sender-image\/\" target=\"_tabs\" rel=\"noopener noreferrer\">sender image<\/a> using your brand\u2019s logo along with your message. Not only does BIMI provide brand recognition at a glance, but it\u2019s a DNS TXT record that provides additional authentication. According to the recent Sinch report on the state of customer communications, <strong><a href=\"https:\/\/www.mailgun.com\/blog\/email\/customer-communication-challenges-2025\/\">53% of consumers say they\u2019ve received legitimate brand emails they didn\u2019t trust.<\/a><\/strong> With phishing at an all time high, certifications like Bimi can help boost brand trust visually inside the inbox while adding an extra layer of authentication.<\/p>\n\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" class=\"wp-image-4443\" width=\"1424\" height=\"1016\" src=\"https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/EN-MJ-BMI-Mockups.png\" alt=\"Mobile devices with and without inbox logos\" srcset=\"https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/EN-MJ-BMI-Mockups.png 1424w, https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/EN-MJ-BMI-Mockups-300x214.png 300w, https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/EN-MJ-BMI-Mockups-768x548.png 768w, https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/EN-MJ-BMI-Mockups-1024x731.png 1024w\" sizes=\"(max-width: 1424px) 100vw, 1424px\" \/><\/figure>\n\n<p class=\"wp-block-paragraph\">Think of BIMI as the icing on the cake. After you\u2019ve jumped through the hoops and configured all your authentication standards, you become eligible for a BIMI record but there is a caveat. <a href=\"\/blog\/deliverability\/bimi-more-than-funny-name\/#chapter-2\" target=\"_tabs\" rel=\"noopener noreferrer\"><b>For BIMI to work<\/b><\/a><b>, your DMARC policy must be set to either quarantine or reject.<\/b><\/p>\n    <div data-content-type=\"longform\"  class=\"callout text-body-color px-5 py-6 px-md-6 px-lg-7 py-md-7 longform-spacings rounded-lg bg-light\" data-theme=\"light\">\r\n\r\n        <div class=\"content-body\"> We still recommend starting with p=none when you implement DMARC \u2013 this is a great way to test DMARC configurations and reporting, but it shouldn\u2019t be your ongoing standard as it doesn\u2019t protect against phishing or spoofing. <b>BIMI requires <\/b>p=quarantine<b> or <\/b>p=reject<b> as part of a larger movement to enforce stricter DMARC policies.<\/b><\/div>\r\n    <\/div>\r\n\n<h2 class=\"wp-block-heading\">Email authentication: The last defense<\/h2>\n\n<p class=\"wp-block-paragraph\">Email authentication isn\u2019t just about securing your identity, it\u2019s a deciding factor in message filtering. At the end of your email\u2019s journey, when the ISPs are deciding whether to let your message into the inbox, authentication is what gets your message past spam filters and into subscribers\u2019 inboxes. <a href=\"\/blog\/email\/email-predictions-2024\/\" target=\"_tabs\" rel=\"noopener noreferrer\">It\u2019s a hot topic right now, and for good reason.<\/a><\/p>\n\n<p class=\"wp-block-paragraph\">The real question isn\u2019t whether or not to go through with the process of email authentication, but if you can afford <i>not to.<\/i><\/p>\n\n<p class=\"wp-block-paragraph\">Email authentication encompasses deliverability, reputation, and security. There\u2019s a lot more to implementing and understanding email authentication protocols, and security goes far beyond authentication. Curious about other ways to secure your email program? We are too. So curious, in fact, that we gathered our most dedicated security and deliverability email geeks to put together a comprehensive guide. Check it out for everything you need to know about email security and compliance.<\/p>\n\r\n    <aside data-content-type=\"longform\"  class=\"banner-block longform-spacings rounded-lg shadow-lg px-5 py-6 px-md-6 py-md-7 p-lg-7 bg-light\" data-theme=\"dark\" aria-labelledby=\"banner-block-block_566a2e81447bcef202365f3f1ca80d80\">\r\n                    <p class=\"text-uppercase section-caption text-body-color\">\r\n                Learn about email security and compliance            <\/p>\r\n                            <p class=\"h4 text-accent fw-bold\" id=\"banner-block-block_566a2e81447bcef202365f3f1ca80d80\">\r\n                Email security and compliance            <\/p>\r\n                            <div class=\"mb-0 text-body-color\">\r\n                                    <div class=\"content-body mb-0 text-body-color\">Email security isn&#x27;t easy. But you need to protect your business, brand, employees, and subscribers. Find out about the benefits of continually improving email security and compliance from our industry experts. It&#x27;s yours to explore. No form filling required.<\/div>\r\n                            <\/div>\r\n        \r\n        <div class=\"text-start mt-5\"><a href=\"https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/10\/GU-MG-Security-and-Compliance.pdf\" target=\"_blank\" class=\"btn btn-secondary\" >Get the guide<\/a><\/div>\r\n    <\/aside>\r\n\r\n","protected":false},"excerpt":{"rendered":"<p>No puedes conducir un coche sin carn\u00e9. No puedes viajar a otro pa\u00eds sin pasaporte. Y no puedes ser un remitente leg\u00edtimo sin autenticaci\u00f3n. Pero \u00bfqu\u00e9 implica la autenticaci\u00f3n y cu\u00e1les necesitas para proteger tu identidad? Desc\u00fabrelo en nuestro art\u00edculo.<\/p>\n","protected":false},"author":48,"featured_media":4376,"menu_order":0,"template":"","meta":{"_acf_changed":false,"footnotes":""},"blog_category":[21],"class_list":["post-21798","blog","type-blog","status-publish","has-post-thumbnail","hentry","blog_category-deliverability"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.4 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Conceptos b\u00e1sicos de autenticaci\u00f3n de emails: SPF, DKIM, DMARC y BIMI - Transactional Email API Service For Developers | Mailgun<\/title>\n<meta name=\"description\" content=\"Nuestra gu\u00eda sobre autenticaci\u00f3n de emails abarca SPF, DKIM, DMARC y BIMI, adem\u00e1s de lo que ahora exigen Gmail, Yahoo y Microsoft a los remitentes.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.mailgun.com\/es\/blog\/deliverability\/autenticacion-emails-documento-identidad-envios\/\" \/>\n<meta property=\"og:locale\" content=\"es_ES\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Conceptos b\u00e1sicos de autenticaci\u00f3n de emails: SPF, DKIM, DMARC y BIMI - Transactional Email API Service For Developers | Mailgun\" \/>\n<meta property=\"og:description\" content=\"Nuestra gu\u00eda sobre autenticaci\u00f3n de emails abarca SPF, DKIM, DMARC y BIMI, adem\u00e1s de lo que ahora exigen Gmail, Yahoo y Microsoft a los remitentes.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.mailgun.com\/es\/blog\/deliverability\/autenticacion-emails-documento-identidad-envios\/\" \/>\n<meta property=\"og:site_name\" content=\"Transactional Email API Service For Developers | Mailgun\" \/>\n<meta property=\"article:modified_time\" content=\"2026-09-15T16:27:59+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/MG-Blog-Deliverability.png\" \/>\n\t<meta property=\"og:image:width\" content=\"720\" \/>\n\t<meta property=\"og:image:height\" content=\"448\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"13 minutos\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.mailgun.com\\\/es\\\/blog\\\/deliverability\\\/autenticacion-emails-documento-identidad-envios\\\/\",\"url\":\"https:\\\/\\\/www.mailgun.com\\\/es\\\/blog\\\/deliverability\\\/autenticacion-emails-documento-identidad-envios\\\/\",\"name\":\"Conceptos b\u00e1sicos de autenticaci\u00f3n de emails: SPF, DKIM, DMARC y BIMI - Transactional Email API Service For Developers | Mailgun\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.mailgun.com\\\/es\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.mailgun.com\\\/es\\\/blog\\\/deliverability\\\/autenticacion-emails-documento-identidad-envios\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.mailgun.com\\\/es\\\/blog\\\/deliverability\\\/autenticacion-emails-documento-identidad-envios\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.mailgun.com\\\/wp-content\\\/uploads\\\/2025\\\/07\\\/MG-Blog-Deliverability.png\",\"datePublished\":\"2026-03-16T00:00:00+00:00\",\"dateModified\":\"2026-09-15T16:27:59+00:00\",\"description\":\"Nuestra gu\u00eda sobre autenticaci\u00f3n de emails abarca SPF, DKIM, DMARC y BIMI, adem\u00e1s de lo que ahora exigen Gmail, Yahoo y Microsoft a los remitentes.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.mailgun.com\\\/es\\\/blog\\\/deliverability\\\/autenticacion-emails-documento-identidad-envios\\\/#breadcrumb\"},\"inLanguage\":\"es\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.mailgun.com\\\/es\\\/blog\\\/deliverability\\\/autenticacion-emails-documento-identidad-envios\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"es\",\"@id\":\"https:\\\/\\\/www.mailgun.com\\\/es\\\/blog\\\/deliverability\\\/autenticacion-emails-documento-identidad-envios\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.mailgun.com\\\/wp-content\\\/uploads\\\/2025\\\/07\\\/MG-Blog-Deliverability.png\",\"contentUrl\":\"https:\\\/\\\/www.mailgun.com\\\/wp-content\\\/uploads\\\/2025\\\/07\\\/MG-Blog-Deliverability.png\",\"width\":720,\"height\":448},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.mailgun.com\\\/es\\\/blog\\\/deliverability\\\/autenticacion-emails-documento-identidad-envios\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.mailgun.com\\\/es\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Blog\",\"item\":\"https:\\\/\\\/www.mailgun.com\\\/es\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Autenticaci\u00f3n de emails: tu documento de identidad para realizar env\u00edos\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.mailgun.com\\\/es\\\/#website\",\"url\":\"https:\\\/\\\/www.mailgun.com\\\/es\\\/\",\"name\":\"Transactional Email API Service For Developers | Mailgun\",\"description\":\"Potentes API de email transaccional que te permiten enviar, recibir y hacer seguimiento de emails, creadas pensando en los desarrolladores. \u00a1Descubre m\u00e1s!\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.mailgun.com\\\/es\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.mailgun.com\\\/es\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"es\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.mailgun.com\\\/es\\\/#organization\",\"name\":\"Transactional Email API Service For Developers | Mailgun\",\"url\":\"https:\\\/\\\/www.mailgun.com\\\/es\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"es\",\"@id\":\"https:\\\/\\\/www.mailgun.com\\\/es\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.mailgun.com\\\/wp-content\\\/uploads\\\/2025\\\/06\\\/cropped-android-chrome-512x512-1.png\",\"contentUrl\":\"https:\\\/\\\/www.mailgun.com\\\/wp-content\\\/uploads\\\/2025\\\/06\\\/cropped-android-chrome-512x512-1.png\",\"width\":512,\"height\":512,\"caption\":\"Transactional Email API Service For Developers | Mailgun\"},\"image\":{\"@id\":\"https:\\\/\\\/www.mailgun.com\\\/es\\\/#\\\/schema\\\/logo\\\/image\\\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Conceptos b\u00e1sicos de autenticaci\u00f3n de emails: SPF, DKIM, DMARC y BIMI - Transactional Email API Service For Developers | Mailgun","description":"Nuestra gu\u00eda sobre autenticaci\u00f3n de emails abarca SPF, DKIM, DMARC y BIMI, adem\u00e1s de lo que ahora exigen Gmail, Yahoo y Microsoft a los remitentes.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.mailgun.com\/es\/blog\/deliverability\/autenticacion-emails-documento-identidad-envios\/","og_locale":"es_ES","og_type":"article","og_title":"Conceptos b\u00e1sicos de autenticaci\u00f3n de emails: SPF, DKIM, DMARC y BIMI - Transactional Email API Service For Developers | Mailgun","og_description":"Nuestra gu\u00eda sobre autenticaci\u00f3n de emails abarca SPF, DKIM, DMARC y BIMI, adem\u00e1s de lo que ahora exigen Gmail, Yahoo y Microsoft a los remitentes.","og_url":"https:\/\/www.mailgun.com\/es\/blog\/deliverability\/autenticacion-emails-documento-identidad-envios\/","og_site_name":"Transactional Email API Service For Developers | Mailgun","article_modified_time":"2026-09-15T16:27:59+00:00","og_image":[{"width":720,"height":448,"url":"https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/MG-Blog-Deliverability.png","type":"image\/png"}],"twitter_card":"summary_large_image","twitter_misc":{"Est. reading time":"13 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/www.mailgun.com\/es\/blog\/deliverability\/autenticacion-emails-documento-identidad-envios\/","url":"https:\/\/www.mailgun.com\/es\/blog\/deliverability\/autenticacion-emails-documento-identidad-envios\/","name":"Conceptos b\u00e1sicos de autenticaci\u00f3n de emails: SPF, DKIM, DMARC y BIMI - Transactional Email API Service For Developers | Mailgun","isPartOf":{"@id":"https:\/\/www.mailgun.com\/es\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.mailgun.com\/es\/blog\/deliverability\/autenticacion-emails-documento-identidad-envios\/#primaryimage"},"image":{"@id":"https:\/\/www.mailgun.com\/es\/blog\/deliverability\/autenticacion-emails-documento-identidad-envios\/#primaryimage"},"thumbnailUrl":"https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/MG-Blog-Deliverability.png","datePublished":"2026-03-16T00:00:00+00:00","dateModified":"2026-09-15T16:27:59+00:00","description":"Nuestra gu\u00eda sobre autenticaci\u00f3n de emails abarca SPF, DKIM, DMARC y BIMI, adem\u00e1s de lo que ahora exigen Gmail, Yahoo y Microsoft a los remitentes.","breadcrumb":{"@id":"https:\/\/www.mailgun.com\/es\/blog\/deliverability\/autenticacion-emails-documento-identidad-envios\/#breadcrumb"},"inLanguage":"es","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.mailgun.com\/es\/blog\/deliverability\/autenticacion-emails-documento-identidad-envios\/"]}]},{"@type":"ImageObject","inLanguage":"es","@id":"https:\/\/www.mailgun.com\/es\/blog\/deliverability\/autenticacion-emails-documento-identidad-envios\/#primaryimage","url":"https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/MG-Blog-Deliverability.png","contentUrl":"https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/MG-Blog-Deliverability.png","width":720,"height":448},{"@type":"BreadcrumbList","@id":"https:\/\/www.mailgun.com\/es\/blog\/deliverability\/autenticacion-emails-documento-identidad-envios\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.mailgun.com\/es\/"},{"@type":"ListItem","position":2,"name":"Blog","item":"https:\/\/www.mailgun.com\/es\/blog\/"},{"@type":"ListItem","position":3,"name":"Autenticaci\u00f3n de emails: tu documento de identidad para realizar env\u00edos"}]},{"@type":"WebSite","@id":"https:\/\/www.mailgun.com\/es\/#website","url":"https:\/\/www.mailgun.com\/es\/","name":"Transactional Email API Service For Developers | Mailgun","description":"Potentes API de email transaccional que te permiten enviar, recibir y hacer seguimiento de emails, creadas pensando en los desarrolladores. \u00a1Descubre m\u00e1s!","publisher":{"@id":"https:\/\/www.mailgun.com\/es\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.mailgun.com\/es\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"es"},{"@type":"Organization","@id":"https:\/\/www.mailgun.com\/es\/#organization","name":"Transactional Email API Service For Developers | Mailgun","url":"https:\/\/www.mailgun.com\/es\/","logo":{"@type":"ImageObject","inLanguage":"es","@id":"https:\/\/www.mailgun.com\/es\/#\/schema\/logo\/image\/","url":"https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/06\/cropped-android-chrome-512x512-1.png","contentUrl":"https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/06\/cropped-android-chrome-512x512-1.png","width":512,"height":512,"caption":"Transactional Email API Service For Developers | Mailgun"},"image":{"@id":"https:\/\/www.mailgun.com\/es\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/www.mailgun.com\/es\/wp-json\/wp\/v2\/blog\/21798","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.mailgun.com\/es\/wp-json\/wp\/v2\/blog"}],"about":[{"href":"https:\/\/www.mailgun.com\/es\/wp-json\/wp\/v2\/types\/blog"}],"author":[{"embeddable":true,"href":"https:\/\/www.mailgun.com\/es\/wp-json\/wp\/v2\/users\/48"}],"version-history":[{"count":2,"href":"https:\/\/www.mailgun.com\/es\/wp-json\/wp\/v2\/blog\/21798\/revisions"}],"predecessor-version":[{"id":21839,"href":"https:\/\/www.mailgun.com\/es\/wp-json\/wp\/v2\/blog\/21798\/revisions\/21839"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.mailgun.com\/es\/wp-json\/wp\/v2\/media\/4376"}],"wp:attachment":[{"href":"https:\/\/www.mailgun.com\/es\/wp-json\/wp\/v2\/media?parent=21798"}],"wp:term":[{"taxonomy":"blog_category","embeddable":true,"href":"https:\/\/www.mailgun.com\/es\/wp-json\/wp\/v2\/blog_category?post=21798"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}