SurfaceMap › w › wattsupwiththat.com

wattsupwiththat.com

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

✗Problems found Score 62 of 100

Domain & DNS

warn

23 passed 2 warn 0 failed

Areas

iRegistration !Delegation iNameservers ✓SOA !DNSSEC iRecords

Problems

!

Glue differs from the zone

Delegation · The addresses at the parent (glue) differ from the addresses in the zone: ns5.openhostingservice.com (glue 192.0.75.14, 2620:115:c00f::c000:4b0e, zone 192.0.75.14). Update the glue at your registrar.

#8
!

Not signed

DNSSEC · The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.

#27

Recent checks

!

Full report

Domain & DNS report for wattsupwiththat.com ›

Mail

fail

18 passed 4 warn 2 failed

Areas

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

Problems

✗

Policy: none (monitoring only)

DMARC · DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.

#4
✗

No DKIM keys published

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

#7
!

Not enabled

DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.

#8
!

Hosts without IPv6

MX · The following MX hosts could not be resolved to IPv6 addresses: mx1.titan.email, mx2.titan.email

#11
!

No aggregate reports (rua)

DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...

#19
!

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 wattsupwiththat.com ›