visitsaudi.com

Checked 22 October 2026, 11:22 UTC · via 8.8.8.8
✗Problems found
22 passed 4 warnings 1 failed 4 info

Registration

info

.com generic · GoDaddy.com, LLC · expires 2031-06-23

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
GoDaddy.com, LLC
Registered
23 June 2010
Last changed
30 September 2026
Expires
23 June 2031
Status
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
Registry nameservers
pdns13.domaincontrol.com, pdns14.domaincontrol.com
RDAP server
https://rdap.verisign.com/com/v1/

Checks

  • i
    .com is a generic TLD (gTLD)
    Generic TLD under an ICANN registry agreement: ICANN-accredited registrars, UDRP and RDAP apply.
    #1
  • ✓ TLD delegated and signed #2
    .com is delegated in the root zone and DNSSEC-signed.
  • ✓ Expires on 2031-06-23 #3
    The registration is valid until 2031-06-23 (1705 days).
  • ✓ Transfer locked #4
    Registry status: client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

pdns13.domaincontrol.com, pdns14.domaincontrol.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
pdns13.domaincontrol.com, pdns14.domaincontrol.com
NS in the zone
nsa1.dnetns.com, nsa2.dnetns.com, pdns13.domaincontrol.com, pdns14.domaincontrol.com
NameserverAddressesNetwork (AS)Glue
nsa1.dnetns.com (zone only)34.166.101.62AS396982 GOOGLE-CLOUD-PLATFORM - Google LLC, US-
nsa2.dnetns.com (zone only)81.208.171.185AS31898 ORACLE-BMC-31898 - Oracle Corporation, US-
pdns13.domaincontrol.com97.74.110.56AS44273 GODADDY-DNS - Host Europe GmbH, DE97.74.110.56
pdns14.domaincontrol.com173.201.78.56AS44273 GODADDY-DNS - Host Europe GmbH, DE173.201.78.56

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: pdns13.domaincontrol.com, pdns14.domaincontrol.com.
    #6
  • !
    NS sets differ
    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 glue needed #8
    All nameservers are outside the zone, so no glue records are needed.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 4 IPv4 /24s and 0 IPv6 /48s.
  • ✓ 3 autonomous systems #11
    The nameservers are spread over: AS31898 (ORACLE-BMC-31898 - Oracle Corporation, US): 1 address; AS396982 (GOOGLE-CLOUD-PLATFORM - Google LLC, US): 1 address; AS44273 (GODADDY-DNS - Host Europe GmbH, DE): 2 addresses.
  • i
    All nameserver names under .com
    All nameserver names are under one TLD, so a problem with that TLD also makes the nameservers unreachable. Some operators use names under two TLDs for extra resilience.
    #12
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

warn

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
nsa1.dnetns.com 34.166.101.62NOERROR, 87 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.9.5 (built Aug 25 2025 23:00:00 by pbuilder@bh-ubuntu-22.dev.cpanel.net)
nsa2.dnetns.com 81.208.171.185NOERROR, 66 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.9.17 (built Aug 9 2026 23:00:00 by pbuilder@bh-ubuntu-22.dev.cpanel.net)
pdns13.domaincontrol.com 97.74.110.56NOERROR, 3 ms, authoritativenoyes / yesrefused-
pdns14.domaincontrol.com 173.201.78.56NOERROR, 3 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 4 nameserver addresses answered.
  • ✓ All authoritative #15
    Every responding nameserver answers authoritatively for the zone.
  • ✓ No recursion #16
    The nameservers do not answer recursive queries for other domains.
  • !
    Software version disclosed
    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
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✓ TCP supported #19
    All nameservers answer over TCP.
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

warn

serial 2026093002 · primary nsa1.dnetns.com

Found

Primary (MNAME)
nsa1.dnetns.com
Contact (RNAME)
admin.dnet.sa
Serial
2026093002
Refresh / retry
3600 s / 1800 s
Expire
1209600 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
nsa1.dnetns.com (34.166.101.62)2026093002
nsa2.dnetns.com (81.208.171.185)2026093002
pdns13.domaincontrol.com (97.74.110.56)2026093006
pdns14.domaincontrol.com (173.201.78.56)2026093006

Checks

  • !
    Serials differ
    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
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 30m, expire 14d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver nsa1.dnetns.com is one of the listed nameservers.
  • ✓ Contact admin@dnet.sa #25
    The SOA RNAME admin.dnet.sa means admin@dnet.sa.
  • ✓ Date-based serial #26
    The serial 2026093002 follows the YYYYMMDDnn convention (2026-09-30).

DNSSEC

fail

DS at parent, but zone is not signed

Found

Validated by resolver
yes

DS at the parent

Key tagAlgorithmDigestMatches a key
1913ECDSAP256SHA256 (13)SHA256 79F624905C7D6946…NO
48680ECDSAP256SHA256 (13)SHA256 4658D48B027E3436…NO

Checks

  • ✗
    DS without signed zone
    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

Records

info

3 records at the apex

Found

Read from
34.166.101.62:53
TypeValueTTL
SOAnsa1.dnetns.com. admin.dnet.sa. 2026093002 3600 1800 1209600 8640086400
NSnsa2.dnetns.com.86400
NSnsa1.dnetns.com.86400

Checks

  • ✓ TTLs within range #32
    TTLs: NS 1d. The NS TTL at the parent is 2d and in the zone 1d; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • i
    No CAA records
    Without CAA records any certificate authority may issue certificates for this domain. A CAA record limits issuance to the CAs you use.
    #35