itar-tass.com

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

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

4 of 4 addresses answer authoritatively

Found

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.
• !

  Software version disclosed

  These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns4-l2.nic.ru: "Knot DNS 3.3.4"; 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.

serial 2014043457 · primary ns1.tass.ru

Found

Primary (MNAME)

ns1.tass.ru

Contact (RNAME)

hostmaster.tass.ru

Serial

2014043457

Refresh / retry

1200 s / 600 s

Expire

604800 s

Negative TTL

120 s

Serial per nameserver

Checks

• ✓ Serial 2014043457 everywhere #22

  All nameservers serve the same version of the zone.
• !

  Unusual SOA timers

  negative caching TTL (minimum) 2m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 20m, retry 10m, expire 7d, 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.
• ✓ Timestamp serial #26

  The serial 2014043457 is a Unix timestamp (2033-10-27 16:30 UTC).

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

10 records at the apex

Found

Read from

194.28.239.11:53

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.
• ✓ 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