hey.com
Live email deliverability and anti-spoofing audit. Every value below was read from public DNS at the moment this page was generated.
77/100 — Solid configuration with a few gaps worth closing. Accepts mail · Protected against spoofing
Findings
-
mx redundancy
Only one mail exchanger is published, so there is no failover.
home-mx.app.hey.com
Fix: Add a secondary MX at a higher priority number.
-
spf
SPF ends in ~all (softfail); unauthorised mail is marked rather than rejected.
v=spf1 include:_spf.hey.com ~all
Fix: Move to -all once you have confirmed all senders are listed.
-
dmarc rua
DMARC has no rua address, so you receive no aggregate reports and are flying blind.
v=DMARC1; p=quarantine; adkim=s; aspf=r; ri=3600; fo=1;
Fix: Add rua=mailto:dmarc@hey.com to the record.
-
dkim
No DKIM key found at any common selector. Either DKIM is not configured, or it uses a custom selector we cannot discover from DNS alone.
Fix: Enable DKIM signing at your mail provider and publish the selector they give you.
-
mx
1 mail exchanger published.
10 home-mx.app.hey.com
-
dmarc
DMARC is enforcing with p=quarantine.
v=DMARC1; p=quarantine; adkim=s; aspf=r; ri=3600; fo=1;
-
mta sts
MTA-STS is published, so senders will refuse to downgrade to plaintext SMTP.
v=STSv1; id=20200922120000Z;
-
tls rpt
TLS reporting is enabled.
v=TLSRPTv1; rua=mailto:sts-reports@basecamp.com
Records
| MX | 10 home-mx.app.hey.com |
|---|---|
| SPF | v=spf1 include:_spf.hey.com ~all |
| DMARC | v=DMARC1; p=quarantine; adkim=s; aspf=r; ri=3600; fo=1; |
| DKIM selectors | none discovered |
| MTA-STS | published |
| TLS-RPT | published |
| BIMI | not published |
| DNSSEC | not validating |
Same data, as JSON, in one request. No SMTP probing, no stored recipient data, 250 free calls a month.
curl "https://mailgrade.dev/v1/domain?domain=hey.com"
Also available: /v1/verify?email=… for individual addresses, and
/v1/verify/batch for lists.