C
Scanned 15 days ago. Re-scan for a fresh result after a fix.
Issues to fix
- failServer did not greet with 220 (got no reply).→
- failServer did not accept EHLO or HELO.→
- failSTARTTLS is not advertised; mail to this host is delivered in cleartext.→
- warnp=none: monitoring only, unauthenticated mail is not blocked.→
- warnAll MX hosts resolve to a single IP, no address-level redundancy.→
- warnNo TLS-RPT reporting address. TLS delivery failures go unreported.→
Results
01Mail exchangers (MX)A
pass
1 MX record(s) found.
records
| preference | exchange | ttl |
|---|---|---|
| 0 | adentcom.mx | 14400 |
info
Only one MX host, a secondary MX adds delivery resilience.
warn
All MX hosts resolve to a single IP, no address-level redundancy.
ip 198.23.59.249
02Mail providerA
info
Mail is handled by adentcom.mx, a self-hosted or independent provider.
provider adentcom.mx
03SPFA
pass
SPF record present.
record v=spf1 +a +mx +ip4:170.10.163.98 ~all
pass
SPF uses 2 of the 10 permitted DNS lookups.
lookups 2
pass
~all default policy.
04DKIMA
pass
Selector default key is ~2048-bit.
selector default
record v=DKIM1; k=rsa; 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 1 published key(s) carry over as they are. Adding an Ed25519 key (RFC 8463) prepares for it.
draft-ietf-dkim-dkim2-spec
keys 1
ed25519 false
05DMARCA
pass
DMARC record present.
record v=DMARC1; p=none;
warn
p=none: monitoring only, unauthenticated mail is not blocked.
p none
rua false
06DNS healthA
07BlacklistsA
pass
198.23.59.249 is not listed on PSBL.
target 198.23.59.249
list PSBL
pass
adentcom.mx is not listed on Spamhaus ZRD.
target adentcom.mx
list Spamhaus ZRD
pass
198.23.59.249 is not listed on Spamhaus ZEN.
target 198.23.59.249
list Spamhaus ZEN
pass
198.23.59.249 is not listed on GBUdb Truncate.
target 198.23.59.249
list GBUdb Truncate
pass
adentcom.mx is not listed on Spamhaus DBL.
target adentcom.mx
list Spamhaus DBL
pass
198.23.59.249 is not listed on SpamCop.
target 198.23.59.249
list SpamCop
pass
198.23.59.249 is not listed on Spamhaus AuthBL.
target 198.23.59.249
list Spamhaus AuthBL
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 adentcom.mx
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 adentcom.mx
pass
1 of 1 MX host(s) reachable on port 25.
reachable adentcom.mx
unreachable (none)
fail
Server did not greet with 220 (got no reply).
banner
info
Could not compare banner hostname to reverse DNS.
banner_fqdn
ptr akkyhosting2.mx
fail
Server did not accept EHLO or HELO.
fail
STARTTLS is not advertised; mail to this host is delivered in cleartext.
info
Open-relay test was inconclusive (server did not reach the recipient stage).
info
Null-sender test was inconclusive.
About this report
This report grades the email and DNS setup of adentcom.mx 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.