sify.com

Checked 22 October 2026, 10:42 UTC · via 8.8.8.8
✗Problems found
22 passed 3 warnings 1 failed 5 info

Registration

info

.com generic · PDR Ltd. d/b/a PublicDomainRegistry.com · expires 2029-06-21

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
PDR Ltd. d/b/a PublicDomainRegistry.com
Registered
21 June 1999
Last changed
8 November 2023
Expires
21 June 2029
Status
client transfer prohibited
Registry nameservers
pdns.satyam.net.in, sdns.satyam.net.in
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 2029-06-21 #3
    The registration is valid until 2029-06-21 (973 days).
  • ✓ Transfer locked #4
    Registry status: client transfer prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

pdns.satyam.net.in, sdns.satyam.net.in

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
pdns.satyam.net.in, sdns.satyam.net.in
NS in the zone
pdns.satyam.net.in, sdns.satyam.net.in
NameserverAddressesNetwork (AS)Glue
pdns.satyam.net.in202.144.63.4 2001:e48:9584::aAS9583 SIFY-AS-IN - Sify Limited, IN AS9583 SIFY-AS-IN - Sify Limited, IN-
sdns.satyam.net.in202.144.63.12 2001:e48:9584::aAS9583 SIFY-AS-IN - Sify Limited, IN AS9583 SIFY-AS-IN - Sify Limited, IN-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: pdns.satyam.net.in, sdns.satyam.net.in.
    #6
  • ✓ 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 one network
    all IPv4 addresses are in 202.144.63.0/24; all IPv6 addresses are in 2001:e48:9584::/48. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS9583 (SIFY-AS-IN - Sify Limited, IN): 4 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 .in
    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

fail

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
pdns.satyam.net.in 202.144.63.4NOERROR, 177 ms, authoritativenono / norefused-
pdns.satyam.net.in 2001:e48:9584::aNOERROR, 145 ms, authoritativenono / norefused-
sdns.satyam.net.in 202.144.63.12NOERROR, 122 ms, authoritativenono / norefused-
sdns.satyam.net.in 2001:e48:9584::aNOERROR, 149 ms, authoritativenono / norefused-

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.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✗
    No DNS over TCP
    DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: pdns.satyam.net.in (202.144.63.4): dial tcp 202.144.63.4:53: connect: connection refused; pdns.satyam.net.in (2001:e48:9584::a): read tcp [2a01:4f8:1c1c:eebf::1]:45184->[2001:e48:9584::a]:53: read: connection reset by peer; sdns.satyam.net.in (202.144.63.12): dial tcp 202.144.63.12:53: connect: connection refused; sdns.satyam.net.in (2001:e48:9584::a): EOF.
    #19
  • !
    No EDNS
    These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: pdns.satyam.net.in (202.144.63.4), pdns.satyam.net.in (2001:e48:9584::a), sdns.satyam.net.in (202.144.63.12), sdns.satyam.net.in (2001:e48:9584::a).
    #20
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2000102363 · primary pdns.satyam.net.in

Found

Primary (MNAME)
pdns.satyam.net.in
Contact (RNAME)
dnsadmin.satyam-infoway.com
Serial
2000102363
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
pdns.satyam.net.in (202.144.63.4)2000102363
pdns.satyam.net.in (2001:e48:9584::a)2000102363
sdns.satyam.net.in (202.144.63.12)2000102363
sdns.satyam.net.in (2001:e48:9584::a)2000102363

Checks

  • ✓ Serial 2000102363 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver pdns.satyam.net.in is one of the listed nameservers.
  • ✓ Contact dnsadmin@satyam-infoway.com #25
    The SOA RNAME dnsadmin.satyam-infoway.com means dnsadmin@satyam-infoway.com.
  • ✓ Date-based serial #26
    The serial 2000102363 follows the YYYYMMDDnn convention (2000-10-23).

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

info

8 records at the apex

Found

Read from
202.144.63.4:53
TypeValueTTL
SOApdns.satyam.net.in. dnsadmin.satyam-infoway.com. 2000102363 10800 3600 604800 36003600
NSpdns.satyam.net.in.21600
NSsdns.satyam.net.in.21600
A3.111.210.243600
AAAA2001:e48:0:104::63600
MX0 sify-com.mail.protection.outlook.com.3600
TXT"IUOqVfDkWP3ru6FRBmXuNmbYvXVVuYet3r3O/+Ire3E="1800
TXT"v=spf1 include:spf.protection.outlook.com -all"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 10m, AAAA 1h, MX 1h, NS 6h. The NS TTL at the parent is 2d and in the zone 6h; 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