IP & Domain Reputation Check

See what the public internet reports about your IP or domain: blocklist listings, reverse DNS and forward confirmation, and SPF/DMARC authentication posture — with a transparent public signal health score and exact weights.

Check public reputation signals

Enter a public IP address for blocklist, PTR and FCrDNS checks — or a domain for blocklist and SPF/DMARC posture.

For IPs we check public blocklists, reverse DNS and forward confirmation. For domains we check domain blocklists (RHSBL) and SPF/DMARC posture — website IPs are never assumed to be sending IPs.

We query public DNS on your behalf: blocklist zones, PTR records, and SPF/DMARC TXT records. The address you enter is used only to run these lookups; results are not stored.

How the Reputation Check works

We classify your input

A public IP gets the IP pipeline: DNSBL blocklists, PTR reverse DNS, and forward-confirmed reverse DNS. A domain gets RHSBL domain blocklists plus SPF and DMARC posture. Private and reserved addresses are rejected — public blocklists do not cover them.

Blocklists are queried with honest semantics

Each provider zone is queried through a bounded, time-capped run. A 127.0.0.0/8 answer is a listing with the provider’s documented meaning; no answer means not listed; a timeout or refusal stays unknown — never clean.

Domains never impersonate sending IPs

For a domain we list the infrastructure IPs it resolves to, but a website IP is not assumed to be your outbound sending IP. Only when you select an IP yourself do we run the sending-IP checks — and they are labeled as your selection.

You get a published-formula score

Every factor, its weight, and its evidence are shown: 60/20/20 for IP inputs, 50/25/25 for domains, 50/15/15/10/10 with a selected sending IP. Unknown factors are excluded and the rest renormalized; any listing fails the check outright.

What this tool does and does not tell you

  • Public DNSBL/RHSBL results are not a complete sender reputation score. Gmail, Microsoft, and other mailbox providers keep private reputation that no external tool can query — this page never claims to.
  • The score is a public signal health measure with published weights. It is not a deliverability or inbox-placement guarantee.
  • A domain’s website IP is not necessarily its outbound sending IP; sending-IP checks only run for an IP you explicitly select, and are labeled as your selection.
  • Providers that time out or refuse queries are reported as unknown and are never counted as clean; some operators deliberately block public-resolver traffic.
  • DKIM is not scored because a selector is required to look it up; use the DKIM Record Checker for that layer.
  • Delisting requires fixing the underlying cause first — a delisting request without remediation usually leads to re-listing.

Related free tools

Blacklist Checker

Deep-dive any IP or domain against every active DNSBL and RHSBL provider with per-provider delisting links.

Open tool

SPF Record Checker

Verify the SPF record behind your domain’s posture, including nested includes and the 10-lookup limit.

Open tool

DMARC Record Checker

Inspect the DMARC policy, reporting addresses, and external authorization that feed your domain score.

Open tool

DKIM Record Checker

Look up and validate the DKIM key for your selector — the missing piece this score deliberately leaves out.

Open tool

Frequently Asked Questions

What does this reputation check actually measure?

Only what is publicly queryable: whether an IP appears in public DNS-based blocklists (DNSBLs), whether it has reverse DNS (PTR) that forward-confirms (FCrDNS), whether a domain appears in domain blocklists (RHSBLs), and the domain’s SPF and DMARC authentication posture. These are public signals — not the private reputation scores kept by Gmail, Microsoft, or other mailbox providers, which no external tool can query.

How is the public signal health score calculated?

For an IP, the score is 100 points split across blocklists (60), PTR (20), and FCrDNS (20). For a domain, it is blocklists/RHSBL (50), SPF (25), and DMARC (25); when you also select a sending IP, the IP signals take the lead (blocklists 50, PTR 15, FCrDNS 15, SPF 10, DMARC 10). Each factor earns its full weight when healthy, zero when unhealthy, and is excluded — not counted as clean — when the lookup was inconclusive. Any conclusive blocklist listing fails the check regardless of the number. The score measures signal health, never deliverability or inbox placement.

Why do you ask me to select a sending IP for domain checks?

A domain’s website IP (its A/AAAA record) is not necessarily the IP your mail is sent from — outbound mail often leaves through separate relay IPs. Pretending the website IP is the sending IP would produce a misleading verdict, so the tool lists the domain’s infrastructure IPs and only checks one as a “sending IP” when you explicitly identify it as such.

A blocklist provider shows “Unknown”. Does that mean I’m clean there?

No. Unknown means the provider did not answer conclusively — typically a timeout or a refusal, since some operators block queries from public resolvers. Unknown results are excluded from the score and are never counted as clean or passing. Retry later or check the provider’s own lookup page.

My score is high — does that guarantee my email lands in the inbox?

No. A high public signal health score means your DNS signals look good, but inbox placement also depends on content, engagement, sending volume patterns, and the private reputation mailbox providers build from their own traffic. Treat this score as necessary hygiene, not a deliverability guarantee.

Why is DKIM not included in the domain score?

Looking up a DKIM record requires a selector name, which cannot be discovered reliably from DNS alone. Guessing common selectors produces false “missing DKIM” verdicts, so the score stays honest and leaves DKIM out — use the DKIM Record Checker with your selector instead.

Increase Your Sales Right Now

Automate Sales Outreach & Get Booked!

Start Free Trial

(14 Day Free Trial, No CC Required)