myseldon.com

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

Registration

warn

.com generic · Regional Network Information Center, JSC dba RU-CENTER · expires 2026-11-06

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Regional Network Information Center, JSC dba RU-CENTER
Registered
6 November 2015
Last changed
26 April 2026
Expires
6 November 2026
Status
client transfer prohibited
Registry nameservers
ns3-l2.nic.ru, ns4-cloud.nic.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 in 15 days
    The registration expires on 2026-11-06. Make sure it is renewed.
    #3
  • ✓ 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

ns3-l2.nic.ru, ns4-cloud.nic.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
ns3-l2.nic.ru, ns4-cloud.nic.ru, ns4-l2.nic.ru, ns8-l2.nic.ru
NS in the zone
ns3-l2.nic.ru, ns4-cloud.nic.ru, ns4-l2.nic.ru, ns8-l2.nic.ru
NameserverAddressesNetwork (AS)Glue
ns3-l2.nic.ru193.232.146.1AS48287 RU-CENTER - JSC _RU-CENTER_, RU-
ns4-cloud.nic.ru89.104.93.30 89.104.93.34 89.104.93.33 89.104.95.30 89.104.95.34 89.104.95.33AS43489 ANYCAST-AS - JSC _RU-CENTER_, RU AS43489 ANYCAST-AS - JSC _RU-CENTER_, RU AS43489 ANYCAST-AS - JSC _RU-CENTER_, RU AS43489 ANYCAST-AS - JSC _RU-CENTER_, RU AS43489 ANYCAST-AS - JSC _RU-CENTER_, RU AS43489 ANYCAST-AS - JSC _RU-CENTER_, 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 ns3-l2.nic.ru, ns4-cloud.nic.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 5 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; AS43489 (ANYCAST-AS - JSC _RU-CENTER_, RU): 6 addresses; AS48287 (RU-CENTER - JSC _RU-CENTER_, 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

7 of 9 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns3-l2.nic.ru 193.232.146.1no responsenono / no--
ns4-cloud.nic.ru 89.104.93.30NOERROR, 49 ms, authoritativenoyes / yesrefusedREGRU-DNS 0.4.2
ns4-cloud.nic.ru 89.104.93.34NOERROR, 49 ms, authoritativenoyes / yesrefusedREGRU-DNS 0.4.2
ns4-cloud.nic.ru 89.104.93.33NOERROR, 49 ms, authoritativenoyes / yesrefusedREGRU-DNS 0.4.2
ns4-cloud.nic.ru 89.104.95.30NOERROR, 53 ms, authoritativenoyes / yesrefusedREGRU-DNS 0.4.2
ns4-cloud.nic.ru 89.104.95.34NOERROR, 50 ms, authoritativenoyes / yesrefusedREGRU-DNS 0.4.2
ns4-cloud.nic.ru 89.104.95.33NOERROR, 50 ms, authoritativenoyes / yesrefusedREGRU-DNS 0.4.2
ns4-l2.nic.ru 91.217.20.20no responsenono / no--
ns8-l2.nic.ru 91.217.21.20NOERROR, 56 ms, authoritativenoyes / yesrefusedKnot DNS 3.3.4

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: ns3-l2.nic.ru (193.232.146.1): read udp 46.225.38.91:52579->193.232.146.1:53: i/o timeout; ns4-l2.nic.ru (91.217.20.20): read udp 46.225.38.91:44370->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: ns4-cloud.nic.ru: "REGRU-DNS 0.4.2"; 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 2016022175 · primary ns3-l2.nic.ru

Found

Primary (MNAME)
ns3-l2.nic.ru
Contact (RNAME)
dns.nic.ru
Serial
2016022175
Refresh / retry
1440 s / 3600 s
Expire
2592000 s
Negative TTL
600 s

Serial per nameserver

NameserverSerial
ns4-cloud.nic.ru (89.104.93.30)2016022175
ns4-cloud.nic.ru (89.104.93.34)2016022175
ns4-cloud.nic.ru (89.104.93.33)2016022175
ns4-cloud.nic.ru (89.104.95.30)2016022175
ns4-cloud.nic.ru (89.104.95.34)2016022175
ns4-cloud.nic.ru (89.104.95.33)2016022175
ns8-l2.nic.ru (91.217.21.20)2016022175

Checks

  • ✓ Serial 2016022175 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    retry 1h should be shorter than refresh 24m. Current values: refresh 24m, retry 1h, expire 30d, negative TTL 10m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns3-l2.nic.ru is one of the listed nameservers.
  • ✓ Contact dns@nic.ru #25
    The SOA RNAME dns.nic.ru means dns@nic.ru.
  • ✓ Date-based serial #26
    The serial 2016022175 follows the YYYYMMDDnn convention (2016-02-21).

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

10 records at the apex

Found

Read from
89.104.93.30:53
TypeValueTTL
SOAns3-l2.nic.ru. dns.nic.ru. 2016022175 1440 3600 2592000 6003600
NSns3-l2.nic.ru.3600
NSns4-l2.nic.ru.3600
NSns8-l2.nic.ru.3600
NSns4-cloud.nic.ru.3600
A185.179.199.71600
MX10 relay.myseldon.com.600
TXT"yandex-verification: 276bc16a68d03f00"600
TXT"google-site-verification=gAV6UkGyxCfCJwknvHQpaN_-Y5A4Eje80Nz-Ww6brHA"600
TXT"v=spf1 +a +mx ip4:185.179.199.2/32 ip4:185.179.199.44/32 ip4:185.179.199.32/32 include:spf.sendsay.ru ~all"600

Checks

  • ✓ TTLs within range #32
    TTLs: A 10m, MX 10m, 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