ptr · rdns · doh · cloudflare · live

Reverse DNS PTR lookup

Resolve an IPv4 or IPv6 address back to its hostname via Cloudflare DNS-over-HTTPS. Everything runs in your browser.

Reverse DNS Lookup
IP
1.1.1.1
ipv4
PTR records
0
answers
Status
idle
doh
ARPA
1.1.1.1.in-addr.ar…
domain
IP
input · ip address

A reverse DNS lookup queries the PTR record of an IP's in-addr.arpa (IPv4) or ip6.arpa (IPv6) name.

ARPA form:

1.1.1.1.in-addr.arpa

Resolved via Cloudflare DNS-over-HTTPS (https://cloudflare-dns.com/dns-query).

output · ptr records
No PTR records found.
Quick Start

How a reverse DNS lookup works

An IP becomes a reversed domain under in-addr.arpa or ip6.arpa, and the PTR record at that name holds the hostname.

  1. 01

    Enter an IP

    IPv4 like 1.1.1.1 or IPv6 like 2606:4700::1111.

    Lookups reference the IANA registries (MIME, HTTP status, TLDs) bundled at build time — no live network calls, no rate limits, no leaked queries.

    inputIANAregistryofflinelive
    input · queryip · IANA
    1.1.1.1
    loaded · IANA bundlespec · ready
  2. 02

    Reverse to ARPA

    Octets/nibbles are reversed and joined under in-addr.arpa or ip6.arpa.

    Builders emit canonical syntax per the relevant RFC (9110 for HTTP, 5322 for headers, 3986 for URLs) so the output passes spec-compliant parsers.

    arpaRFC 9110canonicalspec-compliantlive
    arpa · optionsptr · live
    1.1.1.1.in-addr.arpa
    options applied · livecanonical
  3. 03

    Query DoH

    Cloudflare's DNS-over-HTTPS returns the PTR record.

    Validation flags common pitfalls — uppercase header names, smart quotes inside Content-Type, missing ;charset=utf-8 — before they bite production.

    dohvalidationlintpitfallslive
    fetch · looked updoh · ready
    type=PTR
    result · livevalidated
  4. 04

    Read hostname

    One or more hostnames may resolve back from a single IP.

    Copy writes the snippet directly into your clipboard; downloads emit the right extension and MIME so curl/httpie pick them up correctly.

    resultclipboardMIME-correctblobcurl-ready
    ok · copiedready · done
    one.one.one.one
    shipped · ready to shipsuccess
Pro tips

Web-spec details that bite later

Idempotency saves retries

POST/PUT/DELETE should be safely retried. Use idempotency keys and return the same response on duplicate requests.

Match RFC 9110 status codes

Don’t invent codes. 422 for validation errors, 409 for conflicts, 429 for rate limits. Standard codes work with off-the-shelf clients.

Set <code>Cache-Control</code> deliberately

Default browser caching is conservative. Use max-age + stale-while-revalidate for hot endpoints.

Validate Open Graph in dev

OG tags break silently. Use a previewer like OG Generator + Facebook’s debugger before launch.

CORS is a server concern

The browser sends the preflight; the server decides. Wildcard origins disable credentials — be explicit.

MIME drives behaviour

Servers must send the right Content-Type. Browsers sniff but the spec says they shouldn’t — be explicit to avoid surprises.

Use Cases

When to do reverse DNS

Spam triage, log enrichment, mail server hygiene.

Mail server hygiene

Verify your outbound IP has matching forward/reverse DNS. Bundled from IANA registries at build time — no live network call, no rate limit, no leaked queries. The MIME, TLD, and status-code tables are baked in so the tool works offline once loaded.

spec-compliant

Spam triage

Identify what's behind a hostile IP. Output is canonical per the relevant RFC (9110 for HTTP, 5322 for headers, 3986 for URLs), so spec-compliant parsers accept it as-is. Cross-browser and cross-library behaviour stays consistent.

offline

Log enrichment

Turn IPs in access logs into human-readable hostnames. Pairs with the curl-to-fetch converter for end-to-end test stubs — copy the curl from DevTools, paste, get an idiomatic fetch() body. Drop into Playwright/Vitest fixtures without manual translation.

IANA-backed

CDN debugging

Confirm an IP belongs to Cloudflare, Fastly, or your edge. Catches common pitfalls (uppercase header names, smart quotes inside Content-Type, missing ;charset=utf-8) before they bite production. Validation flags rather than auto-corrects so you stay in control.

RFC-aligned

Audit security

Spot odd hostnames that don't match expected providers. Validation runs as you type — copy only when the output is shaped correctly. The output drops directly into nginx, Apache, or CDN configs without re-formatting or re-quoting.

production-grade

Geo / ASN clues

PTR records often hint at the cloud provider and region. Same input plus same options always produces identical canonical output, so the tool is safe to embed in CI scripts that diff against expected configs.

curl-ready
FAQ

Frequently asked questions

Many IPs have no PTR — it's optional. Residential and dynamic IPs often skip it; servers usually have one.
Forward-confirmed reverse DNS (FCrDNS) is required by many mail servers. A mismatch can cause email rejection.
Yes — IPv6 addresses are expanded, nibble-reversed, and queried under ip6.arpa.
To Cloudflare's public DoH endpoint at cloudflare-dns.com — no PII is included.
The IP-to-ARPA computation runs locally; only the DoH query leaves your browser.
Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

Sent straight to the maintainers · no account needed
47 in queue·8 shipped this month
Request queued. Thanks!