ru.com

Checked 22 October 2026, 10:33 UTC · via 8.8.8.8
!Passed with warnings
27 passed 2 warnings 0 failed 6 info

Registration

info

.com generic · Sav.com, LLC · expires 2033-02-06

Found

TLD
.com (generic)
Public suffix
.ru.com
ICANN policies apply
yes
Registrar
Sav.com, LLC
Registered
5 February 1996
Last changed
9 May 2025
Expires
6 February 2033
Status
client transfer prohibited, server delete prohibited, server transfer prohibited, server update prohibited
Registry nameservers
ns1.centralnic.net, ns2.centralnic.net, ns3.centralnic.net, ns4.centralnic.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. Domains are registered under the public suffix .ru.com.
    #1
  • ✓ TLD delegated and signed #2
    .com is delegated in the root zone and DNSSEC-signed.
  • ✓ Expires on 2033-02-06 #3
    The registration is valid until 2033-02-06 (2298 days).
  • ✓ Transfer locked #4
    Registry status: client transfer prohibited, server delete prohibited, server transfer prohibited, server update prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

ns1.centralnic.net, ns2.centralnic.net, ns3.centralnic.net, ns4.centralnic.net

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.centralnic.net, ns2.centralnic.net, ns3.centralnic.net, ns4.centralnic.net
NS in the zone
ns1.centralnic.net, ns2.centralnic.net, ns3.centralnic.net, ns4.centralnic.net
NameserverAddressesNetwork (AS)Glue
ns1.centralnic.net194.169.218.24 2001:67c:13cc::1:24AS199330 CENTRALNIC-ANYCAST-A - CentralNic Ltd, GB AS199330 CENTRALNIC-ANYCAST-A - CentralNic Ltd, GB-
ns2.centralnic.net185.24.64.10 2a04:2b00:13cc::1:10AS60890 CENTRALNIC-ANYCAST-B - CentralNic Ltd, GB AS60890 CENTRALNIC-ANYCAST-B - CentralNic Ltd, GB-
ns3.centralnic.net212.18.248.10 2a04:2b00:13ee::10AS201304 CENTRALNIC-ANYCAST-E - CentralNic Ltd, GB AS201304 CENTRALNIC-ANYCAST-E - CentralNic Ltd, GB-
ns4.centralnic.net212.18.249.24 2a04:2b00:13ff::24AS201303 CentralNic-Anycast-F - CentralNic Ltd, GB AS201303 CentralNic-Anycast-F - CentralNic Ltd, GB-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1.centralnic.net, ns2.centralnic.net, ns3.centralnic.net, ns4.centralnic.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 4 IPv4 /24s and 4 IPv6 /48s.
  • ✓ 4 autonomous systems #11
    The nameservers are spread over: AS199330 (CENTRALNIC-ANYCAST-A - CentralNic Ltd, GB): 2 addresses; AS201303 (CentralNic-Anycast-F - CentralNic Ltd, GB): 2 addresses; AS201304 (CENTRALNIC-ANYCAST-E - CentralNic Ltd, GB): 2 addresses; AS60890 (CENTRALNIC-ANYCAST-B - CentralNic Ltd, GB): 2 addresses.
  • 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

info

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.centralnic.net 194.169.218.24NOERROR, 16 ms, authoritativenoyes / yesrefused-
ns1.centralnic.net 2001:67c:13cc::1:24NOERROR, 16 ms, authoritativenoyes / yesrefused-
ns2.centralnic.net 185.24.64.10NOERROR, 24 ms, authoritativenoyes / yesrefusedoff
ns2.centralnic.net 2a04:2b00:13cc::1:10NOERROR, 27 ms, authoritativenoyes / yesrefusedoff
ns3.centralnic.net 212.18.248.10NOERROR, 16 ms, authoritativenoyes / yesrefused-
ns3.centralnic.net 2a04:2b00:13ee::10NOERROR, 15 ms, authoritativenoyes / yesrefused-
ns4.centralnic.net 212.18.249.24NOERROR, 23 ms, authoritativenoyes / yesrefusedoff
ns4.centralnic.net 2a04:2b00:13ff::24NOERROR, 24 ms, authoritativenoyes / yesrefusedoff

Checks

  • ✓ All respond #14
    All 8 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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ns2.centralnic.net: "off"; ns4.centralnic.net: "off".
    #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 3000678529 · primary ns0.centralnic.net

Found

Primary (MNAME)
ns0.centralnic.net
Contact (RNAME)
hostmaster.centralnic.net
Serial
3000678529
Refresh / retry
900 s / 1800 s
Expire
6048000 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.centralnic.net (194.169.218.24)3000678529
ns1.centralnic.net (2001:67c:13cc::1:24)3000678529
ns2.centralnic.net (185.24.64.10)3000678529
ns2.centralnic.net (2a04:2b00:13cc::1:10)3000678529
ns3.centralnic.net (212.18.248.10)3000678529
ns3.centralnic.net (2a04:2b00:13ee::10)3000678529
ns4.centralnic.net (212.18.249.24)3000678529
ns4.centralnic.net (2a04:2b00:13ff::24)3000678529

Checks

  • ✓ Serial 3000678529 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    refresh 15m is outside 20m–1d; retry 30m should be shorter than refresh 15m. Current values: refresh 15m, retry 30m, expire 70d, negative TTL 1h.
    #23
  • i
    Hidden master
    The primary nameserver ns0.centralnic.net is not listed as a nameserver: a hidden master that only feeds the public secondaries. That is a common setup; make sure it is not reachable for zone transfers from outside.
    #24
  • ✓ Contact hostmaster@centralnic.net #25
    The SOA RNAME hostmaster.centralnic.net means hostmaster@centralnic.net.
  • ✓ Timestamp serial #26
    The serial 3000678529 is a Unix timestamp (2065-02-01 01:48 UTC).

DNSSEC

warn

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC3
NSEC3
0 iterations, 0-byte salt
Signatures valid until
31 October 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
30236RSASHA1-NSEC3-SHA1 (7)SHA256 6BFA57A56A6A71C5…NO
10879RSASHA1-NSEC3-SHA1 (7)SHA256 9B0E8FAAB64C2541…yes

DNSKEY in the zone

Key tagRoleAlgorithm
10879KSK (257)RSASHA1-NSEC3-SHA1 (7)
9257ZSK (256)RSASHA1-NSEC3-SHA1 (7)

Checks

  • ✓ Signed and validated #27
    The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
  • i
    Unused DS records
    These DS records match no key in the zone: key tag 30236 (SHA256). That is normal during a key rollover; otherwise remove them.
    #28
  • !
    Deprecated algorithm
    SHA-1 based algorithms are deprecated and rejected by some validators: RSASHA1-NSEC3-SHA1 (7). Roll over to ECDSAP256SHA256 (13).
    #29
  • ✓ Signatures valid until 2026-10-31 #30
    The earliest DNSKEY/SOA signature expires at 2026-10-31 03:23 UTC.
  • ✓ NSEC3 as recommended #31
    The zone uses NSEC3 with 0 iterations and no salt (RFC 9276).

Records

info

7 records at the apex

Found

Read from
194.169.218.24:53
TypeValueTTL
SOAns0.centralnic.net. hostmaster.centralnic.net. 3000678529 900 1800 6048000 36003600
NSns4.centralnic.net.3600
NSns3.centralnic.net.3600
NSns1.centralnic.net.3600
NSns2.centralnic.net.3600
MX0 .3600
TXT"v=spf1 -all"3600

Checks

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