pingan.com

Checked 22 October 2026, 10:14 UTC · via 8.8.8.8
✗Problems found
23 passed 2 warnings 1 failed 5 info

Registration

info

.com generic · Beijing Brandma International Networking Technology Ltd. · expires 2036-03-26

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Beijing Brandma International Networking Technology Ltd.
Registered
25 March 1997
Last changed
24 June 2026
Expires
26 March 2036
Status
client delete prohibited, client transfer prohibited, server delete prohibited, server transfer prohibited, server update prohibited
Registry nameservers
pans1.pa18.com, pans2.pa18.com, pans3.pa18.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 2036-03-26 #3
    The registration is valid until 2036-03-26 (3442 days).
  • ✓ Transfer locked #4
    Registry status: client delete prohibited, client transfer prohibited, server delete prohibited, server transfer prohibited, server update prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

pans1.pa18.com, pans2.pa18.com, pans3.pa18.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
pans1.pa18.com, pans2.pa18.com, pans3.pa18.com
NS in the zone
pans1.pa18.com, pans2.pa18.com, pans3.pa18.com
NameserverAddressesNetwork (AS)Glue
pans1.pa18.com124.196.57.222 202.69.19.167 2404:7180:a010:201::7 2404:7180:a000:100:0:1:0:7AS23848 PINGANCOM - Shenzhen Ping An Communication Technology Co.,Ltd, CN AS23848 PINGANCOM - Shenzhen Ping An Communication Technology Co.,Ltd, CN AS23848 PINGANCOM - Shenzhen Ping An Communication Technology Co.,Ltd, CN AS23848 PINGANCOM - Shenzhen Ping An Communication Technology Co.,Ltd, CN124.196.57.222 202.69.19.167 2404:7180:a000:100:0:1:0:7 2404:7180:a010:201::7
pans2.pa18.com124.196.57.248 202.69.19.168 2404:7180:a010:201::8 2404:7180:a000:100:0:1:0:8AS23848 PINGANCOM - Shenzhen Ping An Communication Technology Co.,Ltd, CN AS23848 PINGANCOM - Shenzhen Ping An Communication Technology Co.,Ltd, CN AS23848 PINGANCOM - Shenzhen Ping An Communication Technology Co.,Ltd, CN AS23848 PINGANCOM - Shenzhen Ping An Communication Technology Co.,Ltd, CN124.196.57.248 202.69.19.168 2404:7180:a000:100:0:1:0:8 2404:7180:a010:201::8
pans3.pa18.com202.69.19.169 124.196.57.249 2404:7180:a000:100:0:1:0:9 2404:7180:a010:201::9AS23848 PINGANCOM - Shenzhen Ping An Communication Technology Co.,Ltd, CN AS23848 PINGANCOM - Shenzhen Ping An Communication Technology Co.,Ltd, CN AS23848 PINGANCOM - Shenzhen Ping An Communication Technology Co.,Ltd, CN AS23848 PINGANCOM - Shenzhen Ping An Communication Technology Co.,Ltd, CN124.196.57.249 202.69.19.169 2404:7180:a000:100:0:1:0:9 2404:7180:a010:201::9

Checks

  • ✓ 3 nameservers #6
    Delegated to pans1.pa18.com, pans2.pa18.com, pans3.pa18.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 2 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS23848 (PINGANCOM - Shenzhen Ping An Communication Technology Co.,Ltd, CN): 12 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 .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

fail

10 of 12 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
pans1.pa18.com 124.196.57.222NOERROR, 207 ms, authoritativenoyes / yesrefusednone
pans1.pa18.com 202.69.19.167no responsenono / no--
pans1.pa18.com 2404:7180:a010:201::7NOERROR, 200 ms, authoritativenoyes / yesrefusednone
pans1.pa18.com 2404:7180:a000:100:0:1:0:7NOERROR, 191 ms, authoritativenoyes / yesrefusednone
pans2.pa18.com 124.196.57.248no responsenono / no--
pans2.pa18.com 202.69.19.168NOERROR, 213 ms, authoritativenoyes / yesrefusednone
pans2.pa18.com 2404:7180:a010:201::8NOERROR, 208 ms, authoritativenoyes / yesrefusednone
pans2.pa18.com 2404:7180:a000:100:0:1:0:8NOERROR, 198 ms, authoritativenoyes / yesrefusednone
pans3.pa18.com 202.69.19.169NOERROR, 205 ms, authoritativenoyes / yesrefusednone
pans3.pa18.com 124.196.57.249NOERROR, 166 ms, authoritativenoyes / yesrefusednone
pans3.pa18.com 2404:7180:a000:100:0:1:0:9NOERROR, 216 ms, authoritativenoyes / yesrefusednone
pans3.pa18.com 2404:7180:a010:201::9NOERROR, 220 ms, authoritativenoyes / yesrefusednone

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: pans1.pa18.com (202.69.19.167): read udp 46.225.38.91:40324->202.69.19.167:53: i/o timeout; pans2.pa18.com (124.196.57.248): read udp 46.225.38.91:46531->124.196.57.248: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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: pans1.pa18.com: "none"; pans2.pa18.com: "none"; pans3.pa18.com: "none".
    #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 2026102204 · primary pans1.pa18.com

Found

Primary (MNAME)
pans1.pa18.com
Contact (RNAME)
hostmaster.pans1.pa18.com
Serial
2026102204
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
pans1.pa18.com (124.196.57.222)2026102204
pans1.pa18.com (2404:7180:a010:201::7)2026102204
pans1.pa18.com (2404:7180:a000:100:0:1:0:7)2026102204
pans2.pa18.com (202.69.19.168)2026102204
pans2.pa18.com (2404:7180:a010:201::8)2026102204
pans2.pa18.com (2404:7180:a000:100:0:1:0:8)2026102204
pans3.pa18.com (202.69.19.169)2026102204
pans3.pa18.com (124.196.57.249)2026102204
pans3.pa18.com (2404:7180:a000:100:0:1:0:9)2026102204
pans3.pa18.com (2404:7180:a010:201::9)2026102204

Checks

  • ✓ Serial 2026102204 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver pans1.pa18.com is one of the listed nameservers.
  • ✓ Contact hostmaster@pans1.pa18.com #25
    The SOA RNAME hostmaster.pans1.pa18.com means hostmaster@pans1.pa18.com.
  • ✓ Date-based serial #26
    The serial 2026102204 follows the YYYYMMDDnn convention (2026-10-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

warn

8 records at the apex

Found

Read from
124.196.57.222:53
TypeValueTTL
SOApans1.pa18.com. hostmaster.pans1.pa18.com. 2026102204 10800 3600 604800 86400600
A183.62.123.6230
MX10 mx7.pingan.com.cn.600
MX10 mx5.pingan.com.cn.600
MX10 mx4.pingan.com.cn.600
MX10 mx8.pingan.com.cn.600
TXT"v=spf2.0/pra include:spf2.pingan.com.cn -all"60
TXT"v=spf1 include:spf.pingan.com.cn -all"60

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (30s). Low TTLs are useful just before a planned change.
    #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