
Telecom and messaging teams can use this during a routing investigation to review every NAPTR rule and spot an incorrect replacement.
Trace the NAPTR rules published by a domain, from order and preference to replacement, and understand the rewrite path it actually advertises.
A telecom team finds that calls routed through a domain do not follow the expected path. Reading the published NAPTR rules shows whether the advertised rewrite matches the service in use, and whether an outdated rule is still sitting in the zone.
The request is handled by the YOORfree server, which queries the public DNS itself for NAPTR rules and then passes the answer back to you. No file is uploaded with the query.
It describes how an identifier, such as a phone number or a service name, should be rewritten to another form or another target. It appears mainly in telecom and messaging routing chains.
Order ranks the rules by application sequence, and preference breaks ties between rules that share the same order. Reading both values together tells you which rule is considered first.
No, the page only reports what the domain publishes. You have to compare those rules with the ones your operator or service provider expects to see.