sinopec.com

Checked 22 October 2026, 10:43 UTC · via 8.8.8.8
✗Problems found
22 passed 3 warnings 2 failed 4 info

Registration

info

.com generic · Beijing Guoxu Network Technology Co., Ltd. · expires 2029-03-18

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Beijing Guoxu Network Technology Co., Ltd.
Registered
17 March 1997
Last changed
19 October 2026
Expires
18 March 2029
Status
client delete prohibited, client transfer prohibited
Registry nameservers
ns1.sinopec.com, ns2.sinopec.com, ns3.sinopec.com, ns4.sinopec.com, ns5.sinopec.com, ns6.sinopec.com, ns7.sinopec.com, ns8.sinopec.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 2029-03-18 #3
    The registration is valid until 2029-03-18 (877 days).
  • ✓ Transfer locked #4
    Registry status: client delete prohibited, client transfer prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

ns1.sinopec.com, ns2.sinopec.com, ns3.sinopec.com, ns4.sinopec.com, ns5.sinopec.com, ns6.sinopec.com, ns7.sinopec.com, ns8.sinopec.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.sinopec.com, ns2.sinopec.com, ns3.sinopec.com, ns4.sinopec.com, ns5.sinopec.com, ns6.sinopec.com, ns7.sinopec.com, ns8.sinopec.com
NS in the zone
ns1.sinopec.com, ns2.sinopec.com, ns3.sinopec.com, ns4.sinopec.com, ns5.sinopec.com, ns6.sinopec.com, ns7.sinopec.com, ns8.sinopec.com
NameserverAddressesNetwork (AS)Glue
ns1.sinopec.com114.246.38.132AS4808 CHINA169-BJ - China Unicom Beijing Province Network, CN114.246.38.132
ns2.sinopec.com114.246.38.133AS4808 CHINA169-BJ - China Unicom Beijing Province Network, CN114.246.38.133
ns3.sinopec.com219.142.191.158AS4847 CNIX-AP - China Networks Inter-Exchange, CN219.142.191.158
ns4.sinopec.com219.142.191.134AS4847 CNIX-AP - China Networks Inter-Exchange, CN219.142.191.134
ns5.sinopec.com110.16.192.111AS4837 CHINA169-Backbone - CHINA UNICOM China169 Backbone, CN110.16.192.111
ns6.sinopec.com111.56.240.132AS9808 CHINAMOBILE-CN - China Mobile Communications Group Co., Ltd., CN111.56.240.132
ns7.sinopec.com1.180.19.154AS4134 CHINANET-BACKBONE - No.31,Jin-rong Street, CN1.180.19.154
ns8.sinopec.com110.16.192.114AS4837 CHINA169-Backbone - CHINA UNICOM China169 Backbone, CN110.16.192.114

Checks

  • ✓ 8 nameservers #6
    Delegated to ns1.sinopec.com, ns2.sinopec.com, ns3.sinopec.com, ns4.sinopec.com, ns5.sinopec.com, ns6.sinopec.com, ns7.sinopec.com, ns8.sinopec.com.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: ns1.sinopec.com, ns2.sinopec.com, ns3.sinopec.com, ns4.sinopec.com, ns5.sinopec.com, ns6.sinopec.com, ns7.sinopec.com, ns8.sinopec.com.
  • ✓ 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 5 IPv4 /24s and 0 IPv6 /48s.
  • ✓ 5 autonomous systems #11
    The nameservers are spread over: AS4134 (CHINANET-BACKBONE - No.31,Jin-rong Street, CN): 1 address; AS4808 (CHINA169-BJ - China Unicom Beijing Province Network, CN): 2 addresses; AS4837 (CHINA169-Backbone - CHINA UNICOM China169 Backbone, CN): 2 addresses; AS4847 (CNIX-AP - China Networks Inter-Exchange, CN): 2 addresses; AS9808 (CHINAMOBILE-CN - China Mobile Communications Group Co., Ltd., CN): 1 address.
  • 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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

