DNS & SSL Inspector - records and certificate checker | POLPROG Skip to content

DNS & SSL Inspector FREE

Look up DNS records and inspect the SSL/TLS certificate for any domain, all in one place.

Free to use No registration Privacy-first
Enter a domain to inspect
All checks are performed from our servers. We do not store or share your data.
Use cases

When to inspect a domain

DNS and TLS fail on a schedule nobody remembers setting.

Before a migration

Read the current TTLs so you know how long the old answers will keep circulating after you change them.

Certificate renewal season

See the remaining validity window against the issued lifetime, rather than a date on its own.

Investigating email delivery

Check whether MX, SPF and DMARC are actually published before blaming the mail provider.

Scope and limits

One vantage point, not the whole internet

Everything here is a single lookup from one place at one moment.

No global propagation claim

The records shown are what one recursive resolver answered for this query, and the certificate is what one TLS handshake from our server presented. Other resolvers, regions and network paths can legitimately answer differently, especially soon after a change. DKIM is not reported as absent, because a DKIM record lives under a selector name that cannot be enumerated: if it is not checked, we say so instead of guessing.

Help

FAQ

What people ask after a lookup.

I changed a record and it still shows the old value. Why?

Caching. Resolvers keep an answer for as long as its TTL says they may. The TTL profile chart is there precisely to tell you how long that will be.

Is this a global propagation check?

No. It is one lookup from one resolver. A propagation check queries many resolvers in many regions; this tool deliberately does not claim to.

Why is DKIM not checked?

DKIM keys are published at selector._domainkey, and the selector is chosen by whoever sends your mail. There is no way to list selectors from outside, and guessing common names would report a confident absence that means nothing.

What does an expiring certificate actually break?

Browsers refuse the connection with a full-page interstitial, and API clients usually fail outright. It is one of the few problems that takes a whole site down at a precise, predictable second.