--- title: "Resolving “The DNS Record Type 99 (SPF) Has Been Deprecated” Error | AutoSPF" description: "As per RFC 7208 Section 3.1, the developers felt the necessity to assign a new DNS RR type." image: "https://autospf.com/og/blog/resolving-dns-record-type-99-spf-has-been-deprecated-error.png" canonical: "https://autospf.com/blog/resolving-dns-record-type-99-spf-has-been-deprecated-error/" --- Quick Answer As per RFC 7208 Section 3.1, the developers felt the necessity to assign a new DNS RR type. However, in 2014, it was deprecated as they discovered that TXT type RR was a better choice for SPF records. Today, SPF records must only be published as a DNS TXT RR; Share [ ](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fautospf.com%2Fblog%2Fresolving-dns-record-type-99-spf-has-been-deprecated-error%2F "Share on LinkedIn") [ ](https://twitter.com/intent/tweet?text=Resolving%20%E2%80%9CThe%20DNS%20Record%20Type%2099%20%28SPF%29%20Has%20Been%20Deprecated%E2%80%9D%20Error&url=https%3A%2F%2Fautospf.com%2Fblog%2Fresolving-dns-record-type-99-spf-has-been-deprecated-error%2F "Share on X/Twitter") [ ](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fautospf.com%2Fblog%2Fresolving-dns-record-type-99-spf-has-been-deprecated-error%2F "Share on Facebook") [ ](https://reddit.com/submit?url=https%3A%2F%2Fautospf.com%2Fblog%2Fresolving-dns-record-type-99-spf-has-been-deprecated-error%2F&title=Resolving%20%E2%80%9CThe%20DNS%20Record%20Type%2099%20%28SPF%29%20Has%20Been%20Deprecated%E2%80%9D%20Error "Share on Reddit") [ ](mailto:?subject=Resolving%20%E2%80%9CThe%20DNS%20Record%20Type%2099%20%28SPF%29%20Has%20Been%20Deprecated%E2%80%9D%20Error&body=Check out this article: https%3A%2F%2Fautospf.com%2Fblog%2Fresolving-dns-record-type-99-spf-has-been-deprecated-error%2F "Share via Email") ![DNS Record Type](https://media.mailhop.org/autospf/images/2023/12/spf-record-checkerck-1.jpg) As per RFC 7208 Section 3.1, the developers felt the necessity to assign a new DNS RR type. However, in 2014, it was deprecated as they discovered that [TXT type](https://en.wikipedia.org/wiki/TXT%5Frecord) RR was a better choice for [SPF records](/blog/spf-records-benefits-uses-and-generation/). _Per [RFC 7208](https://datatracker.ietf.org/doc/html/rfc7208), SPF evaluation is capped at 10 DNS mechanism lookups and 2 void lookups per check - exceeding either limit produces a `PermError` that fails authentication for every message from the domain._ _Today, SPF records must only be published as a DNS TXT RR; otherwise, it will encounter the “The DNS Record Type 99 (SPF) Has Been Deprecated” error._ ## Why Was the ‘SPF’ Record type Deprecated? During the initial phase, the regulations were tighter, which triggered the developing team to assign new DNS RR types for SPF records. Many years later, the scenario has changed, and the regulations have been relaxed, leading to the [depredation of the SPF record type](https://mxtoolbox.com/problem/spf/spf-record-deprecated). Another reason for this decision was its failure to align well with [DNS servers](https://www.cdnetworks.com/web-performance-blog/what-is-a-dns-server/) and provisioning systems. However, some domain providers still offer the ‘SPF’ record type. So, if everything seems fine with your record, but it is based on the SPF type, then it’s likely to explore the “The DNS Record Type 99 (SPF) Has Been Deprecated” error, which would make your record invalid. ## How Do You Create an SPF Record of TXT Type? Start by gathering an extensive list of all the [IP addresses](https://www.techtarget.com/whatis/definition/IP-address-Internet-Protocol-Address) and email servers that are authorized to send messages as representatives of your organization and using your domain name. Don’t forget to include the sending sources of [third-party vendors](https://www.venminder.com/blog/who-considered-third-party-vendor) who send emails on your behalf. Also, consider adding ESPs and on-premises mail servers for a non-erroneous record and better email delivery. ### Steps to Generate a Record ![SPF record generator](https://media.mailhop.org/autospf/images/2023/12/spf-record-checker-5412.jpg) - After generating a list of reliable IP addresses, the next step is to use an [SPF record generator](/generative-ai-and-phishing-threats/spf-record-generator/) (online tool) to draft your domain’s SPF record by specifying the version number. As of now, there is only one SPF version, so it will always begin with v=spf1. - Use this tag as a prefix to all the IP addresses that you compiled in the first step, for example, v=spf1 ip4:123.345.567 -all, where 123.345.567 is the sending server’s IP address. Also, make sure that you follow this step for the third-party vendors that you included in the list. - End your record with either -all or \~all tag to specify [hardfail or softfail](/blog/spf-softfail-or-spf-hardfail/). ## Who is Responsible for Publishing the SPF Record On Your DNS? It’s usually the responsibility of your DNS manager to publish the SPF record generated using the above steps. This could be an internal position in your organization, or you can ask your [DNS provider](https://help.saleshandy.com/article/189-how-do-i-know-what-my-dns-provider-is) to help you with this. ## How Do You Verify Your Record? Once you have created a TXT record type for SPF to overcome the “The DNS Record Type 99 (SPF) Has Been Deprecated” error, you need to run it through a credible [SPF lookup](/spf-too-many-dns-lookups/solving-faqs-on-spf-lookups-and-their-role-in-email-authentication-and-security/) tool. This will ensure there are no syntactical and configurational errors that can impact your domain’s email delivery. ## We are Here to Help You With SPF Permerror On running your SPF TXT record through a lookup tool, if you encounter the ‘[too many DNS lookups](/spf-too-many-dns-lookups/)’ error, then try our automatic [SPF Flattening](/) tool. _It will replace IP addresses with their domains, thus eliminating the need for multiple lookups._ You can [speak to us](/book-a-demo/) today to resolve SPF issues. ## Topics [ SPF error ](/tags/spf-error/)[ SPF record ](/tags/spf-record/) ![Brad Slavin](https://media.mailhop.org/autospf/images/authors/brad-slavin.jpg) [ Brad Slavin ](/authors/brad-slavin/) General Manager Founder and General Manager of DuoCircle. Product strategy and commercial lead for AutoSPF's 2,000+ customer base. [LinkedIn Profile →](https://www.linkedin.com/in/bradslavin) ## Ready to get started? Try AutoSPF free — no credit card required. [ Book a Demo ](/book-a-demo/) ## Related Articles [ Advanced 5m Troubleshooting the ‘SPF alignment failed’ error for unaffected email authentication and delivery Jul 2, 2024 ](/blog/fixing-spf-alignment-failed-error-for-email-authentication-and-delivery/)[ Advanced 5m How to utilize DMARC reports to resolve SPF errors? Jun 13, 2025 ](/blog/how-to-utilize-dmarc-reports-to-resolve-spf-errors/)[ Advanced 6m Solving the 'Too Many DNS Lookup' Error Jan 5, 2024 ](/blog/solving-the-too-many-dns-lookup-error/)[ Advanced 7m SPF Best Practices for Protection Against Email Spoofing and Phishing; A Guide for CISOs Mar 15, 2024 ](/blog/spf-best-practices-cisos-guide-to-email-security/) ```json {"@context":"https://schema.org","@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897474","name":"AutoSPF","url":"https://autospf.com","logo":{"@type":"ImageObject","url":"https://autospf.com/images/autospf-logo.png"},"description":"Automatic SPF flattening and email authentication management. Resolve SPF lookup limits, flatten SPF records, and maintain email deliverability across all your domains.","parentOrganization":{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138883901","name":"DuoCircle LLC","url":"https://www.duocircle.com","sameAs":["https://www.wikidata.org/wiki/Q138883901","https://www.crunchbase.com/organization/duocircle-llc","https://www.linkedin.com/company/duocircle","https://github.com/duocircle"],"subOrganization":[{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138898167","name":"DMARC Report","url":"https://dmarcreport.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897474","name":"AutoSPF","url":"https://autospf.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897912","name":"Phish Protection","url":"https://www.phishprotection.com"}]},"sameAs":["https://www.wikidata.org/wiki/Q138897474","https://www.linkedin.com/company/autospf","https://x.com/autospf01","https://www.g2.com/products/autospf/reviews"],"contactPoint":{"@type":"ContactPoint","contactType":"customer support","url":"https://autospf.com/contact-us/"},"knowsAbout":["SPF Record Flattening","Sender Policy Framework","Email Authentication","DNS Management","DMARC","DKIM"]} ``` ```json {"@context":"https://schema.org","@type":"WebSite","name":"AutoSPF","url":"https://autospf.com","description":"Automatic SPF flattening and email authentication management. Resolve SPF lookup limits, flatten SPF records, and maintain email deliverability across all your domains.","publisher":{"@type":"Organization","name":"AutoSPF","url":"https://autospf.com","logo":{"@type":"ImageObject","url":"https://autospf.com/images/autospf-logo.png"},"description":"Automatic SPF flattening and email authentication management. Resolve SPF lookup limits, flatten SPF records, and maintain email deliverability across all your domains.","parentOrganization":{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138883901","name":"DuoCircle LLC","url":"https://www.duocircle.com","sameAs":["https://www.wikidata.org/wiki/Q138883901","https://www.crunchbase.com/organization/duocircle-llc","https://www.linkedin.com/company/duocircle","https://github.com/duocircle"],"subOrganization":[{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138898167","name":"DMARC Report","url":"https://dmarcreport.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897474","name":"AutoSPF","url":"https://autospf.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897912","name":"Phish Protection","url":"https://www.phishprotection.com"}]}}} ``` ```json {"@context":"https://schema.org","@type":"BlogPosting","headline":"Resolving “The DNS Record Type 99 (SPF) Has Been Deprecated” Error","description":"As per RFC 7208 Section 3.1, the developers felt the necessity to assign a new DNS RR type.","url":"https://autospf.com/blog/resolving-dns-record-type-99-spf-has-been-deprecated-error/","datePublished":"2023-12-08T14:56:07.000Z","dateModified":"2026-04-18T02:36:41.000Z","dateCreated":"2023-12-08T14:56:07.000Z","author":{"@type":"Person","@id":"https://autospf.com/authors/brad-slavin/#person","name":"Brad Slavin","url":"https://autospf.com/authors/brad-slavin/","jobTitle":"General Manager","description":"Brad Slavin is the founder and General Manager of DuoCircle, the company behind AutoSPF, DMARC Report, Phish Protection, and Mailhop. He founded DuoCircle in 2014 to solve the SPF 10-DNS-lookup problem at scale and has led the company's growth to 2,000+ customers. Brad's focus is product strategy, customer relationships, and the commercial and compliance side of email authentication (DPAs, SLAs, enterprise procurement) rather than hands-on DNS engineering.","image":"https://media.mailhop.org/autospf/images/authors/brad-slavin.jpg","knowsAbout":["Email Security Strategy","SaaS Product Management","Enterprise Compliance","Customer Success","Email Deliverability Business"],"worksFor":{"@type":"Organization","name":"AutoSPF","url":"https://autospf.com"},"sameAs":["https://www.linkedin.com/in/bradslavin"]},"publisher":{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897474","name":"AutoSPF","url":"https://autospf.com","logo":{"@type":"ImageObject","url":"https://autospf.com/images/autospf-logo.png"},"description":"Automatic SPF flattening and email authentication management. Resolve SPF lookup limits, flatten SPF records, and maintain email deliverability across all your domains.","parentOrganization":{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138883901","name":"DuoCircle LLC","url":"https://www.duocircle.com","sameAs":["https://www.wikidata.org/wiki/Q138883901","https://www.crunchbase.com/organization/duocircle-llc","https://www.linkedin.com/company/duocircle","https://github.com/duocircle"],"subOrganization":[{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138898167","name":"DMARC Report","url":"https://dmarcreport.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897474","name":"AutoSPF","url":"https://autospf.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897912","name":"Phish Protection","url":"https://www.phishprotection.com"}]},"sameAs":["https://www.wikidata.org/wiki/Q138897474","https://www.linkedin.com/company/autospf","https://x.com/autospf01","https://www.g2.com/products/autospf/reviews"],"contactPoint":{"@type":"ContactPoint","contactType":"customer support","url":"https://autospf.com/contact-us/"},"knowsAbout":["SPF Record Flattening","Sender Policy Framework","Email Authentication","DNS Management","DMARC","DKIM"]},"mainEntityOfPage":{"@type":"WebPage","@id":"https://autospf.com/blog/resolving-dns-record-type-99-spf-has-been-deprecated-error/"},"articleSection":"advanced","keywords":"SPF error, SPF record","wordCount":607,"image":{"@type":"ImageObject","url":"https://media.mailhop.org/autospf/images/2023/12/spf-record-checkerck-1.jpg","caption":"DNS Record Type","width":900,"height":583},"speakable":{"@type":"SpeakableSpecification","cssSelector":[".answer-block","h1"]}} ``` ```json {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://autospf.com/"},{"@type":"ListItem","position":2,"name":"Blog","item":"https://autospf.com/blog/"},{"@type":"ListItem","position":3,"name":"Advanced","item":"https://autospf.com/advanced/"},{"@type":"ListItem","position":4,"name":"Resolving “The DNS Record Type 99 (SPF) Has Been Deprecated” Error","item":"https://autospf.com/blog/resolving-dns-record-type-99-spf-has-been-deprecated-error/"}]} ```