threatpost.com

Checked 22 October 2026, 11:04 UTC · via 8.8.8.8
!Passed with warnings
23 passed 2 warnings 0 failed 6 info

Registration

info

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

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Regional Network Information Center, JSC dba RU-CENTER
Registered
23 December 2008
Last changed
29 July 2024
Expires
23 December 2026
Status
client transfer prohibited
Registry nameservers
ns1.yandexcloud.net, ns2.yandexcloud.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 2026-12-23 #3
    The registration is valid until 2026-12-23 (62 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.yandexcloud.net, ns2.yandexcloud.net

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.yandexcloud.net, ns2.yandexcloud.net
NS in the zone
ns1.yandexcloud.net, ns2.yandexcloud.net
NameserverAddressesNetwork (AS)Glue
ns1.yandexcloud.net84.201.185.208 2a0d:d6c1:0:1a::1b4AS200350 YandexCloud - Yandex.Cloud LLC, RU AS200350 YandexCloud - Yandex.Cloud LLC, RU-
ns2.yandexcloud.net84.201.189.229 2a0d:d6c1:0:1a::2c9AS200350 YandexCloud - Yandex.Cloud LLC, RU AS200350 YandexCloud - Yandex.Cloud LLC, RU-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.yandexcloud.net, ns2.yandexcloud.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 2a0d:d6c1::/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 (AS200350 (YandexCloud - Yandex.Cloud 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.yandexcloud.net 84.201.185.208NOERROR, 42 ms, authoritativenoyes / yesrefused-
ns1.yandexcloud.net 2a0d:d6c1:0:1a::1b4NOERROR, 55 ms, authoritativenoyes / yesrefused-
ns2.yandexcloud.net 84.201.189.229NOERROR, 40 ms, authoritativenoyes / yesrefused-
ns2.yandexcloud.net 2a0d:d6c1:0:1a::2c9NOERROR, 51 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

pass

serial 1 · primary ns1.yandexcloud.net

Found

Primary (MNAME)
ns1.yandexcloud.net
Contact (RNAME)
mx.cloud.yandex.net
Serial
1
Refresh / retry
10800 s / 900 s
Expire
604800 s
Negative TTL
900 s

Serial per nameserver

NameserverSerial
ns1.yandexcloud.net (84.201.185.208)1
ns1.yandexcloud.net (2a0d:d6c1:0:1a::1b4)1
ns2.yandexcloud.net (84.201.189.229)1
ns2.yandexcloud.net (2a0d:d6c1:0:1a::2c9)1

Checks

  • ✓ Serial 1 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 15m, expire 7d, negative TTL 15m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.yandexcloud.net is one of the listed nameservers.
  • ✓ Contact mx@cloud.yandex.net #25
    The SOA RNAME mx.cloud.yandex.net means mx@cloud.yandex.net.
  • ✓ Counter serial #26
    The serial 1 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

13 records at the apex

Found

Read from
84.201.185.208:53
TypeValueTTL
SOAns1.yandexcloud.net. mx.cloud.yandex.net. 1 10800 900 604800 9003600
NSns1.yandexcloud.net.3600
NSns2.yandexcloud.net.3600
A82.202.190.24142
MX0 threatpost-com.mail.protection.outlook.com.3600
TXT"yandex-verification: d2cfa297d6302d69"3600
TXT"google-site-verification=IAC53QOVd-CRvhQSmvtMwg2rfhe3Ku8AcQW-_TUue5U"3600
TXT"vwy3przbhtm2gg0ybwdcs5j2lx3cy1tv"3600
TXT"y7ksf87msb7d4tbrkncvg7c1v09s5mqq"3600
TXT"mailru-verification: 37d00c741a9b052a"3600
TXT"v=spf1 include:spf.protection.outlook.com -all,3600"3600
TXT"MS=ms46391769"3600
TXT"_txtgz6goyzdtxawkcq5is98p30s2z88"3600

Checks

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