ToolsReputation

Are you on a blocklist that matters?

Six lists, checked against the addresses that actually send for your domain. You get what each listing means and whether it is worth acting on.

Freeno account, no email

Example: jamestyler.com

Not listed anywhere that matters

198.51.100.24The host your mail leaves from

  • ClearSpamhaus ZENNot listed
  • ClearBarracudaNot listed
  • ClearSpamCopNot listed
  • No answerSORBSThe zone did not answer in time.

Get told if this ever stops being true.

Clean today is the right time to start watching. You will hear from me only when something moves.

This asks me to set it up. It does not start anything and it does not charge you.

I email you about this domain only, when something changes.

This one cannot run in your browser, because it needs real DNS queries. It sends the domain you typed and nothing else. I store the domain to stop the endpoint being used as somebody else’s scanner.

How this is calculated, and what to put in

Why most blocklist checkers mislead you

Almost all of them check the addresses behind your MX records. Those are the servers that receive your mail.

If you send campaigns through a platform, those are not the addresses you send from. A clear result there tells you nothing about whether your mail lands. This one checks those too, and labels them as what they are.

What it checks instead

First, any address your own record names directly. Those are the ones you authorized yourself, and they are yours to fix.

Ranges belonging to a sending platform are counted, not scanned. A single range can hold thousands of addresses. Checking six of them at random would be theater.

Not every listing is a problem

Some entries are policy, not reputation. An address marked as one that should never send mail directly is the system working. Filing a delisting request for it wastes your afternoon.

This checker separates those from the listings that cost you delivery. Treating them alike is how people chase the wrong thing.

When a list will not answer

Some operators refuse queries arriving from large public resolvers. They answer with a refusal code rather than a result.

A checker reading that code as a listing tells you that you are blocked everywhere. This one reports it as unanswered, because unchecked and clear are not the same thing.

A listing is a symptom. Something caused it.

Delisting without finding the cause buys you about three weeks. Tell me how you send and I will tell you what to look at.