What's My IP?

We've detected your public IP from this connection. Below: ASN, PTR, FCrDNS, IPv6 connectivity, and DNSBL status, plus next-step links depending on what the checks return.

Your public IPv4 address
216.73.217.106

Your public IP, with the checks that matter for mail delivery

This page picks up the IP your browser is connecting from and runs the lookups an email admin actually uses. The RDAP record (ASN, network, country, abuse contact). The PTR and FCrDNS status, which is the cheap authentication step mail servers run before they'll accept SMTP. An IPv6 reachability test. And a sweep against the major DNSBL blocklists.

Results stream in as each check finishes. Your IP shows up first, the rest fills in to the panel above.

Why not just show me an IP and stop there?

Most "what's my IP" tools dump an address and a country flag. Useful for two seconds. The questions that follow are always the same: is this IP listed anywhere, does it have a sensible PTR, does IPv6 actually work from here. We run those checks in the same pass.

Each result links into the matching deeper tool with the IP, or the PTR-derived hostname, already filled in. A DNSBL hit jumps to the full blacklist breakdown. An FCrDNS failure links to the FCrDNS checker. A mail-server PTR offers prefilled SPF, DMARC and MX lookups for the same domain.

Is the IP shown here the one my mail server sends from?

Only if you're loading this page from the same network your mail server runs on. The address shown here is whichever IP this browser session is using to reach tamingdns.com. If your mail server lives on a different host, VPS or hosting tenant, look up its public IP and run the checks against that via IP Info or Reverse DNS.

Why no city or region?

RDAP only publishes the country an IP block was registered in. City and region GeoIP comes from commercial databases (MaxMind, IP2Location) built on inference, and the data is shaky for IPv6, mobile carriers and cloud ranges.

Our take: for a deliverability tool, country from the registry is honest. A city pinpoint that's wrong half the time is worse than no city at all.

Why this matters

Gmail, Microsoft and Yahoo all gate inbound SMTP on a working PTR and a passing FCrDNS check. Fail one and the connection gets refused with 550 5.7.25 before your DKIM signature is even looked at. A DNSBL listing on top of that and you're invisible. The lookups on this page tell you which of those three is the actual blocker.

Privacy: your IP is shown back to you and used to run the queries on this page. We don't store it. We deliberately skip city-level GeoIP. RDAP country data is reliable, commercial city databases aren't.

Frequently Asked Questions

Common questions about public IPs, FCrDNS, IPv6, and DNSBLs.

Forward-Confirmed reverse DNS. The PTR for the IP resolves to a hostname, and that hostname's A or AAAA record resolves back to the same IP. It's a cheap sanity check, and big receivers (Gmail, Microsoft, Yahoo) run it before they'll talk SMTP to you.

Failing it usually shows up as:

550 5.7.25 The IP address sending this message does not have a PTR record setup

The PTR is set by whoever owns the IP block, usually your hosting provider or ISP. If you're on a VPS, it's almost always a self-service field in the control panel.

The test fetches a small JSON endpoint from a hostname that only publishes an AAAA record. If your network claims IPv6 capability but the connection times out, the IPv6 path is misconfigured somewhere between you and the upstream.

Common culprits: stale router advertisements, ISP IPv6 in transit but not at the edge, a firewall blocking outbound IPv6. For senders this isn't cosmetic. Gmail refuses IPv6 SMTP without a working IPv6 PTR plus FCrDNS, so a half-broken IPv6 path can mean your mail goes out over v6 and gets rejected.

Open the full blacklist breakdown from the result card above. Each listing has a direct link to the operator's delisting form.

Fix the cause before you submit. Asking Spamhaus to delist an IP that's still emitting spam from a compromised mailbox gets you relisted within hours, and the second listing is harder to clear than the first.

Not on its own. Two things matter. The PTR should resolve to something sensible, not a generic auto-PTR like:

5-23-45-67.broadband.example.net

And the forward A or AAAA record on that hostname must point back to the same IP. Receivers authenticate the sending identity through DKIM, SPF and DMARC alignment, not through the PTR. A mismatched PTR is only a red flag when it looks like dynamic or residential space.