Email security check

See whether your practice domain publishes SPF, DKIM, and DMARC — in plain language, with the business consequence.

Demo / prototype. This page does not query live DNS. Enter any domain and click Run — results shown are a pre-baked example for impact360.com so the meeting can walk the UX. Production (Job 2) will use a rate-limited public DNS lookup only.
Pass

SPF

An SPF record is published. Receiving servers can check which hosts are allowed to send as this domain.

v=spf1 include:_spf.example-demo ~all

Business meaning: Harder for random servers to send mail that claims to be from your office — if receivers honor SPF.

Review

DKIM

Demo shows a selector present, but rotation / dual-selector hygiene should be verified with your mail host (Google Workspace, Microsoft 365, etc.).

selector1._domainkey → found (demo)

Business meaning: DKIM signs messages so receivers can tell the body wasn’t altered in transit. Missing DKIM makes spoofed look-alikes easier to believe.

Fail

DMARC

Demo finding: no enforcing policy (common in this market). p=none monitors only — it does not tell receivers to reject fakes.

Suggested fix (copy for your web/DNS person):
v=DMARC1; p=quarantine; rua=mailto:dmarc@yourdomain.com; pct=100

Business meaning: Without enforcement, someone can send email that appears to be from your practice. On a 300-practice sample (Sep 2026), most orthodontic domains had at least one email-auth finding.

Pass

HTTPS (site)

Demo: certificate present and not expired. Production will check redirect-to-HTTPS and expiry date.

Passive public checks only in production. Nothing private is scanned. Results are not stored without consent.

← Help Library