SurfaceMap › l › london2012.com

london2012.com

Checked 2026-10-22 09:40 UTC · first added 2026-10-21
✗Problems found Score 53 of 100

Domain & DNS

warn

22 passed 4 warn 0 failed

Areas

iRegistration !Delegation ✓Nameservers !SOA !DNSSEC iRecords

Problems

  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: vip7.alidns.com (glue 121.40.6.167, 140.205.1.13, 170.33.32.214, 170.33.80.14, 2408:4009:500::7, 39.103.26.216, 47.108.36.167, 47.253.24.27, 47.254.160.176, 47.74.160.227, 47.88.82.208, 8.212.93.7, zone 170.33.32.214, 140.205.1.13, 47.88.82.208, 170.33.80.14, 47.254.160.176, 8.212.93.7, 47.253.24.27, 2408:4009:500::7); vip8.alidns.com (glue 121.40.6.168, 140.205.1.14, 170.33.32.215, 170.33.80.15, 2408:4009:500::8, 39.103.26.217, 47.108.36.168, 47.253.24.28, 47.254.160.177, 47.74.160.228, 47.88.82.209, 8.212.93.8, zone 170.33.32.215, 170.33.80.15, 47.88.82.209, 8.212.93.8, 47.253.24.28, 140.205.1.14, 47.254.160.177, 2408:4009:500::8). Update the glue at your registrar.
    #8
  • !
    Serials differ
    SOA · The nameservers serve different versions of the zone: 2022061416 on vip7.alidns.com (8.212.93.7); 2026081316 on vip8.alidns.com (8.212.93.8); 2026081710 on vip7.alidns.com (47.88.82.208), vip8.alidns.com (47.88.82.209); 2026081716 on vip8.alidns.com (170.33.32.215), vip8.alidns.com (170.33.80.15); 2026081810 on vip7.alidns.com (170.33.32.214), vip7.alidns.com (140.205.1.13), vip8.alidns.com (47.253.24.28), vip8.alidns.com (140.205.1.14), vip8.alidns.com (47.254.160.177); 2026081812 on vip7.alidns.com (47.253.24.27); 2026082415 on vip7.alidns.com (47.254.160.176), vip7.alidns.com (2408:4009:500::7), vip8.alidns.com (2408:4009:500::8); 2026082516 on vip7.alidns.com (170.33.80.14). 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 · expire 1d is shorter than 7d; secondaries stop answering too soon when the primary is down. Current values: refresh 1h, retry 20m, expire 1d, negative TTL 10m.
    #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 london2012.com ›

Mail

fail

9 passed 5 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 SPF record
    SPF · No SPF record was found for this domain. SPF is important for preventing email spoofing. Add an SPF record to specify which servers are authorized to send email for your domain.
    #6
  • !
    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: cluster4.eu.messagelabs.com, cluster4a.eu.messagelabs.com
    #11
  • !
    Unreadable DKIM key
    DKIM · These keys could not be parsed, so signatures made with them will fail: k1 (RSA public key could not be parsed).
    #23
  • !
    Key in test mode
    DKIM · These keys have t=y, so receivers treat DKIM failures as a test: k1. Remove t=y once DKIM works.
    #24
  • !
    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 london2012.com ›