india.com

Checked 22 October 2026, 09:20 UTC · via 8.8.8.8
!Passed with warnings
23 passed 3 warnings 0 failed 5 info

Registration

info

.com generic · GoDaddy.com, LLC · expires 2030-05-30

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
GoDaddy.com, LLC
Registered
13 August 1997
Last changed
25 July 2025
Expires
30 May 2030
Status
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
Registry nameservers
a1-227.akam.net, a10-66.akam.net, a13-67.akam.net, a22-64.akam.net, a28-65.akam.net, a3-66.akam.net
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 2030-05-30 #3
    The registration is valid until 2030-05-30 (1315 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

info

a1-227.akam.net, a10-66.akam.net, a13-67.akam.net, a22-64.akam.net, a28-65.akam.net, a3-66.akam.net

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
a1-227.akam.net, a10-66.akam.net, a13-67.akam.net, a22-64.akam.net, a28-65.akam.net, a3-66.akam.net
NS in the zone
a1-227.akam.net, a10-66.akam.net, a13-67.akam.net, a22-64.akam.net, a28-65.akam.net, a3-66.akam.net
NameserverAddressesNetwork (AS)Glue
a1-227.akam.net193.108.91.227 2600:1401:2::e3AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a10-66.akam.net96.7.50.66 2600:1480:d000::42AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a13-67.akam.net2.22.230.67 2600:1480:800::43AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a22-64.akam.net23.211.61.64 2600:1480:7800::40AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a28-65.akam.net95.100.173.65 2600:1480:d800::41AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a3-66.akam.net96.7.49.66 2600:1408:1c::42AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-

Checks

  • ✓ 6 nameservers #6
    Delegated to a1-227.akam.net, a10-66.akam.net, a13-67.akam.net, a22-64.akam.net, a28-65.akam.net, a3-66.akam.net.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ 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 6 IPv4 /24s and 6 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS21342 (AKAMAI-ASN2 - Akamai International B.V., NL): 12 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • i
    All nameserver names under .net
    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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

12 of 12 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
a1-227.akam.net 193.108.91.227NOERROR, 4 ms, authoritativenoyes / yesrefused41824.8
a1-227.akam.net 2600:1401:2::e3NOERROR, 5 ms, authoritativenoyes / yesrefused41824.4
a10-66.akam.net 96.7.50.66NOERROR, 3 ms, authoritativenoyes / yesrefused48878.32
a10-66.akam.net 2600:1480:d000::42NOERROR, 4 ms, authoritativenoyes / yesrefused48878.31
a13-67.akam.net 2.22.230.67NOERROR, 5 ms, authoritativenoyes / yesrefused41824.5
a13-67.akam.net 2600:1480:800::43NOERROR, 6 ms, authoritativenoyes / yesrefused41824.5
a22-64.akam.net 23.211.61.64NOERROR, 3 ms, authoritativenoyes / yesrefused48878.26
a22-64.akam.net 2600:1480:7800::40NOERROR, 5 ms, authoritativenoyes / yesrefused48878.31
a28-65.akam.net 95.100.173.65NOERROR, 3 ms, authoritativenoyes / yesrefused48878.29
a28-65.akam.net 2600:1480:d800::41NOERROR, 4 ms, authoritativenoyes / yesrefused48878.29
a3-66.akam.net 96.7.49.66NOERROR, 4 ms, authoritativenoyes / yesrefused41824.11
a3-66.akam.net 2600:1408:1c::42NOERROR, 4 ms, authoritativenoyes / yesrefused41824.8

Checks

  • ✓ All respond #14
    All 12 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: a1-227.akam.net: "41824.8"; a1-227.akam.net: "41824.4"; a10-66.akam.net: "48878.32"; a10-66.akam.net: "48878.31"; a13-67.akam.net: "41824.5"; a22-64.akam.net: "48878.26"; a22-64.akam.net: "48878.31"; a28-65.akam.net: "48878.29"; a3-66.akam.net: "41824.11"; a3-66.akam.net: "41824.8". 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

pass

serial 182 · primary a1-227.akam.net

Found

Primary (MNAME)
a1-227.akam.net
Contact (RNAME)
hostmaster.akamai.com
Serial
182
Refresh / retry
7200 s / 900 s
Expire
1209600 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
a1-227.akam.net (193.108.91.227)182
a1-227.akam.net (2600:1401:2::e3)182
a10-66.akam.net (96.7.50.66)182
a10-66.akam.net (2600:1480:d000::42)182
a13-67.akam.net (2.22.230.67)182
a13-67.akam.net (2600:1480:800::43)182
a22-64.akam.net (23.211.61.64)182
a22-64.akam.net (2600:1480:7800::40)182
a28-65.akam.net (95.100.173.65)182
a28-65.akam.net (2600:1480:d800::41)182
a3-66.akam.net (96.7.49.66)182
a3-66.akam.net (2600:1408:1c::42)182

Checks

  • ✓ Serial 182 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 2h, retry 15m, expire 14d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver a1-227.akam.net is one of the listed nameservers.
  • ✓ Contact hostmaster@akamai.com #25
    The SOA RNAME hostmaster.akamai.com means hostmaster@akamai.com.
  • ✓ Counter serial #26
    The serial 182 is a plain counter.

DNSSEC

warn

Not signed

Found

Validated by resolver
no

Checks

  • !
    Not signed
    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

Records

warn

18 records at the apex

Found

Read from
193.108.91.227:53
TypeValueTTL
SOAa1-227.akam.net. hostmaster.akamai.com. 182 7200 900 1209600 86400300
NSa22-64.akam.net.86400
NSa13-67.akam.net.86400
NSa1-227.akam.net.86400
NSa10-66.akam.net.86400
NSa28-65.akam.net.86400
NSa3-66.akam.net.86400
A2.16.183.2020
A2.16.183.820
AAAA2a02:26f0:b700:18::210:ccd020
AAAA2a02:26f0:b700:18::210:ccc820
MX0 india-com.mail.protection.outlook.com.3600
TXT"MS=ms77740152"300
TXT"fh67zxh6lsmyc0w15t4qg4trwdwnbps6"300
TXT"4pptk5v1lvv7xf0kyp0c2q8qlg3k10yw"300
TXT"google-site-verification=PfFHWm4oUtKHVa8cTcohHf-QGio10nFaoYXwwfdCc-4"300
TXT"v=spf1 include:spf.protection.outlook.com -all"300
TXT"google-site-verification=e-J5w5kwvwcCfQG94KkbMte5XSOCG65d4mKzWd9MvbM"300

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (20s), AAAA (20s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 1d; resolvers may use either.
    #32
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • i
    Wildcard record
    A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.
    #34
  • 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