SurfaceMap › u › us.com

us.com

Checked 2026-10-22 11:16 UTC · first added 2026-10-21

✗Problems found Score 62 of 100

Domain & DNS

warn

27 passed 3 warn 0 failed

Areas

iRegistration iDelegation iNameservers !SOA !DNSSEC !Records

Problems

!

Unusual SOA timers

SOA · refresh 15m is outside 20m–1d; retry 30m should be shorter than refresh 15m. Current values: refresh 15m, retry 30m, expire 70d, negative TTL 1h.

#23
!

Deprecated algorithm

DNSSEC · SHA-1 based algorithms are deprecated and rejected by some validators: RSASHA1-NSEC3-SHA1 (7). Roll over to ECDSAP256SHA256 (13).

#29
!

Very low TTLs

Records · These records have a TTL below 5m, causing extra queries and slower lookups: MX (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 1h; resolvers may use either.

#32

Recent checks

!

Full report

Domain & DNS report for us.com ›

Mail

fail

17 passed 3 warn 2 failed

Areas

✓SPF ✗DMARC ✗DKIM ✓DNSSEC !MX !TLS iBIMI

Problems

✗

No DMARC record

DMARC · No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.

#5
✗

No DKIM keys published

DKIM · _domainkey.us.com does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.

#7
!

Hosts without IPv6

MX · The following MX hosts could not be resolved to IPv6 addresses: mx-01.emailme.com

#11
!

Single MX host, no backup

MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.

#12
!

Not configured

TLS · MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.

#32

Recent checks

✗

Full report

Mail report for us.com ›