SurfaceMap › r › runoob.com

runoob.com

Checked 2026-10-22 10:33 UTC · first added 2026-10-21
✗Problems found Score 43 of 100

Domain & DNS

warn

21 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: vip1.alidns.com (glue 121.40.6.161, 140.205.1.1, 170.33.32.208, 170.33.73.24, 170.33.80.8, 2408:4009:500::1, 39.103.26.210, 47.116.84.176, 8.129.152.243, 8.212.93.1, zone 8.212.93.1, 140.205.1.1, 170.33.32.208, 170.33.73.24, 170.33.80.8, 2408:4009:500::1); vip2.alidns.com (glue 121.40.6.162, 140.205.1.2, 170.33.32.209, 170.33.73.25, 170.33.80.9, 2408:4009:500::2, 39.103.26.211, 47.116.84.177, 8.129.152.244, 8.212.93.2, zone 170.33.80.9, 8.212.93.2, 170.33.73.25, 140.205.1.2, 170.33.32.209, 2408:4009:500::2). Update the glue at your registrar.
    #8
  • !
    Serials differ
    SOA · The nameservers serve different versions of the zone: 2015062412 on vip1.alidns.com (8.212.93.1), vip1.alidns.com (140.205.1.1); 2026081712 on vip1.alidns.com (170.33.32.208), vip2.alidns.com (170.33.32.209); 2026081810 on vip1.alidns.com (170.33.80.8), vip1.alidns.com (2408:4009:500::1), vip2.alidns.com (170.33.80.9), vip2.alidns.com (8.212.93.2), vip2.alidns.com (170.33.73.25), vip2.alidns.com (2408:4009:500::2); 2026082415 on vip2.alidns.com (140.205.1.2); 2026082516 on vip1.alidns.com (170.33.73.24). 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 runoob.com ›

Mail

fail

6 passed 5 warn 3 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
  • ✗
    No DKIM keys published
    DKIM · _domainkey.runoob.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
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    Hosts are CNAMEs
    MX · MX records must point to a host name with A/AAAA records, not to a CNAME: mxdomain.qq.com -> mx3.qq.com
    #22
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 203.205.219.57 (mxdomain.qq.com), 240d:c040:1:40::133 (mxdomain.qq.com). Ask your hosting provider to set one.
    #30
  • !
    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 runoob.com ›