tok2.com

Checked 22 October 2026, 11:10 UTC · via 8.8.8.8
✗Problems found
20 passed 4 warnings 1 failed 6 info

Registration

fail

.com generic · Ascio Technologies, Inc. Danmark - Filial af Ascio technologies, Inc. USA · expires 2026-10-29

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Ascio Technologies, Inc. Danmark - Filial af Ascio technologies, Inc. USA
Registered
29 October 1999
Last changed
30 October 2025
Expires
29 October 2026
Status
active
Registry nameservers
dns1.prego.jp, dns2.prego.jp
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 6 days
    The registration expires on 2026-10-29. Renew it now or enable auto-renewal.
    #3
  • i
    No transfer lock
    The domain has no transfer lock (status: active). A registrar lock protects against unauthorized transfers.
    #4
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

dns1.prego.jp, dns2.prego.jp

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
dns1.prego.jp, dns2.prego.jp
NS in the zone
dns1.prego.jp, dns2.prego.jp
NameserverAddressesNetwork (AS)Glue
dns1.prego.jp210.198.29.104AS7514 MEX - Computer Engineering & Consulting, Ltd., JP-
dns2.prego.jp210.198.29.104AS7514 MEX - Computer Engineering & Consulting, Ltd., JP-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: dns1.prego.jp, dns2.prego.jp.
    #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.
  • !
    Nameservers in one network
    all IPv4 addresses are in 210.198.29.0/24. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS7514 (MEX - Computer Engineering & Consulting, Ltd., JP): 2 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 .jp
    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

warn

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns1.prego.jp 210.198.29.104NOERROR, 242 ms, authoritativenoyes / yesrefused9.8.2rc1-RedHat-9.8.2-0.30.rc1.el6_6.2
dns2.prego.jp 210.198.29.104NOERROR, 239 ms, authoritativenoyes / yesrefused9.8.2rc1-RedHat-9.8.2-0.30.rc1.el6_6.2

Checks

  • ✓ All respond #14
    All 2 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: dns1.prego.jp: "9.8.2rc1-RedHat-9.8.2-0.30.rc1.el6_6.2"; dns2.prego.jp: "9.8.2rc1-RedHat-9.8.2-0.30.rc1.el6_6.2". 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

pass

serial 2021053001 · primary dns1.prego.jp

Found

Primary (MNAME)
dns1.prego.jp
Contact (RNAME)
root.dns1.prego.jp
Serial
2021053001
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
360 s

Serial per nameserver

NameserverSerial
dns1.prego.jp (210.198.29.104)2021053001
dns2.prego.jp (210.198.29.104)2021053001

Checks

  • ✓ Serial 2021053001 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 6m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver dns1.prego.jp is one of the listed nameservers.
  • ✓ Contact root@dns1.prego.jp #25
    The SOA RNAME root.dns1.prego.jp means root@dns1.prego.jp.
  • ✓ Date-based serial #26
    The serial 2021053001 follows the YYYYMMDDnn convention (2021-05-30).

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

6 records at the apex

Found

Read from
210.198.29.104:53
TypeValueTTL
SOAdns1.prego.jp. root.dns1.prego.jp. 2021053001 10800 3600 604800 3603600
NSdns1.prego.jp.3600
NSdns2.prego.jp.3600
A157.7.189.2203600
MX10 mx01.lolipop.jp.3600
TXT"v=spf1 ip4:118.238.21.0/24 ~all"3600

Checks

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