Records of one type
API · /dns-api
DNS Lookup API
healthy
3,545 Subscribers
Resolve DNS records — A, AAAA, MX, NS, TXT, CNAME, SOA, SRV, CAA, PTR — for any domain, fetch all common records in a single call, or run a reverse PTR lookup for an IPv4 address. Backed by Google DNS-over-HTTPS. Ideal for devops tooling, uptime and email-deliverability checks (SPF/DKIM/DMARC), security research and domain monitoring.
api.oanor.com/dns-api
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 138 ms
- Server probes · 24h
- Subscribers
- 3,545
- active
- Total calls
- 57
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 1,500 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 1,500 lookups/month at 2 rps
- A, AAAA, MX, NS, TXT, CNAME records
- No credit card
- Community support
Basic
€12.00 /month
- 120,000 calls / month
- 8 requests / second
- Hard cap (429 above quota, no overage)
- 120,000 lookups/month at 8 rps
- All record types incl. SOA, SRV, CAA, PTR
- Reverse PTR + fetch-all-records endpoints
- Commercial use allowed
Pro
€34.00 /month
- 600,000 calls / month
- 25 requests / second
- Hard cap (429 above quota, no overage)
- 600,000 lookups/month at 25 rps
- Full record set + reverse DNS
- Bulk multi-domain resolution
- Priority email support
Mega
€89.00 /month
- 2,500,000 calls / month
- 80 requests / second
- Hard cap (429 above quota, no overage)
- 2,500,000 lookups/month at 80 rps
- 99.9% uptime SLA
- Priority queue + dedicated support
- Highest rate limits for monitoring fleets
Built by
Related APIs
Other APIs with overlapping tags.
TLD (Top-Level Domain) API
Every top-level domain in the IANA root zone as an API — the authoritative list a registrar, domain validator or analytics tool needs. For each TLD: whether it is a country-code TLD (ccTLD), a generic TLD (gTLD) or an internationalized (IDN) domain, its A-label, its Unicode form (e.g. xn--p1ai resolves to .рф) and, for ccTLDs, the country it belongs to. Validate a TLD or whole domain, find a country's ccTLD, filter by type, search, or list the entire root zone. Sourced from IANA's official tlds-alpha-by-domain.txt and served from memory — always fast.
api.oanor.com/tld-api
Punycode / IDN API
Convert internationalized domain names (IDNs) between their human-readable Unicode form and the ASCII Punycode form (xn--…) that DNS actually uses. Encode a Unicode domain like münchen.de or 例え.jp (or even an emoji label like ☕.example) to ASCII, decode an xn-- domain back to Unicode, and convert a whole URL's host in either direction. Handles accents, non-Latin scripts and emoji. Useful for IDN domain handling, email and URL validation, DNS tooling, and spotting homograph / look-alike domains. Pure local IDNA conversion — no key, no third-party service, instant. Live. 4 endpoints. Distinct from Public-Suffix-List domain parsing and from generic text encoders.
api.oanor.com/punycode-api
MTA-STS API
Inspect a domain's SMTP transport-security posture — whether mail servers are required to deliver inbound mail over authenticated TLS, protecting it from downgrade and man-in-the-middle attacks. Pass a domain and the service fetches the MTA-STS policy file from mta-sts.<domain>/.well-known/mta-sts.txt (its version, mode, the permitted MX hosts and max_age), the _mta-sts DNS TXT record (its policy id) and the _smtp._tls TLS-RPT record (the rua reporting address), then reports whether MTA-STS is actually enforced and a prioritised list of issues — no policy file, no DNS record, a mode of only "testing", or a missing TLS-RPT record. A second endpoint returns just the parsed policy file. The request is made server-side and private/internal targets are refused (SSRF-guarded). Built for email-deliverability and anti-downgrade-attack audits, vendor and third-party assessment, and compliance. An MTA-STS / TLS-RPT checker — the SMTP transport-security counterpart to the email-authentication analyzer (emailsec, which covers SPF, DKIM and DMARC), and distinct from raw DNS lookup (dns). No upstream key, no cache.
api.oanor.com/mtasts-api
DNS Propagation API
Check DNS propagation by querying a record across several major public resolvers at once — Google (8.8.8.8), Cloudflare (1.1.1.1), AdGuard and dns.sb — and seeing whether they all return the same answer. Pass a domain and a record type and the service queries every resolver in parallel and reports each resolver's answers, whether they are consistent (the change has fully propagated) or still differ (mid-propagation, stale caching or split-horizon DNS), the number of distinct answer sets and the union of all answers. Supported record types: A, AAAA, CNAME, MX, TXT, NS, SOA, SRV, CAA and PTR. A single-resolver endpoint queries one named resolver on its own, and a failing resolver is reported per-resolver without failing the whole call. Live DoH (DNS-over-HTTPS) JSON queries, always current. Built for verifying DNS changes after a migration or launch, debugging split-horizon or stale-cache issues, and uptime/propagation monitoring. A DNS propagation checker — distinct from single-resolver record lookup (dns), the email-authentication analyzer (emailsec) and WHOIS (whois). No upstream key, no cache.
api.oanor.com/dnspropagation-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for DNS Lookup API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call DNS Lookup API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for DNS Lookup API?
Free tier allows 1 request per second. Paid plans scale up to 50 requests per second on the Mega tier. Hard limits return HTTP 429 above the quota — no surprise overage charges.
How much does DNS Lookup API cost?
DNS Lookup API has a free tier with 100 calls / month. Paid plans start at €12.00 / month with higher quotas and faster rate limits.
Can I cancel my subscription anytime?
Yes. Plans are billed monthly and you can cancel anytime from your billing dashboard. No long-term contracts and no cancellation fee.
Is DNS Lookup API GDPR-compliant?
All requests to DNS Lookup API go through our EU-based gateway. Your upstream API key never leaves our server and no personal data is shared with the upstream provider beyond the request you send.
Pick an endpoint from the list on the left to see its details and try it.
Code snippets
Sign up to get an API key, then call any path under your slug.
curl https://api.oanor.com/dns-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."const res = await fetch("https://api.oanor.com/dns-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();$ch = curl_init("https://api.oanor.com/dns-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);import requests
r = requests.get(
"https://api.oanor.com/dns-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())Ratings
Sign in to rate.
No reviews yet.
Discussion
Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.
Sign in to start a thread or reply.
Sign inNew thread
📌 Pinned
🔒 Locked
·
·
·
-
Provider answer
🔒 This thread is locked — no new replies.
-
·
- No threads yet — start the discussion.
Support
Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.
Sign in to open a support ticket.
Sign inOpen new ticket
Describe what you need help with. The provider team gets an email and replies on the ticket page.
-
·
Urgent - No tickets yet for this API.