{"id":20054,"date":"2025-05-14T00:00:00","date_gmt":"2025-05-14T00:00:00","guid":{"rendered":"https:\/\/www.mailgun.com\/blog\/como-configurar-autenticacao-e-mail\/"},"modified":"2026-09-15T10:56:43","modified_gmt":"2026-09-15T10:56:43","slug":"como-configurar-autenticacao-e-mail","status":"publish","type":"blog","link":"https:\/\/www.mailgun.com\/pt\/blog\/dev-life\/como-configurar-autenticacao-e-mail\/","title":{"rendered":"Como autenticar seu e-mail para ter melhores taxas de entrega"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">When building applications that send emails\u2014like marketing platforms or CRM systems\u2014your users need confidence that messages will reach their inbox. But with evolving anti-spam measures, even legitimate emails can face roadblocks.<\/p>\n\n<p class=\"wp-block-paragraph\">Email authentication protocols like SPF, DKIM, and DMARC verify sender identity, prevent spoofing, and support a strong sender reputation. This post explains how these protocols work, how to configure them, and how to confirm they\u2019re set up correctly\u2014so your emails get delivered as intended.<\/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-7804\"><p class=\"h5 m-0\" id=\"toc-title-7804\">\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=\"#why-email-deliverability-matters\">Why email deliverability matters<\/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=\"#authenticating-your-email-for-better-delivery-rates\">Authenticating your email for better delivery rates<\/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=\"#setting-up-spf\">Setting up SPF<\/a><a class=\"scrollme link-body-color\" href=\"#creating-an-spf-record\">Creating an SPF record<\/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=\"#configuring-dkim\">Configuring DKIM<\/a><a class=\"scrollme link-body-color\" href=\"#creating-dkim-keys\">Creating DKIM keys<\/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=\"#implementing-dmarc\">Implementing DMARC<\/a><\/div><\/div><div class=\"d-flex mt-3\"><div class=\"w-auto fw-bold text-accent d-flex me-2\">06<\/div><div class=\"d-flex flex-column\"><a class=\"fw-bold scrollme link-body-color text-accent\" href=\"#wrapping-up\">Wrapping up<\/a><\/div><\/div><\/nav>\n<h2 class=\"wp-block-heading\">Why email deliverability matters<\/h2>\n\n<p class=\"wp-block-paragraph\">If your application offers email functionality, you need to make sure they&#8217;re actually delivered. Misconfigured authentication shouldn&#8217;t leave users thinking messages were sent when they weren&#8217;t.<\/p>\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/www.mailgun.com\/blog\/deliverability\/email-authentication-your-id-card-sending\/\" target=\"_tabs\" rel=\"noopener noreferrer\">Authentication<\/a> configuration problems can result in high <a href=\"https:\/\/www.mailgun.com\/blog\/deliverability\/email-bounces-what-to-do-about-them\/\" target=\"_tabs\" rel=\"noopener noreferrer\">bounce rates<\/a>, <a href=\"https:\/\/www.mailgun.com\/blog\/deliverability\/spam-complaint-rate\/\" target=\"_tabs\" rel=\"noopener noreferrer\">spam complaints<\/a>, and blocklisted IP addresses. It also opens you up to email spoofing and phishing attacks, which can have an impact on your sender&#8217;s reputation and organizational security posture.<\/p>\n\n<p class=\"wp-block-paragraph\">Deliverability issues can also eat into your developers&#8217; time, impacting productivity. Consider cases where intermittent delivery issues are escalated through customer support to the development team. Developers then have to stop what they&#8217;re doing and find out what happened to the affected emails \u2013 whether they bounced or faced other delivery issues. Diagnosing such issues can be very time-consuming and can kill productivity if they&#8217;re a regular occurrence.<\/p>\n\n<p class=\"wp-block-paragraph\">Luckily, none of these are new problems, and there are solutions you can adopt to improve your email deliverability. Email authentication protocols (including SPF, DKIM, and DMARC) can be used to mitigate these issues. And, when you use them together, you can put your email-sending application in the best position to s\ucceed with reliable, trusted email delivery.<\/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 a more holistic understanding of the challenges of email delivery, be sure to check out the <a href='https:\/\/www.mailgun.com\/pt\/state-of-email-deliverability\/chapter\/introducao\/'>state of email deliverability report<\/a>.<\/div>\r\n    <\/div>\r\n\n<h2 class=\"wp-block-heading\">Authenticating your email for better delivery rates<\/h2>\n\n<p class=\"wp-block-paragraph\">SPF is a mechanism that allows you to define DNS records that track which servers are allowed to send emails on behalf of your domain. Without SPF records, anyone would be able to send spoofed emails pretending to be from your domain, and there would be no way to verify their claims. Similarly, misconfigured SPF records can be problematic: You might send a legitimate email from your own domain, but if the SPF records are not configured to include the sending server as a valid source, the email is likely to get flagged as spam or rejected.<\/p>\n\n<h2 class=\"wp-block-heading\">Setting up SPF<\/h2>\n\n<p class=\"wp-block-paragraph\">To check if your domain has SPF records already, you can use a tool like <a href=\"https:\/\/mxtoolbox.com\/SuperTool.aspx\" target=\"_tabs\" rel=\"noopener noreferrer\">MxToolbox<\/a>. Or, if you prefer the terminal, you can use the dig command, like this:<\/p>\n\n<p class=\"wp-block-paragraph\"><code>$ dig +short TXT yourdomain.com | grep spf<\/code><\/p>\n\n<p class=\"wp-block-paragraph\">If you&#8217;re missing an SPF record, you won&#8217;t see any output. However, if you already have a record, you should see something like this:<\/p>\n\n<p class=\"wp-block-paragraph\"><code>v=spf1 include:mailgun.org ~all<\/code><\/p>\n\n<p class=\"wp-block-paragraph\">There are three key components to this record:<\/p>\n\n<ul class=\"wp-block-list\">\n<li><code>v=spf1 <\/code>denotes the version of the SPF protocol being used. All SPF records should start with this tag.<\/li>\n\n\n\n<li><code>include:mailgun.org <\/code>specifies that the domain <code>mailgun.org<\/code> is allowed to send emails on behalf of your domain. When the receiving mail server receives an email from <code>mailgun.org<\/code>, it checks for an SPF record that includes this to validate the sending server. Note that you can include multiple domains here if desired, like <code>include:mailgun.org include:google.com<\/code>.<\/li>\n\n\n\n<li><code>~all<\/code> specifies the policy for emails that do not match the SPF rules. In this case, <code>~ <\/code>denotes a &#8220;soft fail,&#8221; where emails not matching the policy should be accepted but marked as suspicious rather than outright rejected. Alternatively, you could use -all to specify a &#8220;hard fail&#8221; for emails that do not match the policy.<\/li>\n<\/ul>\n\n<h3 class=\"wp-block-heading\">Creating an SPF record<\/h3>\n\n<p class=\"wp-block-paragraph\">Now that you understand the components of an <a href=\"https:\/\/www.mailgun.com\/blog\/deliverability\/spf-records-basics\/\" target=\"_tabs\" rel=\"noopener noreferrer\">SPF record,<\/a> creating a record for your domain is simply a matter of adding a new TXT DNS record.<\/p>\n\n<p class=\"wp-block-paragraph\">If you&#8217;re unsure how to do this, the Mailgun Help Center has guides for the following DNS providers:<\/p>\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https:\/\/help.mailgun.com\/hc\/en-us\/articles\/15353034939931\" target=\"_tabs\" rel=\"noopener noreferrer\">GoDaddy<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/help.mailgun.com\/hc\/en-us\/articles\/15585722150299\" target=\"_tabs\" rel=\"noopener noreferrer\">Cloudflare<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/help.mailgun.com\/hc\/en-us\/articles\/15823826021275\" target=\"_tabs\" rel=\"noopener noreferrer\">Namecheap<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/help.mailgun.com\/hc\/en-us\/articles\/15351999098523\" target=\"_tabs\" rel=\"noopener noreferrer\">Google Domains<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/help.mailgun.com\/hc\/en-us\/articles\/14707808393499\" target=\"_tabs\" rel=\"noopener noreferrer\">DigitalOcean<\/a><\/li>\n<\/ul>\n\n<p class=\"wp-block-paragraph\">If you already have an SPF record and need to add a new domain, be aware that you cannot add multiple SPF records for the same domain. Instead, you need to modify your existing record and add a new value to it. For instance, if your current SPF record is <code>v=spf1 include:example.com ~all <\/code>and you want to add <code>mailgun.org<\/code>, your new record would be <code>v=spf1 include:example.com include:mailgun.org ~all<\/code>.<\/p>\n\n<p class=\"wp-block-paragraph\">While basic SPF records are fairly simple to create and manage, they can introduce friction for developers when you need to manage SPF records for multiple sending services. For instance, if you have marketing tools, CRMs, and messaging services all sending emails from the same domain, you might end up with long, complex SPF records.<\/p>\n\n<p class=\"wp-block-paragraph\">The SPF protocol also has a limit of 10 DNS lookups, where only the first 10 lookups in your SPF record will be actioned. If the email is not matched within these 10 lookups, it will be treated as unauthenticated. When this happens, there are a few things you can try:<\/p>\n\n<ul class=\"wp-block-list\">\n<li><b>Dedicated subdomains:<\/b> You can assign each sending service a dedicated subdomain and then define simple SPF records on each subdomain. This makes managing large numbers of sending services easier and bypasses the lookup limit, as each record is minimal.<\/li>\n\n\n\n<li><b>SPF record flattening tools:<\/b> Tools exist to flatten SPF records down to IP addresses or IP ranges, which can help deal with the lookup limit. However, this can <a href=\"https:\/\/dmarcian.com\/spf-flattening\/\" target=\"_tabs\" rel=\"noopener noreferrer\">introduce new issues<\/a>, so dedicated subdomains may be preferred.<\/li>\n<\/ul>\n\n<h2 class=\"wp-block-heading\">Configuring DKIM<\/h2>\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/www.mailgun.com\/pt\/blog\/deliverability\/entender-dkim-como-funciona\/\" target=\"_tabs\" rel=\"noopener noreferrer\">DKIM<\/a> is an email authentication protocol that allows you to attach a digital signature to emails to allow for the identification and prevention of tampering. When an email is signed with DKIM, the following flow takes place:<\/p>\n\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" class=\"wp-image-3956\" width=\"1332\" height=\"1678\" src=\"https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/Screenshot_2025-02-20_at_9.11.23_AM.png\" alt=\"DKIM signature flow\" srcset=\"https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/Screenshot_2025-02-20_at_9.11.23_AM.png 1332w, https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/Screenshot_2025-02-20_at_9.11.23_AM-238x300.png 238w, https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/Screenshot_2025-02-20_at_9.11.23_AM-768x967.png 768w, https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/Screenshot_2025-02-20_at_9.11.23_AM-813x1024.png 813w, https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/Screenshot_2025-02-20_at_9.11.23_AM-1219x1536.png 1219w\" sizes=\"(max-width: 1332px) 100vw, 1332px\" \/><\/figure>\n\n<p class=\"wp-block-paragraph\">DKIM&#8217;s primary purpose is to prove that an email has not been tampered with and has arrived with the original content sent by the signing sender server. However, as a side effect, it can also help reduce the odds of the email being marked as spam based on content heuristics. This is because consistently validating emails with DKIM will improve your sender reputation over time, which will ultimately reduce spam filters&#8217; dependence on content-based spam flags.<\/p>\n\n<p class=\"wp-block-paragraph\">Checking if you have DKIM configured on a domain is slightly more complex than checking SPF because the DNS record for DKIM exists on a special subdomain that uses an arbitrary &#8220;selector.&#8221; Since the selector can be any alphanumeric string, the only way to determine which one to check is the same method used by the receiving server \u2013 by examining the <code>DKIM-Signature<\/code> header in the email. If you look at the raw content of an email that was signed with DKIM and search for this header, you&#8217;ll see something like this:<\/p>\n\n<p class=\"wp-block-paragraph\"><code>DKIM-Signature: v=1; a=rsa-sha256; c=relaxed\/relaxed; d=example.com; s=dkim; t=1672618838; h=from:from:reply-to:subject:subject:date:date:message-id:message-id:to:to:cc:mime-version:mime-version:content-type:content-type:content-transfer-encoding:content-transfer-encoding:in-reply-to:in-reply-to:references:references; bh=RKkrHxZminSEI0rxtiN3+8wFv6vKCozhmrATLVIZFcw=; b=lndiW4xUpmGqbbIxjiER0FEa67zPqpmW+MqrmMcvuvgd+Gta851Jd+lU4yJ4rmiCHSPfRA gDh+ZsPC8UWZ8U5cfg14uFuvtxUWr6N9Ncy1mntgz7ZNhMIovpknioDIOLYD2wM72mglVP BAeTy2oHVZ0B6tBQqC4\/hePtzyF0dnU=<\/code><\/p>\n\n<p class=\"wp-block-paragraph\">This header is made up of several components:<\/p>\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Comp\u00adone\u00adnt<\/th><th>Purp\u00adose<\/th><th>Exam\u00adple Valu\u00ade<\/th><\/tr><\/thead><tbody><tr><td>\nv\n<\/td><td>DKIM\u00ad vers\u00adion<\/td><td>v=1<\/td><\/tr><tr><td>a<\/td><td>Sign\u00ading algo\u00adrithm<\/td><td>rsa-sha256<\/td><\/tr><tr><td>c<\/td><td>Cano\u00adnicalization meth\u00adod<\/td><td>rel\u00adax\u00aded<\/td><\/tr><tr><td>d<\/td><td>Sign\u00ading doma\u00adin<\/td><td>exa\u00admp\u00adle<\/td><\/tr><tr><td>s<\/td><td>Sele\u00adctor for DNS publ\u00adic key look\u00adup<\/td><td>dkim<\/td><\/tr><tr><td>t<\/td><td>Tim\u00ades\u00adta\u00admp<\/td><td>1672618838<\/td><\/tr><tr><td>h<\/td><td>Head\u00aders incl\u00aduded in the sign\u00adature<\/td><td>from:reply-to:subject:date:message-id:to:cc:mime-version:content-type:content-transfer-encoding:in-reply-to:references<\/td><\/tr><tr><td>bh<\/td><td>Body\u00ad hash\u00ad<\/td><td>RKk\u00adrH\u00adxZ\u00adminSEI0<\/td><\/tr><tr><td>b<\/td><td>Cryp\u00adtographic sign\u00adature<\/td><td>lnd\u00adiW\u00ad4x\u00adUpmGq<\/td><\/tr><\/tbody><\/table><\/figure>\n\n<p class=\"wp-block-paragraph\">The receiving server needs this information to verify the email. It recomputes the email&#8217;s hash, including the headers specified in the h component, and retrieves the public key from the DNS record using the selector in the s component (dkim, in this case). When the selector is combined with the sender domain, the full DKIM key location would look like this: <code>._domainkey..<\/code><\/p>\n\n<p class=\"wp-block-paragraph\">For instance, if your selector was <code>dkim<\/code> and your domain was <code>example.com<\/code>, the DNS record would be located at <code>dkim._domainkey.example.com<\/code>. In this case, you could view the DNS record either using an <a href=\"https:\/\/dkimcore.org\/c\/keycheck\" target=\"_tabs\" rel=\"noopener noreferrer\">online tool<\/a> or <code>dig:<\/code><\/p>\n\n<p class=\"wp-block-paragraph\"><code>$ dig +short TXT dkim._domainkey.example.com<\/code><\/p>\n\n<p class=\"wp-block-paragraph\">If a record is found, your output will look like this:<\/p>\n\n<p class=\"wp-block-paragraph\"><code>v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQE...<\/code><\/p>\n\n<p class=\"wp-block-paragraph\">This record has three components:<\/p>\n\n<ul class=\"wp-block-list\">\n<li><code>v=DKIM1<\/code> specifies the DKIM version.<\/li>\n\n\n\n<li><code>k=rsa<\/code> defines the key type (RSA is standard).<\/li>\n\n\n\n<li><code>p=<\/code> contains the public key.<\/li>\n<\/ul>\n\n<h3 class=\"wp-block-heading\">Creating DKIM keys<\/h3>\n\n<p class=\"wp-block-paragraph\">When setting up DKIM, you need to generate a key pair consisting of a public and private key. The sending server uses the private key to sign emails, and the public key is published as a DNS record and used by the receiving server to validate those emails.<\/p>\n\n<p class=\"wp-block-paragraph\">Typically, if you&#8217;re setting up DKIM for an email-sending service, the service generates the keys on your behalf (or allows you to use your own, in some cases). For instance, Mailgun provides <a href=\"https:\/\/www.mailgun.com\/pt\/blog\/deliverability\/entender-dkim-como-funciona\/#chapter-5\" target=\"_tabs\" rel=\"noopener noreferrer\">step-by-step instructions<\/a> on how to generate and configure DKIM records for a given domain. However, it&#8217;s good to understand the underlying process, and in some cases, you may prefer to take full custody of the key pair.<\/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\"> It\u2019s a good practice to keep your email program secure by regularly rotating your DKIM keys, learn how in our <a href='https:\/\/www.mailgun.com\/pt\/blog\/email\/dkim-key-rotation\/'>key rotation guide.<\/a><\/div>\r\n    <\/div>\r\n\n<p class=\"wp-block-paragraph\">For this example, you can generate the key pair using a tool like <code>openssl<\/code>. First, generate the private key like this:<\/p>\n\n<p class=\"wp-block-paragraph\"><code>openssl genpkey -algorithm RSA -out private.key -pkeyopt rsa_keygen_bits:2048<\/code><\/p>\n\n<p class=\"wp-block-paragraph\">This command creates a file called <code>private.key<\/code> containing the RSA private key. Next, you can use this private key with <code>openssl<\/code> to create the public key:<\/p>\n\n<p class=\"wp-block-paragraph\"><code>openssl rsa -pubout -in private.key -out public.key<\/code><\/p>\n\n<p class=\"wp-block-paragraph\">Once you have the public key, you can create the DNS record for it with your selector of choice (dkim, in this case). The DNS record would look like this:<\/p>\n\n<p class=\"wp-block-paragraph\"><code>dkim._domainkey.example.com. IN TXT \"v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQE...etc\"<\/code><\/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\"> Mailgun has <a href='https:\/\/help.mailgun.com\/hc\/en-us\/sections\/360006038234-DNS'>help center guides<\/a> that provide guidance on adding records for common DNS providers.<\/div>\r\n    <\/div>\r\n\n<p class=\"wp-block-paragraph\">Similar to SPF, DKIM can introduce complexity for your developers. Challenges may arise, such as mismanaged private keys and conflicts between sender services.<\/p>\n\n<p class=\"wp-block-paragraph\">The protection DKIM offers is only as good as your key management practices. A compromised signing key could expose you to bad actors and spoofed emails. As such, you must exercise good security hygiene when dealing with private keys, storing them securely with a service such as AWS Secrets Manager or HashiCorp Vault. Likewise, it&#8217;s often a good idea to rotate signing keys regularly, since this limits the potential impact of a compromised key. The fact that DKIM selectors are arbitrary is useful here, as you can start sending emails with a new selector, signed with a new private key, while you phase out your old key pair.<\/p>\n\n<h2 class=\"wp-block-heading\">Implementing DMARC<\/h2>\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/www.mailgun.com\/pt\/blog\/deliverability\/implementar-dmarc\/\" target=\"_tabs\" rel=\"noopener noreferrer\">DMARC<\/a> is another email authentication protocol designed to help mitigate spoofing, phishing, and spam. DMARC builds on top of SPF and DKIM. Specifically, DMARC uses SPF and DKIM to perform checks on incoming emails and enforce the defined DMARC policy in accordance with the outcome of those checks.<\/p>\n\n<p class=\"wp-block-paragraph\">DMARC also performs an alignment check for SPF and DKIM, ensuring that the domain specified by those mechanisms also matches the domain in the from: header of the email, further tightening things up to prevent spoofing.<\/p>\n\n<p class=\"wp-block-paragraph\">DMARC records are published at a well-known subdomain<code> (_dmarc)<\/code> of your sending domain. For instance, if you wanted to check the DMARC record of <code>example.com<\/code> with <code>dig<\/code>, you&#8217;d run a command like this:<\/p>\n\n<p class=\"wp-block-paragraph\"><code>$ dig +short TXT _dmarc.example.com<\/code><\/p>\n\n<p class=\"wp-block-paragraph\">If you had a record configured for this domain, your output would look like this:<\/p>\n\n<p class=\"wp-block-paragraph\"><code>\"v=DMARC1; p=quarantine; pct=100; adkim=s; aspf=s\"<\/code><\/p>\n\n<p class=\"wp-block-paragraph\">This example record contains five components. However, there are more possible components a DMARC record can include:<\/p>\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Comp\u00adone\u00adnt<\/th><th>Purp\u00adose<\/th><th>Exam\u00adple Valu\u00ade(s)<\/th><\/tr><\/thead><tbody><tr><td>v<\/td><td>Vers\u00adion of DMAR\u00adC<\/td><td>Alwa\u00adys DMAR\u00adC1 curr\u00adently<\/td><\/tr><tr><td>p<\/td><td>Poli\u00adcy to appl\u00ady for nonc\u00adompliant emai\u00adls<\/td><td>Poss\u00adible valu\u00ades are none\u00ad, quar\u00adantine, or reje\u00adct<\/td><\/tr><tr><td>rua<\/td><td>Repo\u00adrting URI for aggr\u00adegate repo\u00adrts (ema\u00adil addr\u00adesses wher\u00ade repo\u00adrts are sent\u00ad)<\/td><td>mai\u00adlt\u00ado<\/td><\/tr><tr><td>ruf<\/td><td>Repo\u00adrting URI for fore\u00adnsic repo\u00adrts (ema\u00adil addr\u00adesses wher\u00ade deta\u00adiled repo\u00adrts are sent\u00ad)<\/td><td>mai\u00adlt\u00ado<\/td><\/tr><tr><td>adk\u00adim<\/td><td>DKIM\u00ad alig\u00adnment mode\u00ad<\/td><td>r for rela\u00adxed, s for stri\u00adct<\/td><\/tr><tr><td>aspf<\/td><td>SPF alig\u00adnment mode\u00ad<\/td><td>r for rela\u00adxed, s for stri\u00adct<\/td><\/tr><tr><td>pct<\/td><td>Perc\u00adentage of emai\u00adls subj\u00adected to DMAR\u00adC poli\u00adcy<\/td><td>0\u2013100<\/td><\/tr><tr><td>fo<\/td><td>Fore\u00adnsic repo\u00adrting opti\u00adons<\/td><td>0 for &#8220;all\u00ad fail\u00adures,&#8221; 1 for &#8220;DKI\u00adM fail\u00adure only\u00ad&#8221;<\/td><\/tr><\/tbody><\/table><\/figure>\n\n<p class=\"wp-block-paragraph\">A key concept for DMARC is the idea of &#8220;alignment.&#8221; Alignment determines how closely the domains used in SPF and DKIM need to match the domain in the email&#8217;s <code>from:<\/code> header. The alignment mode is controlled by the <code>adkim<\/code> and <code>aspf<\/code> components of the DMARC record, and they have the following meanings:<\/p>\n\n<ul class=\"wp-block-list\">\n<li><b>DKIM alignment:<\/b>\n<ul class=\"wp-block-list\">\n<li>Strict <code>(adkim=s):<\/code> The domain in the DKIM signature (d=) must match <i>exactly<\/i> with the <code>from:<\/code> address.<\/li>\n\n\n\n<li>Relaxed <code>(adkim=r): <\/code>The domain in the DKIM signature must share the same <i>organizational domain<\/i> as the domain in the <code>from: <\/code>address. This means subdomains are permitted. <\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><b>SPF alignment:<\/b>\n<ul class=\"wp-block-list\">\n<li>Strict <code>(aspf=s): <\/code>The domain in the SPF <code>Return-Path<\/code> must match <i>exactly<\/i> with the <code>from: address<\/code>.<\/li>\n\n\n\n<li>Relaxed <code>(aspf=r): <\/code>The domain in the SPF <code>Return-Path<\/code> must share the same <i>organizational domain<\/i> as the domain in the <code>from:<\/code> address. Subdomains are permitted.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n<p class=\"wp-block-paragraph\">Assuming SPF, DKIM, and DMARC are all configured correctly when an email is sent, the following sequence of events will take place:<\/p>\n\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" class=\"wp-image-3960\" width=\"2054\" height=\"1428\" src=\"https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/Screenshot_2025-02-20_at_9.17.05_AM__1_.png\" alt=\"Assuming SPF, DKIM, and DMARC are all configured correctly when an email is sent, the following sequence of events will take place\" srcset=\"https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/Screenshot_2025-02-20_at_9.17.05_AM__1_.png 2054w, https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/Screenshot_2025-02-20_at_9.17.05_AM__1_-300x209.png 300w, https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/Screenshot_2025-02-20_at_9.17.05_AM__1_-768x534.png 768w, https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/Screenshot_2025-02-20_at_9.17.05_AM__1_-1024x712.png 1024w, https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/Screenshot_2025-02-20_at_9.17.05_AM__1_-1536x1068.png 1536w, https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/Screenshot_2025-02-20_at_9.17.05_AM__1_-2048x1424.png 2048w\" sizes=\"(max-width: 2054px) 100vw, 2054px\" \/><\/figure>\n\n<p class=\"wp-block-paragraph\">DMARC is considered to have passed if <i>either<\/i> SPF or DKIM is valid and aligned. If both of them are invalid and\/or unaligned, then DMARC is considered to have failed, and the DMARC policy is enforced.<\/p>\n\n<p class=\"wp-block-paragraph\">The policy is defined by the <code>p= <\/code>component and has three possible modes:<\/p>\n\n<ul class=\"wp-block-list\">\n<li><code>p=none:<\/code> No action is taken, but reports are generated.<\/li>\n\n\n\n<li><code>p=quarantine:<\/code> Emails are treated as suspicious and are sent to the spam folder.<\/li>\n\n\n\n<li><code>p=reject:<\/code> Emails are rejected and not delivered.<\/li>\n<\/ul>\n\n<p class=\"wp-block-paragraph\">Remember, the DMARC policy you define does not affect your incoming emails; it tells the rest of the world what <i>they<\/i> should do with unauthenticated emails that claim to have come from your domain. This includes the aggregate <code>(rua)<\/code> and forensic <code>(ruf)<\/code> report tags, which specify where receiving servers should send compliance reports regarding unauthenticated emails claiming to come from your domain.<\/p>\n\n<p class=\"wp-block-paragraph\">It&#8217;s important to set these options and make sure the inboxes they point to are actively monitored, as these reports are invaluable in understanding your domain&#8217;s email usage, identifying unauthorized senders, and refining your authentication settings.<\/p>\n\n<p class=\"wp-block-paragraph\">As with the other email authentication mechanisms that have been covered, setting up your DMARC record is simply a matter of creating the appropriate TXT DNS record, which would look something like this:<\/p>\n\n<p class=\"wp-block-paragraph\"><code>_dmarc.example.com IN TXT \"v=DMARC1; p=reject; rua=mailto:dmarc-reports@example.com; ruf=mailto:dmarc-failures@example.com; aspf=s; adkim=s; pct=100\"<\/code><\/p>\n\n<p class=\"wp-block-paragraph\">Be mindful that if you&#8217;re setting up email authentication for a domain for the first time, it can be beneficial to ease into it. Rather than starting with strict enforcement <code>(p=reject)<\/code>, you may want to start with gradual enforcement <code>(p=none)<\/code> and monitor the DMARC reports to make sure your emails are passing validation as expected. Otherwise, a misconfiguration could impact the deliverability of your legitimate emails.<\/p>\n\n<h2 class=\"wp-block-heading\">Wrapping up<\/h2>\n\n<p class=\"wp-block-paragraph\">Email authentication protocols like SPF, DKIM, and DMARC play a major role in ensuring your emails&#8217; deliverability and protecting your domains&#8217; reputation. Properly configured email authentication builds trust and enhances your sender reputation, reducing the chances of your emails being marked as spam.<\/p>\n\n<p class=\"wp-block-paragraph\">If you haven&#8217;t configured or recently reviewed your email authentication settings, you should take some time to review and implement these steps for your email infrastructure. Remember to actively monitor your DMARC reports and test your emails&#8217; deliverability to ensure everything is configured correctly. If you need a reliable resource for testing and managing your email deliverability, <a href=\"https:\/\/www.mailgun.com\/blog\/deliverability\/testing-email-deliverability\/\" target=\"_tabs\" rel=\"noopener noreferrer\">Mailgun has you covered<\/a>.<\/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_75a6e1a58ca3fc3c13c961c9ec5b1f45\">\r\n                    <p class=\"text-uppercase section-caption text-body-color\">\r\n                Sign Up            <\/p>\r\n                            <p class=\"h4 text-accent fw-bold\" id=\"banner-block-block_75a6e1a58ca3fc3c13c961c9ec5b1f45\">\r\n                It&#8217;s easy to get started. And it&#8217;s free.            <\/p>\r\n                            <div class=\"mb-0 text-body-color\">\r\n                                    <div class=\"content-body mb-0 text-body-color\">See what you can accomplish with the world\u2019s best email delivery platform.<\/div>\r\n                            <\/div>\r\n        \r\n        <div class=\"text-start mt-5\"><a href=\"https:\/\/signup.mailgun.com\/new\/signup\"  class=\"btn btn-secondary\" >Get started<\/a><\/div>\r\n    <\/aside>\r\n\r\n","protected":false},"excerpt":{"rendered":"<p>Protocolos de autentica\u00e7\u00e3o de e-mail, como SPF, DKIM e DMARC, t\u00eam a fun\u00e7\u00e3o crucial de proteger seus e-mails contra spoofing e melhorar a entregabilidade. Veja como configur\u00e1-los e mant\u00ea-los funcionando.<\/p>\n","protected":false},"author":8,"featured_media":3952,"menu_order":0,"template":"","meta":{"_acf_changed":false,"footnotes":""},"blog_category":[19],"class_list":["post-20054","blog","type-blog","status-publish","has-post-thumbnail","hentry","blog_category-dev-life"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.4 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Implementa\u00e7\u00e3o de SPF, DKIM e DMARC para entrega confi\u00e1vel de e-mail - Transactional Email API Service For Developers | Mailgun<\/title>\n<meta name=\"description\" content=\"Profissionais de desenvolvimento, saibam como configurar o SPF, o DKIM e o DMARC para autenticar e-mails, evitar spoofing e melhorar a entregabilidade para as suas aplica\u00e7\u00f5es.\" \/>\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\/pt\/blog\/dev-life\/como-configurar-autenticacao-e-mail\/\" \/>\n<meta property=\"og:locale\" content=\"pt_BR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Implementa\u00e7\u00e3o de SPF, DKIM e DMARC para entrega confi\u00e1vel de e-mail - Transactional Email API Service For Developers | Mailgun\" \/>\n<meta property=\"og:description\" content=\"Profissionais de desenvolvimento, saibam como configurar o SPF, o DKIM e o DMARC para autenticar e-mails, evitar spoofing e melhorar a entregabilidade para as suas aplica\u00e7\u00f5es.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.mailgun.com\/pt\/blog\/dev-life\/como-configurar-autenticacao-e-mail\/\" \/>\n<meta property=\"og:site_name\" content=\"Transactional Email API Service For Developers | Mailgun\" \/>\n<meta property=\"article:modified_time\" content=\"2026-09-15T10:56:43+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/MG-Blog-Dev-Life.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=\"11 minutos\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.mailgun.com\\\/pt\\\/blog\\\/dev-life\\\/como-configurar-autenticacao-e-mail\\\/\",\"url\":\"https:\\\/\\\/www.mailgun.com\\\/pt\\\/blog\\\/dev-life\\\/como-configurar-autenticacao-e-mail\\\/\",\"name\":\"Implementa\u00e7\u00e3o de SPF, DKIM e DMARC para entrega confi\u00e1vel de e-mail - Transactional Email API Service For Developers | Mailgun\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.mailgun.com\\\/pt\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.mailgun.com\\\/pt\\\/blog\\\/dev-life\\\/como-configurar-autenticacao-e-mail\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.mailgun.com\\\/pt\\\/blog\\\/dev-life\\\/como-configurar-autenticacao-e-mail\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.mailgun.com\\\/wp-content\\\/uploads\\\/2025\\\/07\\\/MG-Blog-Dev-Life.png\",\"datePublished\":\"2025-05-14T00:00:00+00:00\",\"dateModified\":\"2026-09-15T10:56:43+00:00\",\"description\":\"Profissionais de desenvolvimento, saibam como configurar o SPF, o DKIM e o DMARC para autenticar e-mails, evitar spoofing e melhorar a entregabilidade para as suas aplica\u00e7\u00f5es.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.mailgun.com\\\/pt\\\/blog\\\/dev-life\\\/como-configurar-autenticacao-e-mail\\\/#breadcrumb\"},\"inLanguage\":\"pt-BR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.mailgun.com\\\/pt\\\/blog\\\/dev-life\\\/como-configurar-autenticacao-e-mail\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"pt-BR\",\"@id\":\"https:\\\/\\\/www.mailgun.com\\\/pt\\\/blog\\\/dev-life\\\/como-configurar-autenticacao-e-mail\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.mailgun.com\\\/wp-content\\\/uploads\\\/2025\\\/07\\\/MG-Blog-Dev-Life.png\",\"contentUrl\":\"https:\\\/\\\/www.mailgun.com\\\/wp-content\\\/uploads\\\/2025\\\/07\\\/MG-Blog-Dev-Life.png\",\"width\":720,\"height\":448},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.mailgun.com\\\/pt\\\/blog\\\/dev-life\\\/como-configurar-autenticacao-e-mail\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.mailgun.com\\\/pt\\\/inicio\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Blog\",\"item\":\"https:\\\/\\\/www.mailgun.com\\\/pt\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Como autenticar seu e-mail para ter melhores taxas de entrega\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.mailgun.com\\\/pt\\\/#website\",\"url\":\"https:\\\/\\\/www.mailgun.com\\\/pt\\\/\",\"name\":\"Transactional Email API Service For Developers | Mailgun\",\"description\":\"Poderosas APIs de e-mail transacional que permitem a voc\u00ea enviar, receber e rastrear e-mails, criadas com os desenvolvedores em mente. Saiba mais hoje mesmo!\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.mailgun.com\\\/pt\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.mailgun.com\\\/pt\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"pt-BR\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.mailgun.com\\\/pt\\\/#organization\",\"name\":\"Transactional Email API Service For Developers | Mailgun\",\"url\":\"https:\\\/\\\/www.mailgun.com\\\/pt\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pt-BR\",\"@id\":\"https:\\\/\\\/www.mailgun.com\\\/pt\\\/#\\\/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\\\/pt\\\/#\\\/schema\\\/logo\\\/image\\\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Implementa\u00e7\u00e3o de SPF, DKIM e DMARC para entrega confi\u00e1vel de e-mail - Transactional Email API Service For Developers | Mailgun","description":"Profissionais de desenvolvimento, saibam como configurar o SPF, o DKIM e o DMARC para autenticar e-mails, evitar spoofing e melhorar a entregabilidade para as suas aplica\u00e7\u00f5es.","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\/pt\/blog\/dev-life\/como-configurar-autenticacao-e-mail\/","og_locale":"pt_BR","og_type":"article","og_title":"Implementa\u00e7\u00e3o de SPF, DKIM e DMARC para entrega confi\u00e1vel de e-mail - Transactional Email API Service For Developers | Mailgun","og_description":"Profissionais de desenvolvimento, saibam como configurar o SPF, o DKIM e o DMARC para autenticar e-mails, evitar spoofing e melhorar a entregabilidade para as suas aplica\u00e7\u00f5es.","og_url":"https:\/\/www.mailgun.com\/pt\/blog\/dev-life\/como-configurar-autenticacao-e-mail\/","og_site_name":"Transactional Email API Service For Developers | Mailgun","article_modified_time":"2026-09-15T10:56:43+00:00","og_image":[{"width":720,"height":448,"url":"https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/MG-Blog-Dev-Life.png","type":"image\/png"}],"twitter_card":"summary_large_image","twitter_misc":{"Est. reading time":"11 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/www.mailgun.com\/pt\/blog\/dev-life\/como-configurar-autenticacao-e-mail\/","url":"https:\/\/www.mailgun.com\/pt\/blog\/dev-life\/como-configurar-autenticacao-e-mail\/","name":"Implementa\u00e7\u00e3o de SPF, DKIM e DMARC para entrega confi\u00e1vel de e-mail - Transactional Email API Service For Developers | Mailgun","isPartOf":{"@id":"https:\/\/www.mailgun.com\/pt\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.mailgun.com\/pt\/blog\/dev-life\/como-configurar-autenticacao-e-mail\/#primaryimage"},"image":{"@id":"https:\/\/www.mailgun.com\/pt\/blog\/dev-life\/como-configurar-autenticacao-e-mail\/#primaryimage"},"thumbnailUrl":"https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/MG-Blog-Dev-Life.png","datePublished":"2025-05-14T00:00:00+00:00","dateModified":"2026-09-15T10:56:43+00:00","description":"Profissionais de desenvolvimento, saibam como configurar o SPF, o DKIM e o DMARC para autenticar e-mails, evitar spoofing e melhorar a entregabilidade para as suas aplica\u00e7\u00f5es.","breadcrumb":{"@id":"https:\/\/www.mailgun.com\/pt\/blog\/dev-life\/como-configurar-autenticacao-e-mail\/#breadcrumb"},"inLanguage":"pt-BR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.mailgun.com\/pt\/blog\/dev-life\/como-configurar-autenticacao-e-mail\/"]}]},{"@type":"ImageObject","inLanguage":"pt-BR","@id":"https:\/\/www.mailgun.com\/pt\/blog\/dev-life\/como-configurar-autenticacao-e-mail\/#primaryimage","url":"https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/MG-Blog-Dev-Life.png","contentUrl":"https:\/\/www.mailgun.com\/wp-content\/uploads\/2025\/07\/MG-Blog-Dev-Life.png","width":720,"height":448},{"@type":"BreadcrumbList","@id":"https:\/\/www.mailgun.com\/pt\/blog\/dev-life\/como-configurar-autenticacao-e-mail\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.mailgun.com\/pt\/inicio\/"},{"@type":"ListItem","position":2,"name":"Blog","item":"https:\/\/www.mailgun.com\/pt\/blog\/"},{"@type":"ListItem","position":3,"name":"Como autenticar seu e-mail para ter melhores taxas de entrega"}]},{"@type":"WebSite","@id":"https:\/\/www.mailgun.com\/pt\/#website","url":"https:\/\/www.mailgun.com\/pt\/","name":"Transactional Email API Service For Developers | Mailgun","description":"Poderosas APIs de e-mail transacional que permitem a voc\u00ea enviar, receber e rastrear e-mails, criadas com os desenvolvedores em mente. Saiba mais hoje mesmo!","publisher":{"@id":"https:\/\/www.mailgun.com\/pt\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.mailgun.com\/pt\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"pt-BR"},{"@type":"Organization","@id":"https:\/\/www.mailgun.com\/pt\/#organization","name":"Transactional Email API Service For Developers | Mailgun","url":"https:\/\/www.mailgun.com\/pt\/","logo":{"@type":"ImageObject","inLanguage":"pt-BR","@id":"https:\/\/www.mailgun.com\/pt\/#\/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\/pt\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/www.mailgun.com\/pt\/wp-json\/wp\/v2\/blog\/20054","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.mailgun.com\/pt\/wp-json\/wp\/v2\/blog"}],"about":[{"href":"https:\/\/www.mailgun.com\/pt\/wp-json\/wp\/v2\/types\/blog"}],"author":[{"embeddable":true,"href":"https:\/\/www.mailgun.com\/pt\/wp-json\/wp\/v2\/users\/8"}],"version-history":[{"count":3,"href":"https:\/\/www.mailgun.com\/pt\/wp-json\/wp\/v2\/blog\/20054\/revisions"}],"predecessor-version":[{"id":21406,"href":"https:\/\/www.mailgun.com\/pt\/wp-json\/wp\/v2\/blog\/20054\/revisions\/21406"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.mailgun.com\/pt\/wp-json\/wp\/v2\/media\/3952"}],"wp:attachment":[{"href":"https:\/\/www.mailgun.com\/pt\/wp-json\/wp\/v2\/media?parent=20054"}],"wp:term":[{"taxonomy":"blog_category","embeddable":true,"href":"https:\/\/www.mailgun.com\/pt\/wp-json\/wp\/v2\/blog_category?post=20054"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}