rt.com

Checked 22 October 2026, 10:33 UTC · via 8.8.8.8
✗Problems found
23 passed 3 warnings 2 failed 3 info

Registration

info

.com generic · Regional Network Information Center, JSC dba RU-CENTER · expires 2027-09-22

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Regional Network Information Center, JSC dba RU-CENTER
Registered
23 September 1991
Last changed
21 September 2026
Expires
22 September 2027
Status
client transfer prohibited
Registry nameservers
ens-a.rttv.ru, ens-k.rttv.ru, ens-u.rttv.ru, ns1.rttv.ru, ns2.rttv.ru
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 2027-09-22 #3
    The registration is valid until 2027-09-22 (334 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

ens-a.rttv.ru, ens-k.rttv.ru, ens-u.rttv.ru, ns1.rttv.ru, ns2.rttv.ru

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ens-a.rttv.ru, ens-k.rttv.ru, ens-u.rttv.ru, ns1.rttv.ru, ns2.rttv.ru
NS in the zone
ens-a.rttv.ru, ens-k.rttv.ru, ens-u.rttv.ru, ns1.rttv.ru, ns2.rttv.ru
NameserverAddressesNetwork (AS)Glue
ens-a.rttv.ru95.163.176.17AS210644 AEZA-AS - AEZA GROUP LLC, RU-
ens-k.rttv.ru185.116.194.23AS202958 Hoster-ALM - LLP _Kompaniya Hoster.KZ_, KZ-
ens-u.rttv.ru31.44.6.191AS208951 AS-ITGLOBALCOM - ITGLOBAL.COM NL B.V., NL-
ns1.rttv.ru109.73.15.35AS50040 RUSSIA_TODAY - ANO TV NOVOSTI, RU-
ns2.rttv.ru185.79.236.245AS199599 CIREX - Telecom-Birzha, LLC, RU-

Checks

  • ✓ 5 nameservers #6
    Delegated to ens-a.rttv.ru, ens-k.rttv.ru, ens-u.rttv.ru, ns1.rttv.ru, ns2.rttv.ru.
  • ✓ 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 5 IPv4 /24s and 0 IPv6 /48s.
  • ✓ 5 autonomous systems #11
    The nameservers are spread over: AS199599 (CIREX - Telecom-Birzha, LLC, RU): 1 address; AS202958 (Hoster-ALM - LLP _Kompaniya Hoster.KZ_, KZ): 1 address; AS208951 (AS-ITGLOBALCOM - ITGLOBAL.COM NL B.V., NL): 1 address; AS210644 (AEZA-AS - AEZA GROUP LLC, RU): 1 address; AS50040 (RUSSIA_TODAY - ANO TV NOVOSTI, RU): 1 address.
  • i
    All nameserver names under .ru
    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

fail

4 of 5 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ens-a.rttv.ru 95.163.176.17NOERROR, 9 ms, authoritativenoyes / yesrefused-
ens-k.rttv.ru 185.116.194.23NOERROR, 88 ms, authoritativenoyes / yesrefused-
ens-u.rttv.ru 31.44.6.191no responsenono / no--
ns1.rttv.ru 109.73.15.35NOERROR, 41 ms, authoritativenono / yesrefused-
ns2.rttv.ru 185.79.236.245NOERROR, 45 ms, authoritativenoyes / yesrefused-

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: ens-u.rttv.ru (31.44.6.191): read udp 46.225.38.91:60148->31.44.6.191:53: i/o timeout.
    #14
  • ✓ 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: ns1.rttv.ru (109.73.15.35): dial tcp 109.73.15.35:53: i/o timeout.
    #19
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

warn

serial 2026100801 · primary ns1.rttv.ru

Found

Primary (MNAME)
ns1.rttv.ru
Contact (RNAME)
itdept.rttv.ru
Serial
2026100801
Refresh / retry
300 s / 300 s
Expire
604800 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ens-a.rttv.ru (95.163.176.17)2026100801
ens-k.rttv.ru (185.116.194.23)2026100801
ns1.rttv.ru (109.73.15.35)2026100801
ns2.rttv.ru (185.79.236.245)2026100801

Checks

  • ✓ Serial 2026100801 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    refresh 5m is outside 20m–1d; retry 5m should be shorter than refresh 5m. Current values: refresh 5m, retry 5m, expire 7d, negative TTL 5m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.rttv.ru is one of the listed nameservers.
  • ✓ Contact itdept@rttv.ru #25
    The SOA RNAME itdept.rttv.ru means itdept@rttv.ru.
  • ✓ Date-based serial #26
    The serial 2026100801 follows the YYYYMMDDnn convention (2026-10-08).

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

12 records at the apex

Found

Read from
95.163.176.17:53
TypeValueTTL
SOAns1.rttv.ru. itdept.rttv.ru. 2026100801 300 300 604800 300300
NSens-k.rttv.ru.300
NSns1.rttv.ru.300
NSens-a.rttv.ru.300
NSens-u.rttv.ru.300
NSns2.rttv.ru.300
A91.215.41.4300
MX10 mx.yandex.net.300
TXT"google-site-verification=WQjoV9sBpeuI20b2jwEoXYRcxCSUnexj6gCdSNdN9rs"300
TXT"yandex-verification: 952c89f52932efa3"300
TXT"v=spf1 redirect=_spf.yandex.net"300
TXT"1593f397-3ea1-493c-b394-cfa950c7e364"300

Checks

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