Obsolete: SPF policies must be published as TXT.
Type 99 was created for SPF during its experimental phase (RFC 4408) but saw little use. RFC 7208 (2014) says SPF records must be published as TXT only, that the alternative type has been discontinued, and that implementations are not to use type 99.
- Type
- SPF
- Code
- 99
- Defined in
- RFC 7208
- IANA description
- (obsolete for SPF publishing)
- Field: —
- Use TXT
How it works
If your DNS host offers an “SPF” record type in its menu, choose TXT instead; some hosts quietly create a TXT behind the scenes, others create a type 99 record that receivers ignore.
Example
example.com. 3600 IN TXT "v=spf1 include:_spf.example.net ~all" (publish as TXT, not type 99)
Example uses reserved documentation names and addresses (RFC 2606, RFC 5737, RFC 3849).
Common mistakes
- Publishing only a type 99 record, so receivers see no SPF at all.
How to check yours
To check yours, look up TXT at the domain and make sure exactly one record starts with v=spf1. If your DNS host’s menu still lists an SPF type, it is a leftover from the experimental days; choosing TXT is always correct, and receivers that follow RFC 7208 never read type 99.
For email
Publish SPF as TXT at the domain you send from.
Related record types
Sources
Sources
- IANA: Resource Record (RR) TYPEs registry · checked 5 Oct 2026
- RFC 7208 · checked 5 Oct 2026