SurfaceMap › v › visitsaudi.com

visitsaudi.com

Checked 2026-10-22 11:22 UTC · first added 2026-10-21
!Check could not complete

Domain & DNS

fail

22 passed 4 warn 1 failed

Areas

iRegistration !Delegation !Nameservers !SOA ✗DNSSEC iRecords

Problems

  • ✗
    DS without signed zone
    DNSSEC · The parent publishes a DS record but the zone has no DNSKEY records, so validating resolvers will reject it. Remove the DS record or sign the zone.
    #27
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only in the zone: nsa1.dnetns.com, nsa2.dnetns.com. nsa1.dnetns.com, nsa2.dnetns.com report NS nsa1.dnetns.com nsa2.dnetns.com. pdns13.domaincontrol.com, pdns14.domaincontrol.com report NS nsa1.dnetns.com nsa2.dnetns.com pdns13.domaincontrol.com pdns14.domaincontrol.com.
    #7
  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: nsa1.dnetns.com: "PowerDNS Authoritative Server 4.9.5 (built Aug 25 2025 23:00:00 by pbuilder@bh-ubuntu-22.dev.cpanel.net)"; nsa2.dnetns.com: "PowerDNS Authoritative Server 4.9.17 (built Aug 9 2026 23:00:00 by pbuilder@bh-ubuntu-22.dev.cpanel.net)". Hide or replace the version string.
    #17
  • !
    Serials differ
    SOA · The nameservers serve different versions of the zone: 2026093002 on nsa1.dnetns.com (34.166.101.62), nsa2.dnetns.com (81.208.171.185); 2026093006 on pdns13.domaincontrol.com (97.74.110.56), pdns14.domaincontrol.com (173.201.78.56). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.
    #22

Recent checks

✗

Full report

Domain & DNS report for visitsaudi.com ›

Mail

error

27 passed 3 warn 0 failed 1 errors

lookups failed for tls-rpt; results are incomplete

Areas

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

Problems

  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: selector1 (1024 bits), s2 (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    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 visitsaudi.com ›