A
Scanned 14 days ago. Re-scan for a fresh result after a fix.
Issues to fix
- warnp=none: monitoring only, unauthenticated mail is not blocked.→
- warnMX host mx1.hostinger.com (172.65.182.103) has no PTR record, many receivers reject senders without reverse DNS.→
- warnMX host mx2.hostinger.com (172.65.182.103) has no PTR record, many receivers reject senders without reverse DNS.→
- warnMX host mx2.hostinger.com (2606:4700:90:0:c1f8:f874:2386:b61f) has no PTR record, many receivers reject senders without reverse DNS.→
- warnMX host mx1.hostinger.com (2606:4700:90:0:c1f8:f874:2386:b61f) has no PTR record, many receivers reject senders without reverse DNS.→
- warnPartial bulk-sender setup, missing DKIM. Gmail/Yahoo and Microsoft require all three for 5,000+ messages/day.→
- warnNo TLS-RPT reporting address. TLS delivery failures go unreported.→
- warnGreeting is 220 but announces no FQDN.→
Results
01Mail exchangers (MX)A
pass
2 MX record(s) found.
records
| preference | exchange | ttl |
|---|---|---|
| 5 | mx1.hostinger.com | 14400 |
| 10 | mx2.hostinger.com | 14400 |
02Mail providerA
info
Mail is handled by hostinger.com, a self-hosted or independent provider.
provider hostinger.com
03SPFA
pass
SPF record present.
record v=spf1 include:_spf.mail.hostinger.com ~all
pass
SPF uses 3 of the 10 permitted DNS lookups.
lookups 3
pass
~all default policy.
04DKIMA
info
No DKIM selector found via common probes (a _domainkey subtree exists but no common selector matched), the domain may use a custom selector.
05DMARCA
pass
DMARC record present.
record v=DMARC1; p=none
warn
p=none: monitoring only, unauthenticated mail is not blocked.
p none
06DNS healthC
warn
MX host mx1.hostinger.com (172.65.182.103) has no PTR record, many receivers reject senders without reverse DNS.
host mx1.hostinger.com
ip 172.65.182.103
warn
MX host mx2.hostinger.com (172.65.182.103) has no PTR record, many receivers reject senders without reverse DNS.
host mx2.hostinger.com
ip 172.65.182.103
warn
MX host mx2.hostinger.com (2606:4700:90:0:c1f8:f874:2386:b61f) has no PTR record, many receivers reject senders without reverse DNS.
host mx2.hostinger.com
ip 2606:4700:90:0:c1f8:f874:2386:b61f
warn
MX host mx1.hostinger.com (2606:4700:90:0:c1f8:f874:2386:b61f) has no PTR record, many receivers reject senders without reverse DNS.
host mx1.hostinger.com
ip 2606:4700:90:0:c1f8:f874:2386:b61f
pass
2 nameservers published.
count 2
pass
SOA timers are sane.
mname orbit.dns-parking.com.
rname dns.hostinger.com.
refresh 10000
retry 2400
expire 604800
minimum 600
info
Zone is not DNSSEC-signed.
07BlacklistsA
info
IPv6 MX addresses are not checked against IP DNSBLs.
pass
172.65.182.103 is not listed on SpamCop.
target 172.65.182.103
list SpamCop
pass
172.65.182.103 is not listed on Spamhaus AuthBL.
target 172.65.182.103
list Spamhaus AuthBL
pass
graffmode.com is not listed on Spamhaus DBL.
target graffmode.com
list Spamhaus DBL
pass
graffmode.com is not listed on Spamhaus ZRD.
target graffmode.com
list Spamhaus ZRD
pass
172.65.182.103 is not listed on Spamhaus ZEN.
target 172.65.182.103
list Spamhaus ZEN
pass
172.65.182.103 is not listed on GBUdb Truncate.
target 172.65.182.103
list GBUdb Truncate
pass
172.65.182.103 is not listed on PSBL.
target 172.65.182.103
list PSBL
08Bulk sending readinessA
warn
Partial bulk-sender setup, missing DKIM. Gmail/Yahoo and Microsoft require all three for 5,000+ messages/day.
spf true
dkim false
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 mx1.hostinger.com, mx2.hostinger.com
pass
Negotiated TLSv1.3.
tls_version TLSv1.3
host mx1.hostinger.com
pass
Certificate valid for 160 more day(s).
not_after 2027-01-16T23:59:59+00:00
host mx1.hostinger.com
pass
Certificate covers mx1.hostinger.com.
names hostinger.com, *.hosting24.com, *.hostinger.ae, *.hostinger.co, *.hostinger.co.id, *.hostinger.co.il, *.hostinger.co.uk, *.hostinger.com, *.hostinger.com.ar, *.hostinger.com.br, *.hostinger.com.hk, *.hostinger.com.ua, *.hostinger.cz, *.hostinger.de, *.hostinger.dk, *.hostinger.ee, *.hostinger.es, *.hostinger.eu, *.hostinger.fi, *.hostinger.fr, *.hostinger.gr, *.hostinger.hr, *.hostinger.hu, *.hostinger.in, *.hostinger.in.th, *.hostinger.it, *.hostinger.jp, *.hostinger.kr, *.hostinger.lt, *.hostinger.lv, *.hostinger.mx, *.hostinger.my, *.hostinger.nl, *.hostinger.no, *.hostinger.ph, *.hostinger.pl, *.hostinger.pt, *.hostinger.ro, *.hostinger.se, *.hostinger.sk, *.hostinger.vn, *.hostinger.web.tr, *.hostmania.es, *.hstgr.io, *.main-hosting.eu, *.niagahoster.co.id, *.weblink.com.br, *.zyro.com
host mx1.hostinger.com
pass
Server presented a 4-certificate chain.
chain_len 4
host mx1.hostinger.com
10MTA-STSA
11BIMIA
info
No BIMI record. No brand logo is published for inboxes with BIMI support.
BIMI draft
SMTP (live probe)
info
No DANE/TLSA records. DANE is not deployed for these mail servers.
hosts mx1.hostinger.com, mx2.hostinger.com
pass
2 of 2 MX host(s) reachable on port 25.
reachable mx1.hostinger.com, mx2.hostinger.com
unreachable (none)
warn
Greeting is 220 but announces no FQDN.
banner 220-ESMTP mx.hostinger.com
info
Could not compare banner hostname to reverse DNS.
banner_fqdn
ptr
pass
EHLO accepted with 7 extension(s).
extensions 8BITMIME, CHUNKING, DSN, ENHANCEDSTATUSCODES, ETRN, PIPELINING, SIZE
info
Server does not advertise SMTPUTF8; internationalized (EAI) addresses may be rejected.
pass
STARTTLS is advertised in EHLO.
pass
STARTTLS negotiated a working TLS session.
tls_version TLSv1.3
pass
Negotiated TLSv1.3.
tls_version TLSv1.3
host mx1.hostinger.com
pass
Certificate valid for 160 more day(s).
not_after 2027-01-16T23:59:59+00:00
host mx1.hostinger.com
pass
Certificate covers mx1.hostinger.com.
names hostinger.com, *.hosting24.com, *.hostinger.ae, *.hostinger.co, *.hostinger.co.id, *.hostinger.co.il, *.hostinger.co.uk, *.hostinger.com, *.hostinger.com.ar, *.hostinger.com.br, *.hostinger.com.hk, *.hostinger.com.ua, *.hostinger.cz, *.hostinger.de, *.hostinger.dk, *.hostinger.ee, *.hostinger.es, *.hostinger.eu, *.hostinger.fi, *.hostinger.fr, *.hostinger.gr, *.hostinger.hr, *.hostinger.hu, *.hostinger.in, *.hostinger.in.th, *.hostinger.it, *.hostinger.jp, *.hostinger.kr, *.hostinger.lt, *.hostinger.lv, *.hostinger.mx, *.hostinger.my, *.hostinger.nl, *.hostinger.no, *.hostinger.ph, *.hostinger.pl, *.hostinger.pt, *.hostinger.ro, *.hostinger.se, *.hostinger.sk, *.hostinger.vn, *.hostinger.web.tr, *.hostmania.es, *.hstgr.io, *.main-hosting.eu, *.niagahoster.co.id, *.weblink.com.br, *.zyro.com
host mx1.hostinger.com
pass
Server presented a 4-certificate chain.
chain_len 4
host mx1.hostinger.com
pass
Server refused external relay, as expected.
reply 554 5.7.1 <relay-test@example.com>: Relay access denied
pass
Server accepts the null sender (MAIL FROM:<>), so bounces and DSNs can be delivered.
reply 250 2.1.0 Ok
About this report
This report grades the email and DNS setup of graffmode.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.