fail

6 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.sinopec.com 114.246.38.132NOERROR, 135 ms, authoritativenono / yesrefusednone
ns2.sinopec.com 114.246.38.133NOERROR, 184 ms, authoritativenono / yesrefusednone
ns3.sinopec.com 219.142.191.158NOERROR, 143 ms, authoritativenono / yesrefusednone
ns4.sinopec.com 219.142.191.134NOERROR, 136 ms, authoritativenono / yesrefusednone
ns5.sinopec.com 110.16.192.111no responsenono / no--
ns6.sinopec.com 111.56.240.132NOERROR, 224 ms, authoritativenoyes / yesrefusednone
ns7.sinopec.com 1.180.19.154NOERROR, 210 ms, authoritativenoyes / yesrefusednone
ns8.sinopec.com 110.16.192.114no responsenono / no--

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: ns5.sinopec.com (110.16.192.111): read udp 46.225.38.91:53140->110.16.192.111:53: i/o timeout; ns8.sinopec.com (110.16.192.114): read udp 46.225.38.91:38161->110.16.192.114: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: ns1.sinopec.com: "none"; ns2.sinopec.com: "none"; ns3.sinopec.com: "none"; ns4.sinopec.com: "none"; ns6.sinopec.com: "none"; ns7.sinopec.com: "none".
    #17
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✗
    No DNS over TCP
    DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns1.sinopec.com (114.246.38.132): dial tcp 114.246.38.132:53: i/o timeout; ns2.sinopec.com (114.246.38.133): dial tcp 114.246.38.133:53: i/o timeout; ns3.sinopec.com (219.142.191.158): dial tcp 219.142.191.158:53: i/o timeout; ns4.sinopec.com (219.142.191.134): dial tcp 219.142.191.134:53: i/o timeout.
    #19
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2026102209 · primary ns1.sinopec.com

Found

Primary (MNAME)
ns1.sinopec.com
Contact (RNAME)
admin.sinopec.com
Serial
2026102209
Refresh / retry
28800 s / 7200 s
Expire
2400000 s
Negative TTL
900 s

Serial per nameserver

NameserverSerial
ns1.sinopec.com (114.246.38.132)2026102209
ns2.sinopec.com (114.246.38.133)2026102209
ns3.sinopec.com (219.142.191.158)2026102209
ns4.sinopec.com (219.142.191.134)2026102209
ns6.sinopec.com (111.56.240.132)2026102209
ns7.sinopec.com (1.180.19.154)2026102209

Checks

  • ✓ Serial 2026102209 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 8h, retry 2h, expire 40000m, negative TTL 15m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.sinopec.com is one of the listed nameservers.
  • ✓ Contact admin@sinopec.com #25
    The SOA RNAME admin.sinopec.com means admin@sinopec.com.
  • ✓ Date-based serial #26
    The serial 2026102209 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

11 records at the apex

Found

Read from
114.246.38.132:53
TypeValueTTL
SOAns1.sinopec.com. admin.sinopec.com. 2026102209 28800 7200 2400000 90086400
NSns4.sinopec.com.300
NSns5.sinopec.com.300
NSns1.sinopec.com.300
NSns8.sinopec.com.300
NSns6.sinopec.com.300
NSns3.sinopec.com.300
NSns7.sinopec.com.300
NSns2.sinopec.com.300
MX4 mailmx5.sinopec.com.30
TXT"v=spf1 mx ip4:219.143.118.3 ip4:123.124.249.224 ip4:223.119.51.171 ip4:183.242.52.3 ip4:114.247.161.131 ip4:36.112.50.231 ip4:61.135.14.231 ip4:219.142.191.131 ip4:110.16.192.6 ip4:1.180.19.6 ip4:218.189.28.251 ip4:218.188.67.105 -all"600

Checks

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