Refresh ListTools

server reputation checker

Use this working tool to inspect structure, plan credits, or query a domain without confusing that action with mailbox verification.

PUBLIC SERVER IDENTITY CHECK

We check reverse DNS and forward-confirmed reverse DNS using public records. No email is sent and no mailbox is contacted.

COMMON QUESTIONS

Server identity, answered.

What does the server identity score measure?+

It summarizes public DNS identity signals such as reverse DNS, forward-confirmed reverse DNS, and domain MX routing. It is not a complete IP reputation score.

What is reverse DNS?+

Reverse DNS maps an IP address to a hostname using a PTR record. Many receiving systems expect mail servers to have a consistent identity.

What is forward-confirmed reverse DNS?+

It checks whether the hostname returned by PTR points back to the same IP in an A record. This helps identify mismatched server identity.

Does a passing score guarantee delivery?+

No. Delivery also depends on authentication, reputation, complaints, bounces, message content, consent, and recipient policy.

Why is PTR important for email servers?+

A consistent PTR hostname gives receiving systems a clearer server identity. Missing or generic PTR records can be a configuration warning.

Can I check a domain and an IP?+

Yes. A domain is resolved to up to three public IPv4 addresses; an IP is checked directly.

Why can a domain have several scores?+

A domain may send from multiple servers. The checker reports each returned IPv4 address so you can investigate differences.

Does this tool check IPv6?+

The current public checker evaluates IPv4 addresses. IPv6 identity checks can be added separately.

What does no MX record mean?+

It means no explicit mail-exchange record was returned for the domain. It does not prove that every mailbox is invalid.

Does the checker contact my mail server?+

No. It uses public DNS lookups only and does not open an SMTP session or send email.

How often should I run this check?+

Run it after changing mail infrastructure, moving providers, or seeing bounce and reputation changes. Re-run after DNS propagation.