AthonisOne module 07 of 08

Internet Posture

Everything the world can see of you, read from where they see it.

Every other module reads the inside of the estate. This one reads what the estate publishes to the world — DNS, mail authentication, certificates and the headers public sites send — and reports where a domain can be spoofed, where mail can be downgraded to plaintext, and where a forgotten record hands a name to a stranger. The first tier needs nothing but a domain name.

What it answers

The questions this module exists for.

  • 01 Could an attacker send mail that appears to come from our domain?
  • 02 Is our DNS signed, anchored and correctly delegated — and are the signatures about to expire?
  • 03 Which of our public certificates expire this fortnight, and which are not trusted?
  • 04 Does every public site enforce HTTPS and send HSTS?
  • 05 Is our CDN protecting the origin, or can the origin be reached directly around it?
  • 06 Is any subdomain pointing at a resource we retired that someone else could claim?
  • 07 Is the anti-phishing policy we configured actually applied to anybody?
What it checks

In detail.

01

Mail authentication

SPF, DKIM, DMARC, MTA-STS and TLS-RPT — presence, syntax, enforcement, key strength — plus whether the mail exchangers offer STARTTLS and any dangling MX records. Whether your domain can be spoofed, and whether mail to it can be downgraded to plaintext.

02

DNS hygiene

Registrar lock, delegation consistency, nameserver behaviour, CAA records and DNSSEC as a full chain: signed, anchored at the registrar, DS-to-key match, signature expiry and algorithm strength.

03

Certificates and web headers

For every public hostname: expired or expiring certificates, certificates that do not chain to a trusted root, name mismatches, weak keys and deprecated TLS. Whether plain HTTP redirects and HSTS is actually sent.

04

Zone records and the CDN edge

With a Cloudflare token: subdomains pointing at retired hosting anyone could re-create, dangling CNAMEs, private addresses in the public zone, the CDN's TLS mode to the origin, and origins reachable around the proxy.

05

Both sides of mail authentication

Connect Exchange Online and the module reads what your own mail platform does with mail — accepted domains and DKIM signing, mail flow rules and connectors and whether they require TLS, remote domains, authentication policies, and the anti-spam, anti-phishing, anti-malware, Safe Links and Safe Attachments policies — beside what your domains publish, on the same row.

06

Which recipients a policy actually reaches

A policy can be switched on, correctly configured, pass its audit, and sit in the mail path of nobody. The module says which recipients each protection policy reaches — and names domains the tenant sends as that nothing is watching.

Typed findings

Each with the evidence behind it, not just a severity label.

Finding Wiki

A built-in explainer on every finding — what it is, why it matters, what to do.

A posture score

Rolled up from the findings and trended over time.

Compliance evidence

Findings mapped to the framework controls they evidence.

How it judges

Where it refuses to over-claim.

A check that guesses produces false findings, and false findings teach a team to ignore the real ones. These are the places this module holds back.

  • A lookup that did not answer is reported as not measured, never as a record that is absent. A resolver outage produces a visible gap, not a sweep of false findings.
  • A mail exchanger's encryption offer is judged only when it held a conversation. One that refuses the appliance reads not measured.
  • Domains that receive no mail are not asked for MTA-STS or TLS-RPT; domains that publish no mail infrastructure are not asked for DKIM. SPF and DMARC still apply, to say the domain sends nothing.
  • A verdict that needs the whole zone is withheld when only the apex was visible — each domain states how completely its zone could be read.
  • On a genuinely air-gapped install the module runs unconfigured, and its checks read not measured rather than pretending to a result.
What it reads

Connected to what you already run.

  • Your internet-facing domains
    Mail authentication, delegation and DNSSEC, certificates and web headers — no credential at all
  • Cloudflare
    Zone records, DNSSEC state and edge-security settings, on a scoped read-only token. The legacy global API key is refused
  • Microsoft Exchange Online
    Mail-tenant configuration only, through read-only application permissions plus a read-only Exchange role
What it never does

The boundary, stated plainly.

  • Never scans your perimeter. No port scanner, no discovery sweep, no path enumeration — the only outbound traffic is DNS, registry lookups, and handshakes against names you publish.
  • Never sends anything through a mail server. The mail-exchanger check stops at the handshake.
  • Never reads anybody's mail. The tenant is read for configuration only — never a message body, subject, recipient or attachment.
  • Never stores page content or session material, and never hands your domain list to a third party.

Findings from this module evidence the mail-authentication, DNS-security, certificate-lifecycle, cryptography and data-in-transit control areas of every activated framework.

See what Internet Posture would say about your estate.

Licensed on its own, and on the same platform as every other module. We'll show you the answer — and what it would say it couldn't measure.