The free exposure check: six lookups you can do by hand

An exposure check is a look at what anyone on the internet can already learn about your business domain, starting with whether they can send email as you. This page lists six lookups you can do yourself today, for free, using public records. A tool that runs them for you is planned and is not available yet; there is nothing to run on this site today.

The six lookups

What to checkHow to lookA good result
Can someone send email as you?Look up your SPF and DMARC records. Steps →One SPF record; DKIM passing; a DMARC record at p=quarantine or p=reject with a reporting address
Which website names exist under your domain?Search your domain at crt.sh. Steps →Every name on the list is one you recognize and still use
Is your certificate valid, and when does it expire?Click the padlock or site-information icon next to your address in a browserValid, and renewing automatically
Is HTTPS forced, and which security headers are sent?Read your site’s response headers. Steps →Plain HTTP redirects to HTTPS; the basic headers are present
Does your site announce its software version?In the same headers, look for Server and X-Powered-By linesNo version numbers shown
Is the domain itself protected?Log in to your domain registrarTransfer lock on; auto-renew on; contact email current

Write the date and the result of each lookup in a note. That note is your baseline, and it is the thing to re-check after you change anything.

Why these lookups are safe to do

Everything in the table comes from public records (DNS, Certificate Transparency logs, your registrar account) plus loading your own home page, which is what any visitor’s browser does. Nothing here scans, probes or logs in to anything.

A useful line to hold: if a normal person opening your site in a browser would cause that traffic, it is a lookup. Anything more is testing. How to test your own systems safely →

The limits, stated plainly

A clean result means your front door is tidy. It does not mean you are secure. These lookups read what is public. They say nothing about your passwords, your backups, your vendors, your staff habits or anything inside your network.

They cannot see a lookalike domain registered by someone else to imitate you, because that domain is not yours.

They are a snapshot. Certificates get issued and records get edited, so the result describes the day you looked.

What to do with the result

  1. Fix the mail records first, in the safe order. The order →
  2. Lock the domain at the registrar if it is unlocked, and turn on auto-renew.
  3. Work through the list of names and mark each one live, retired or unknown. Delete the DNS record for anything retired. Why →
  4. Add the headers that break nothing, then the ones that need testing. In order →
  5. Repeat the six lookups afterward. Seeing the results change is the proof the work landed.

About the planned tool

We plan to build a free tool that runs these same lookups for a domain you confirm you own and writes up the result in plain English. It is not built, it has no release date, and no reports have been produced with it. When it exists it will be limited to what this page describes: public records plus one ordinary request to the home page.

Until then, the table above is the whole check. If you would like to learn to build small tools like this yourself, that is what our AI classes teach. More guides are on the security basics page.

FAQ

Is the exposure report tool available?

No. It is planned and not built. The six lookups on this page can be done by hand today at no cost.

Do I have to own the domain to do these lookups?

Do them for domains you own. The registrar check requires your login anyway, and the point of the exercise is to fix what you find.

Will these lookups set off alerts or slow my site?

They should not. Reading DNS and certificate logs does not touch your site at all, and reading your headers is one page load, the same as a visitor.

Is this a penetration test?

No. It is a passive look at public information. A penetration test involves actively testing systems and is done by a specialist firm under a written agreement.

How often should I repeat the check?

After any change to your website, email provider or domain, and on a schedule such as once a year.

Email spoofing: SPF, DKIM, DMARC · Website security headers · What strangers can see about your business · Back to security


Get in touch

Email solutions@ikonic303.dev to get the next AI class date, to talk about marketing, or about one AI tool or job you want built. ikonic303 is based in Colorado, and classes are held in the Denver metro.

ikonic303 home · AI classes · what we built · free Anthropic courses · contact