yandex.com

Checked 22 October 2026, 11:36 UTC · via 8.8.8.8
!Passed with warnings
23 passed 1 warning 0 failed 7 info

Registration

info

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

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Regional Network Information Center, JSC dba RU-CENTER
Registered
24 September 1998
Last changed
22 September 2026
Expires
23 September 2027
Status
client transfer prohibited
Registry nameservers
ns1.yandex.net, ns2.yandex.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.
    #1
  • ✓ TLD delegated and signed #2
    .com is delegated in the root zone and DNSSEC-signed.
  • ✓ Expires on 2027-09-23 #3
    The registration is valid until 2027-09-23 (335 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

info

ns1.yandex.net, ns2.yandex.net

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.yandex.net, ns2.yandex.net
NS in the zone
ns1.yandex.net, ns2.yandex.net
NameserverAddressesNetwork (AS)Glue
ns1.yandex.net213.180.193.1 2a02:6b8::1AS13238 YANDEX - YANDEX LLC, RU AS13238 YANDEX - YANDEX LLC, RU-
ns2.yandex.net93.158.134.1 2a02:6b8:0:1::1AS13238 YANDEX - YANDEX LLC, RU AS13238 YANDEX - YANDEX LLC, RU-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.yandex.net, ns2.yandex.net.
    #6
  • ✓ 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.
  • i
    One address family in one network
    all IPv6 addresses are in 2a02:6b8::/48, while the other address family is spread over several networks.
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS13238 (YANDEX - YANDEX LLC, RU): 4 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • 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

pass

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.yandex.net 213.180.193.1NOERROR, 44 ms, authoritativenoyes / yesrefused-
ns1.yandex.net 2a02:6b8::1NOERROR, 44 ms, authoritativenoyes / yesrefused-
ns2.yandex.net 93.158.134.1NOERROR, 39 ms, authoritativenoyes / yesrefused-
ns2.yandex.net 2a02:6b8:0:1::1NOERROR, 36 ms, authoritativenoyes / yesrefused-

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

info

serial 2023042240 · primary ns1.yandex.ru

Found

Primary (MNAME)
ns1.yandex.ru
Contact (RNAME)
sysadmin.yandex.ru
Serial
2023042240
Refresh / retry
3600 s / 900 s
Expire
2592000 s
Negative TTL
900 s

Serial per nameserver

NameserverSerial
ns1.yandex.net (213.180.193.1)2023042240
ns1.yandex.net (2a02:6b8::1)2023042240
ns2.yandex.net (93.158.134.1)2023042240
ns2.yandex.net (2a02:6b8:0:1::1)2023042240

Checks

  • ✓ Serial 2023042240 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 15m, expire 30d, negative TTL 15m.
  • i
    Hidden master
    The primary nameserver ns1.yandex.ru 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 sysadmin@yandex.ru #25
    The SOA RNAME sysadmin.yandex.ru means sysadmin@yandex.ru.
  • ✓ Date-based serial #26
    The serial 2023042240 follows the YYYYMMDDnn convention (2023-04-22).

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

16 records at the apex

Found

Read from
213.180.193.1:53
TypeValueTTL
SOAns1.yandex.ru. sysadmin.yandex.ru. 2023042240 3600 900 2592000 9003600
NSns2.yandex.net.172800
NSns1.yandex.net.172800
A77.88.55.88600
A77.88.44.55600
A5.255.255.77600
AAAA2a02:6b8:a::a1200
MX10 mx.yandex.ru.1200
TXT"facebook-domain-verification=625igbkehyfptcek6nh1hz7q4s3h4a"1200
TXT"facebook-domain-verification=gy3xj2e9mxu0vtcdgqcznoaxoaiv63"1200
TXT"google-site-verification=FVk3gum7zZLdkqi96ypScROFMew0wMetq1Gpu4rkzPI"1200
TXT"_globalsign-domain-verification=LUbMcUb0Zdviv4wd-A5JeHEzy5xZYZSWQQ0cxuo80l"1200
TXT"v=spf1 redirect=_spf.yandex.ru"1200
TXT"5849d1f0fc8a9e73d82dfed9f2c33931"1200
CAA0 issuewild "globalsign.com"3600
CAA0 issue "globalsign.com"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 10m, AAAA 20m, MX 20m, NS 2d.
  • ✓ 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
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: globalsign.com.