Check NAPTR records instantly across global resolvers to validate your advanced URI and telecom routing rules.
NAPTR records are complex DNS records primarily used in Internet Telephony (VoIP) and ENUM (E.164 Number Mapping) to translate phone numbers and services into internet addresses. Enter your domain (or reversed ENUM domain) above to query its active NAPTR rules and verify your telecom routing.
SIP+D2U for SIP over UDP). The Regular Expression (Regex) field is where the actual translation (like turning a phone number into a SIP URI) happens.NAPTR records are notoriously difficult to read. Learn what ENUM is, how the Regular Expressions work, and how NAPTR relates to SRV records.
Read the NAPTR Record WikiNAPTR records provide complex rewrite rules, often used in SIP, ENUM, or service discovery chains. They specify order, preference, flags, service, and replacement values that guide how a client should rewrite or resolve a domain. This lookup helps you verify the rule set and ensure the correct ordering.
Common issues include incorrect ordering, malformed regular expressions, or mismatched service fields. Because NAPTR is advanced and flexible, small errors can break service discovery. Verify the rule sequence and then confirm the next lookup step, usually SRV or URI based on the flags.
If you need related checks, try SRV record validator and TXT record check tool.
Order defines the sequence in which rules are processed. Preference is used to rank rules with the same order. Lower values are tried first.
Flags describe the next step, such as S for SRV lookup or U for a URI. The client behavior depends on the flag.
Check the regex syntax, service field, and replacement. Also verify the order and preference values.
Often yes. NAPTR can point to SRV records for service discovery.
Not always. SIP can use SRV and A/AAAA directly, but NAPTR can provide a more flexible discovery chain.
NAPTR is cached like other records. Use lower TTLs while adjusting complex rule sets.