tass.com

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

Registration

info

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

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Regional Network Information Center, JSC dba RU-CENTER
Registered
17 September 1993
Last changed
15 September 2026
Expires
16 September 2027
Status
client transfer prohibited
Registry nameservers
ns1.tass.ru, ns2.tass.ru, ns4-l2.nic.ru, ns8-l2.nic.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-16 #3
    The registration is valid until 2027-09-16 (328 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

ns1.tass.ru, ns2.tass.ru, ns4-l2.nic.ru, ns8-l2.nic.ru

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.tass.ru, ns2.tass.ru, ns4-l2.nic.ru, ns8-l2.nic.ru
NS in the zone
ns1.tass.ru, ns2.tass.ru, ns4-l2.nic.ru, ns8-l2.nic.ru
NameserverAddressesNetwork (AS)Glue
ns1.tass.ru194.28.239.11AS51186 ITAR-TASS-AS - ITAR-TASS State Enterprise, RU-
ns2.tass.ru194.28.239.12AS51186 ITAR-TASS-AS - ITAR-TASS State Enterprise, RU-
ns4-l2.nic.ru91.217.20.20AS48287 RU-CENTER - JSC _RU-CENTER_, RU-
ns8-l2.nic.ru91.217.21.20AS39494 RU-CENTER-AS - JSC _RU-CENTER_, RU-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1.tass.ru, ns2.tass.ru, ns4-l2.nic.ru, ns8-l2.nic.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 3 IPv4 /24s and 0 IPv6 /48s.
  • ✓ 3 autonomous systems #11
    The nameservers are spread over: AS39494 (RU-CENTER-AS - JSC _RU-CENTER_, RU): 1 address; AS48287 (RU-CENTER - JSC _RU-CENTER_, RU): 1 address; AS51186 (ITAR-TASS-AS - ITAR-TASS State Enterprise, RU): 2 addresses.
  • 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

3 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.tass.ru 194.28.239.11NOERROR, 46 ms, authoritativenoyes / yesrefused-
ns2.tass.ru 194.28.239.12NOERROR, 48 ms, authoritativenoyes / yesrefused-
ns4-l2.nic.ru 91.217.20.20no responsenono / no--
ns8-l2.nic.ru 91.217.21.20NOERROR, 53 ms, authoritativenoyes / yesrefusedKnot DNS 3.3.4

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: ns4-l2.nic.ru (91.217.20.20): read udp 46.225.38.91:48141->91.217.20.20: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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns8-l2.nic.ru: "Knot DNS 3.3.4". 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 321 · primary ns1.tass.ru

Found

Primary (MNAME)
ns1.tass.ru
Contact (RNAME)
hostmaster.tass.ru
Serial
321
Refresh / retry
900 s / 600 s
Expire
86400 s
Negative TTL
120 s

Serial per nameserver

NameserverSerial
ns1.tass.ru (194.28.239.11)321
ns2.tass.ru (194.28.239.12)321
ns8-l2.nic.ru (91.217.21.20)321

Checks

  • ✓ Serial 321 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    refresh 15m is outside 20m–1d; expire 1d is shorter than 7d; secondaries stop answering too soon when the primary is down; negative caching TTL (minimum) 2m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 15m, retry 10m, expire 1d, negative TTL 2m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.tass.ru is one of the listed nameservers.
  • ✓ Contact hostmaster@tass.ru #25
    The SOA RNAME hostmaster.tass.ru means hostmaster@tass.ru.
  • ✓ Counter serial #26
    The serial 321 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

14 records at the apex

Found

Read from
194.28.239.11:53
TypeValueTTL
SOAns1.tass.ru. hostmaster.tass.ru. 321 900 600 86400 120120
NSns8-l2.nic.ru.120
NSns4-l2.nic.ru.120
NSns1.tass.ru.120
NSns2.tass.ru.120
A91.221.164.6120
MX50 mx-ksmg04.tass.ru.120
MX50 mx-ksmg03.tass.ru.120
TXT"_globalsign-domain-verification=c5kbYNfYjqnYCgQnceV9nIU-IuTDNO8zD6NzA84qUV"120
TXT"v=spf1 ip4:194.28.236.0/24 -all"120
TXT"rm_verify=84c2b9132b"120
TXT"yandex-verification: 44af600ae0bb708d"120
TXT"google-site-verification=XDNSrs4P356ho8hDOp7xsqzZmBzOEC5rQWDs0G4A6cg"120
TXT"rm_verify=84c2b9132b."120

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (2m), MX (2m), NS (2m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 2m; 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