SurfaceMap › a › admin5.com

admin5.com

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

Domain & DNS

fail

20 passed 4 warn 1 failed

Areas

iRegistration !Delegation ✓Nameservers !SOA !DNSSEC ✗Records

Problems

  • ✗
    CNAME at the apex
    Records · The zone apex is a CNAME to admin5.com.w.kunlunaq.com. A CNAME can't coexist with the SOA and NS records (RFC 1034); use your provider's ALIAS/flattening feature instead.
    #33
  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: vip3.alidns.com (glue 121.40.6.163, 140.205.1.5, 170.33.32.210, 170.33.73.26, 170.33.80.10, 2408:4009:500::3, 39.103.26.212, 47.108.36.163, 47.116.84.178, 8.129.152.245, 8.212.93.3, zone 170.33.73.26, 8.212.93.3, 170.33.32.210, 170.33.80.10, 140.205.1.5, 2408:4009:500::3); vip4.alidns.com (glue 121.40.6.164, 140.205.1.6, 170.33.32.211, 170.33.73.27, 170.33.80.11, 2408:4009:500::4, 39.103.26.213, 47.108.36.164, 47.116.84.179, 8.129.152.246, 8.212.93.4, zone 8.212.93.4, 140.205.1.6, 170.33.73.27, 170.33.80.11, 170.33.32.211, 2408:4009:500::4). Update the glue at your registrar.
    #8
  • !
    Serials differ
    SOA · The nameservers serve different versions of the zone: 2016120111 on vip3.alidns.com (8.212.93.3), vip4.alidns.com (8.212.93.4), vip4.alidns.com (170.33.80.11); 2026081716 on vip3.alidns.com (170.33.73.26), vip4.alidns.com (170.33.32.211); 2026081810 on vip3.alidns.com (140.205.1.5), vip4.alidns.com (140.205.1.6), vip4.alidns.com (170.33.73.27), vip4.alidns.com (2408:4009:500::4); 2026082415 on vip3.alidns.com (2408:4009:500::3); 2026082516 on vip3.alidns.com (170.33.32.210), vip3.alidns.com (170.33.80.10). 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 admin5.com ›

Mail

fail

0 passed 2 warn 3 failed

Areas

✗SPF ✗DMARC ✗DKIM !DNSSEC !MX 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
  • ✗
    No DKIM keys published
    DKIM · _domainkey.admin5.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
  • !
    No MX records
    MX · No MX records found. If this domain is used for email, add MX records to specify mail servers. If it never receives mail, publish a null MX ("MX 0 .").
    #9

Recent checks

✗

Full report

Mail report for admin5.com ›