SurfaceMap › z › zazzle.be

zazzle.be

Checked 2026-10-22 07:30 UTC · first added 2026-10-21
✗Problems found Score 63 of 100

Domain & DNS

warn

20 passed 5 warn 0 failed

Areas

iRegistration !Delegation iNameservers !SOA !DNSSEC ✓Records

Problems

  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only in the zone: ns07.zazzle.net, ns08.zazzle.net. ns01.zazzle.net, ns02.zazzle.net, ns03.zazzle.net, ns04.zazzle.net, ns05.zazzle.net, ns06.zazzle.net, ns07.zazzle.net, ns08.zazzle.net report NS ns01.zazzle.net ns02.zazzle.net ns03.zazzle.net ns04.zazzle.net ns05.zazzle.net ns06.zazzle.net ns07.zazzle.net ns08.zazzle.net.
    #7
  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    Serials differ
    SOA · The nameservers serve different versions of the zone: 1639417566 on ns05.zazzle.net (198.51.44.6), ns06.zazzle.net (198.51.45.6), ns07.zazzle.net (198.51.44.70), ns08.zazzle.net (198.51.45.70); 2016100435 on ns01.zazzle.net (156.154.64.55), ns02.zazzle.net (156.154.65.55), ns03.zazzle.net (156.154.66.55), ns04.zazzle.net (156.154.67.55). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.
    #22
  • !
    Unusual SOA timers
    SOA · refresh 28h57m13s is outside 20m–1d; negative caching TTL (minimum) 140h4m6s is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 28h57m13s, retry 14h28m36s, expire 202h40m31s, negative TTL 140h4m6s.
    #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 zazzle.be ›

Mail

fail

22 passed 4 warn 1 failed

Areas

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

Problems

  • ✗
    No DKIM keys published
    DKIM · _domainkey.zazzle.be 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: mxa-001c4901.gslb.pphosted.com, mxb-001c4901.gslb.pphosted.com
    #11
  • !
    Subdomains unprotected (sp=none)
    DMARC · DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.
    #20
  • !
    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 zazzle.be ›