pantip.com

Checked 22 October 2026, 10:11 UTC · via 8.8.8.8
!Passed with warnings
25 passed 1 warning 0 failed 5 info

Registration

info

.com generic · eNom, LLC · expires 2031-10-06

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
eNom, LLC
Registered
7 October 1996
Last changed
8 January 2026
Expires
6 October 2031
Status
client transfer prohibited
Registry nameservers
ns1.byteark.com, ns2.byteark.com, ns3.byteark.com
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 2031-10-06 #3
    The registration is valid until 2031-10-06 (1809 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.byteark.com, ns2.byteark.com, ns3.byteark.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.byteark.com, ns2.byteark.com, ns3.byteark.com
NS in the zone
ns1.byteark.com, ns2.byteark.com, ns3.byteark.com
NameserverAddressesNetwork (AS)Glue
ns1.byteark.com103.253.135.151 2401:5700:100:509::151AS131447 POP-IDC-TH - POPIDC powered by CSLoxinfo, TH AS131447 POP-IDC-TH - POPIDC powered by CSLoxinfo, TH103.253.135.151 2401:5700:100:509::151
ns2.byteark.com103.135.111.2 2400:c540:53::53AS59238 INOX-TH - Innovative Extremist Co., Ltd., TH AS59238 INOX-TH - Innovative Extremist Co., Ltd., TH103.135.111.2 2400:c540:53::53
ns3.byteark.com103.135.111.3 2001:19f0:6001:44ef:5400:1ff:feb6:ed4cAS59238 INOX-TH - Innovative Extremist Co., Ltd., TH AS20473 AS-VULTR - The Constant Company, LLC, US103.135.111.3 2001:19f0:6001:44ef:5400:1ff:feb6:ed4c

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.byteark.com, ns2.byteark.com, ns3.byteark.com.
  • ✓ 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 2 IPv4 /24s and 3 IPv6 /48s.
  • ✓ 3 autonomous systems #11
    The nameservers are spread over: AS131447 (POP-IDC-TH - POPIDC powered by CSLoxinfo, TH): 2 addresses; AS20473 (AS-VULTR - The Constant Company, LLC, US): 1 address; AS59238 (INOX-TH - Innovative Extremist Co., Ltd., TH): 3 addresses.
  • i
    All nameserver names under .com
    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

info

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.byteark.com 103.253.135.151NOERROR, 201 ms, authoritativenoyes / yesrefusedgdnsd/3
ns1.byteark.com 2401:5700:100:509::151NOERROR, 207 ms, authoritativenoyes / yesrefusedgdnsd/3
ns2.byteark.com 103.135.111.2NOERROR, 12 ms, authoritativenoyes / yesrefusedgdnsd/3
ns2.byteark.com 2400:c540:53::53NOERROR, 12 ms, authoritativenoyes / yesrefusedgdnsd/3
ns3.byteark.com 103.135.111.3NOERROR, 12 ms, authoritativenoyes / yesrefusedgdnsd/3
ns3.byteark.com 2001:19f0:6001:44ef:5400:1ff:feb6:ed4cNOERROR, 159 ms, authoritativenoyes / yesrefusedgdnsd/3

Checks

  • ✓ All respond #14
    All 6 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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ns1.byteark.com: "gdnsd/3"; ns2.byteark.com: "gdnsd/3"; ns3.byteark.com: "gdnsd/3".
    #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 2026090200 · primary ns1.byteark.com

Found

Primary (MNAME)
ns1.byteark.com
Contact (RNAME)
hostmaster.byteark.com
Serial
2026090200
Refresh / retry
3600 s / 900 s
Expire
1814400 s
Negative TTL
7200 s

Serial per nameserver

NameserverSerial
ns1.byteark.com (103.253.135.151)2026090200
ns1.byteark.com (2401:5700:100:509::151)2026090200
ns2.byteark.com (103.135.111.2)2026090200
ns2.byteark.com (2400:c540:53::53)2026090200
ns3.byteark.com (103.135.111.3)2026090200
ns3.byteark.com (2001:19f0:6001:44ef:5400:1ff:feb6:ed4c)2026090200

Checks

  • ✓ Serial 2026090200 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 15m, expire 21d, negative TTL 2h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.byteark.com is one of the listed nameservers.
  • ✓ Contact hostmaster@byteark.com #25
    The SOA RNAME hostmaster.byteark.com means hostmaster@byteark.com.
  • ✓ Date-based serial #26
    The serial 2026090200 follows the YYYYMMDDnn convention (2026-09-02).

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

13 records at the apex

Found

Read from
103.253.135.151:53
TypeValueTTL
SOAns1.byteark.com. hostmaster.byteark.com. 2026090200 3600 900 1814400 72003600
NSns1.byteark.com.86400
NSns2.byteark.com.86400
NSns3.byteark.com.86400
A15.235.165.13300
A15.235.165.183300
AAAA2402:1f00:8001:18b7::300
AAAA2402:1f00:8001:180d::300
MX10 mail.pantip.com.86400
TXT"v=spf1 a mx a:smtp1.pantip.com a:mail2.pantip.com ip4:203.151.13.131 ip4:203.151.13.132 ip4:203.151.13.155 ip4:203.151.13.200 ip4:103.208.26.143 -all"3600
TXT"google-site-verification=HCwrCnffdsFPRYgMr0DFfYyWg0ia1WcJiarzgg_ttjw"3600
TXT"google-site-verification=iFHSU6lmDu3A1HiKXdroVP0Qvvxk1MG5P6O_yUH9TkQ"3600
TXT"google-site-verification=4LiEn3mbrvxDR8wu7pjugrs-B9LGnhbSAAb424WWk-w"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, AAAA 5m, MX 1d, NS 1d. The NS TTL at the parent is 2d and in the zone 1d; resolvers may use either.
  • ✓ 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
  • 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