Skip to content

Public-data health check

How our public-data health check works

A free, passive look at what anyone can already see on your website and public email records: exactly what we check, what we never do, and how to opt out.

What it is

A free, passive review of what any visitor to your website can already see. We look at three things, the same way a browser or a mail server would:

  • Email security records

    Your SPF, DKIM and DMARC records: the public DNS entries that tell other mail servers which messages really come from you. Any mail server reads them.

  • HTTPS and certificates

    Whether your site loads securely, sends plain-HTTP visitors to HTTPS, and has a valid, current certificate.

  • Software your pages reveal

    Software names and version numbers your public pages and server headers already show every visitor.

What we don’t do

The health check only reads what is already public. It never tests anything. Specifically:

  • Nothing behind a login

    Portals, staff systems and admin pages are never touched.

  • No login attempts

    We never try a password, default or otherwise.

  • No port scans

    We don’t sweep your network looking for open services.

  • No vulnerability probing

    We don’t send crafted requests to see what breaks.

  • No exploit testing

    We never try to get in, not even to prove a point.

If a check would need any of these, it isn’t part of the health check.

How light it is on your site

No more than four ordinary page loads per site per day: about what one person reading a few of your pages would cause. If you see a visit in your logs and want to know whether it was us, just ask: we’ll check our records and tell you. We read email records from public DNS, the way any mail server does; those lookups never touch your website.

Was that us?

For your logs
Send
The date and time (with time zone), the source IP address, and the page requested, copied from your logs.
We reply
We check our own scan records and tell you whether the visit came from us. If it didn’t, we say so plainly.
Rate
≤ 4 page loads / site / day

Our checks run from cloud servers whose addresses change, so we don’t publish a fixed IP list. Asking us is the reliable way to know.

Why we do it

Local governments, schools and utilities are frequent targets, and most of the weak spots we find can be closed once someone has found them and planned the fix properly. Across the 79,796 public organizations we have reviewed in the lower 48:

58%

can have their email spoofed

Only1in7

fully block spoofed email

1in11

public websites still don’t use HTTPS

Source: America Secure public-data health check, 2026Full report

A spoofed email is a message that falsely appears to come from your organization: an invoice from your finance office, say, or a notice to residents. Closing it means getting every legitimate sender authenticated, then moving the domain to enforcement without blocking your own mail: careful work, but well understood.

We evaluate the full email-authentication picture: SPF, DKIM, DMARC enforcement and alignment, among other signals. An organization counts as at risk when mail forged in its name would still reach inboxes. Many are partway there: the records exist, but forged mail still gets through or is only sent to spam. That’s why the two figures above differ: 58% can be spoofed outright, while only 1 in 7 fully block spoofed email.

We would rather you hear about a gap from us, for free, than from someone who means harm.

What happens with results

Who sees them
Your organization, via the contacts you list publicly, such as the contact page on your website.
Sharing
Never sold or published. Shared outside your organization only with your state’s chief information security officer (CISO) or the federal Cybersecurity and Infrastructure Security Agency (CISA), for a serious issue or if we can’t reach you, or if a court or the law compels us (and then we tell you first where the law allows).
What we publish
Only aggregate counts, like the figures on this page. No organization is ever named.

If we find something serious

Now and then the public view shows something that needs attention quickly: an actively exploited software flaw, say, or a significant security miss. When it does, we follow coordinated disclosure: we tell your organization first and privately, and, where appropriate, your state CISO or CISA, so you have help fixing it.

There is no sales pitch attached, and nothing is conditional on working with us.

Read our responsible disclosure policy

Opting out

If you’d rather we didn’t check your domains, use the form below or email team@americasecure.com. You don’t need to give a reason, and opt-outs are honored permanently.

Opt-out request

One or more, one per line or separated by commas. Pasting your website’s address is fine: we keep just the domain.

Used only to process and confirm your opt-out. See our Privacy Policy and Terms.

About this check

The health check is free, and separate from the paid security work America Secure does for public organizations. If you’d like to talk about your results, write to team@americasecure.com. If not, that’s fine too.

About America Secure