SurfaceMap › w › wwe.com

wwe.com

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

✗Problems found Score 69 of 100

Domain & DNS

warn

24 passed 3 warn 0 failed

Areas

iRegistration !Delegation iNameservers !SOA !DNSSEC ✓Records

Problems

!

Glue differs from the zone

Delegation · The addresses at the parent (glue) differ from the addresses in the zone: ns1.wwe.com (glue 38.81.102.100, zone 3.213.173.91); ns3.wwe.com (glue 74.201.147.144, zone 216.247.78.19). Update the glue at your registrar.

#8
!

Unusual SOA timers

SOA · retry 20m should be shorter than refresh 20m. Current values: refresh 20m, retry 20m, expire 14d, negative TTL 12h.

#23
!

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

Mail

fail

22 passed 4 warn 1 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
!

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: us-smtp-inbound-1.mimecast.com, us-smtp-inbound-2.mimecast.com

#11
!

1024-bit DKIM key

DKIM · 1024-bit RSA keys are the minimum and are considered weak today: dkim (1024 bits), s2 (1024 bits). Rotate to a 2048-bit key.

#23
!

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