SurfaceMap › s › strategyzer.com

strategyzer.com

Checked 2026-10-22 10:52 UTC · first added 2026-10-21

✗Problems found Score 78 of 100

Domain & DNS

warn

24 passed 2 warn 0 failed

Areas

iRegistration iDelegation iNameservers !SOA !DNSSEC iRecords

Problems

!

Serials differ

SOA · The nameservers serve different versions of the zone: 1436399117 on ns5.dnsmadeeasy.com (208.94.148.13), ns5.dnsmadeeasy.com (2600:1800:5::1), ns6.dnsmadeeasy.com (208.80.124.13), ns6.dnsmadeeasy.com (2600:1801:6::1), ns7.dnsmadeeasy.com (208.80.126.13), ns7.dnsmadeeasy.com (2600:1802:7::1); 1436399118 on ns1.dnsimple.com (199.247.152.53), ns1.dnsimple.com (2620:111:8004::53), ns2.dnsimple.com (199.247.153.53), ns2.dnsimple.com (2620:111:8005::53), ns3.dnsimple.com (199.247.154.53), ns3.dnsimple.com (2620:111:8006::53), ns4.dnsimple.com (199.247.155.53), ns4.dnsimple.com (2620:111:8007::53). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.

#22
!

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

Mail

fail

24 passed 2 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
!

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