A
Scanned 19 hours ago. Re-scan for a fresh result after a fix.
Issues to fix
Results
01Mail exchangers (MX)A
pass
2 MX record(s) found.
records
| preference | exchange | ttl |
|---|---|---|
| 100 | mxa-00131701.gslb.pphosted.com | 600 |
| 200 | mxb-00131701.gslb.pphosted.com | 600 |
02Mail providerB
info
Mail provider: Proofpoint (gateway).
provider proofpoint
warn
SPF does not include Proofpoint (gateway)'s sending hosts (_spf.pphosted.com), so Proofpoint (gateway) mail may fail SPF.
expected _spf.pphosted.com
03SPFA
pass
SPF record present.
record v=spf1 include:_netblocks1.cgi.com include:_netblocks2.cgi.com include:_spf-a.cgi.com include:spf-00131701.pphosted.com -all
warn
SPF uses 10 of the 10 permitted DNS lookups, little headroom remains.
lookups 10
pass
-all default policy.
04DKIMA
pass
Selector s2 key is ~2048-bit.
selector s2
record k=rsa; t=s; p=MIIBIjANBgkqhkiG9w…IDAQAB
bits 2048
pass
Selector s1 key is ~2048-bit.
selector s1
record k=rsa; t=s; p=MIIBIjANBgkqhkiG9w…IDAQAB
bits 2048
info
DKIM2 reuses these same selector._domainkey records and advertises no capability, so support cannot be detected from DNS. The 2 published key(s) carry over as they are. Adding an Ed25519 key (RFC 8463) prepares for it.
draft-ietf-dkim-dkim2-spec
keys 2
ed25519 false
05DMARCA
pass
DMARC record present.
record v=DMARC1; p=reject; rua=mailto:03fa6858bd9a651@rep.dmarcanalyzer.com; ruf=mailto:03fa6858bd9a651@for.dmarcanalyzer.com; fo=1;
pass
Enforcing policy p=reject.
p reject
rua true
06DNS healthA
07BlacklistsA
info
IPv6 MX addresses are not checked against IP DNSBLs.
pass
67.231.158.130 is not listed on Spamhaus ZEN.
target 67.231.158.130
list Spamhaus ZEN
pass
cgi.com is not listed on Spamhaus DBL.
target cgi.com
list Spamhaus DBL
pass
cgi.com is not listed on Spamhaus ZRD.
target cgi.com
list Spamhaus ZRD
pass
67.231.158.130 is not listed on SpamCop.
target 67.231.158.130
list SpamCop
pass
67.231.158.130 is not listed on GBUdb Truncate.
target 67.231.158.130
list GBUdb Truncate
pass
67.231.158.130 is not listed on Spamhaus AuthBL.
target 67.231.158.130
list Spamhaus AuthBL
pass
67.231.158.130 is not listed on PSBL.
target 67.231.158.130
list PSBL
08Bulk sending readinessA
pass
SPF, DKIM and DMARC are all present: the domain meets the Gmail/Yahoo and Microsoft bulk-sender authentication requirements (5,000+ messages/day).
spf true
dkim true
dmarc true
threshold 5,000 messages/day
info
One-click List-Unsubscribe is a message-level header. Verify by sending a test message.
09TLSA
info
No DANE/TLSA records. DANE is not deployed for these mail servers.
hosts mxa-00131701.gslb.pphosted.com, mxb-00131701.gslb.pphosted.com
10MTA-STSA
11BIMIA
pass
BIMI record present.
BIMI draft
pass
BIMI logo (l=) is published over https.
BIMI draft
logo https://bimi.entrust.net/cgi.com/logo.svg
svgConfirmed true
info
Verified Mark Certificate published (Gmail requires a VMC or CMC to show the logo).
BIMI draft
vmc https://bimi.entrust.net/cgi.com/certchain.pem
12Email Verification Protocol
info
No Email Verification Protocol record. Browsers cannot verify addresses at this domain without sending an email.
EVP draft
About this report
This report grades the email and DNS setup of cgi.com against the relevant RFCs. Each check links to the standard behind the rule. A high grade means the common causes of spoofing and poor deliverability are covered. A grade is not a guarantee that every message reaches the inbox.
Frequently asked questions
What does the grade mean?
The grade summarizes how completely the domain implements the core email authentication and DNS standards. A and B mean the main protections (SPF, DKIM, DMARC, valid MX) are in place. Lower grades flag gaps that make spoofing easier or hurt deliverability. A missing MX record caps the grade at F, a weak SPF all-qualifier caps at D, and no DMARC caps at C.
How fresh is this report?
A report is a snapshot from when it was last scanned, kept as a shareable link. If you are fixing your setup, use the Re-scan button to run every check live again.
Why is the SMTP section still loading?
The live SMTP probe connects to the mail servers from a dedicated prober, which takes a few seconds and runs separately from the DNS checks. The results stream in when ready. If SMTP was not requested for this report, that section stays empty.
I own this domain and want to stop scan.mx checking it.
Domain owners can block scanning by publishing a DNS TXT record; see the opt-out page.