Query DNS data with DNS.NFUse DNS lookup, reverse tools, and API endpoints for fast diagnostics.
DNSRDNSREVERSEAPI

API & Documentation

Live reference for DNS.NF endpoints, record types, and usage examples. Base URL: https://api.dns.nf

DNS Lookup: 30 req/min per IP rDNS: 30s cooldown per client V1: Public (30 req/min) | V2: Internal (Token required) Passive DNS permanently stored in PostgreSQL

Feature Matrix

FeaturePageAPIDescription
DNS Lookup/dns-lookup/v1/dns/lookupA/AAAA/CNAME/MX/NS/SOA/SRV/TXT/CAA records for domain targets
rDNS Scanner/rdns/v1/dns/rdnsIPv4/CIDR concurrent scan, PTR+CNAME match modes, scoring and hint labels
Reverse IP/reverse-ip/api/reverse-ipFind public domains pointing to one IPv4, with source labels + JSON/CSV export
Reverse NS/reverse-ns/api/reverse-nsFind domains sharing authoritative NS servers
Reverse MX/reverse-mx/api/reverse-mxFind domains sharing MX mail servers
Subdomain Discovery/subdomains/api/subdomainsPublic host/subdomain discovery with source labels + JSON/CSV export
DNSSEC/dnssec/api/dnssecDS / DNSKEY / RRSIG / NSEC checks with 0–100 security score and strong/partial/weak status
DNS History/dns-history/v1/dns/historyPassive DNS records from CIRCL, Robtex, and local query history — permanently stored

API Endpoints

MethodPathQueryPurposeLimit / Rule
GET/v1/dns/lookupdomain, type?Standard DNS lookup for domain targets30 req/min per client IP
GET/v1/dns/rdnstarget (ipv4|cidr)Concurrent reverse DNS scan with PTR/CNAME scoring30s cooldown per client
GET/api/reverse-ipipFind public domains pointing to an IPv4Public source dependent
GET/api/reverse-nsdomain, limit?Find domains sharing authoritative NS serversServer-side capped and cached
GET/api/reverse-mxdomain, limit?Find domains sharing MX mail serversServer-side capped and cached
GET/api/subdomainsdomainFind public host records under target domainServer-side capped and cached
GET/api/dnssecdomainDS/DNSKEY/RRSIG/NSEC checks with 0–100 security score30 req/min per client IP
GET/v1/dns/historydomain, limit?Passive DNS history from CIRCL, Robtex, and local records30 req/min per client IP
POST/v1/dns/history(JSON body)Ingest passive DNS records (internal / V2 use)Requires Bearer token
GET/health(none)Health check endpointNo auth; monitoring use

V1 API: Public access, rate limited (30 req/min). V2 API: Internal use only, requires Bearer token, no rate limit.

Interactive Terminal Demo

cURL Example

Record Types And Meaning

TypeTargetWhat It Means
ADomainIPv4 address mapping
AAAADomainIPv6 address mapping
CNAMEDomainAlias target chain
MXDomainMail server routing and priority
NSDomainAuthoritative name servers
PTRIP/Domain(A/AAAA)Reverse lookup hostname
SOADomainZone authority metadata
SRVDomainService endpoint target/port/priority
TXTDomainText policies and verification strings
CAADomainAllowed certificate authorities
SPF / DMARC / DKIMTXT classAuto-grouped under TXT in this system

Response & Errors

HTTP CodeMeaning
200Success — response body contains code, data, cached, timestamp.
400Bad Request — missing or invalid query parameters.
404Not Found — no records found for the requested target.
429Too Many Requests — rate limit exceeded (30 req/min for V1).
500Internal Server Error — upstream lookup failure.

All JSON responses share the same shape: { code: number, data: any, cached: boolean, timestamp: number }.

DNS.NF queries only publicly available DNS data and public datasets. Some results may be incomplete or delayed.