doctorchain.com - robtex.com

doctorchain.com

DNSSEC⚠️ Not signed
NSns1.judns.com ⚠️ Not in zone NS records
A162.159.27.251Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
NSns1.julydns.com ⚠️ Not in parent delegation
A162.159.48.223Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US
NSns2.judns.com ⚠️ Not in zone NS records
A162.159.27.251Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
NSns2.julydns.com ⚠️ Not in parent delegation
A162.159.48.223Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US

com

DNSSEC🔒 Signed (DS record present)
NSa.gtld-servers.net ⭐
NSb.gtld-servers.net
NSc.gtld-servers.net
NSd.gtld-servers.net
NSe.gtld-servers.net
NSf.gtld-servers.net
NSg.gtld-servers.net
NSh.gtld-servers.net
NSi.gtld-servers.net
NSj.gtld-servers.net
NSk.gtld-servers.net
NSl.gtld-servers.net
NSm.gtld-servers.net
SOAa.gtld-servers.netnstld@verisign-grs.com serial=1785917554

Same first word

doctorchain.com

Similar names

doctorchina.org
doctorchina.com
chinadoctor.com.tw
doctorchina.net
doctorchina.co.uk
dantrocchio.com
chinadoctor.de
doctorchina.ru
chinadoctor.org
chinadoctor.com
doctornicha.com
doctorchina.biz

DNS History

21 records (4 active, 17 former)

20162017201820192020202120222023202420252026NSns1.judns.comns1.julydns.comns2.judns.comns2.julydns.comdns1.registrar-servers.comdns1.registrar-servers.com,dns10.hichina.comdns2.registrar-servers.comdns3.registrar-servers.comdns4.registrar-servers.comdns5.registrar-servers.comdns9.hichina.comexpire01.dnspod.netexpire02.dnspod.netMXeforward1.registrar-servers.comeforward2.registrar-servers.comeforward3.registrar-servers.comeforward4.registrar-servers.comeforward5.registrar-servers.comA192.64.119.243CNAMEdomainexpired.domain-expired.com
○NSdns1.registrar-servers.com2015-11-04 → 2016-08-12 · 4 obs
● 2015-11-04 18:02:00
● 2016-08-12 00:36:24
○ 2017-03-25 17:25:14
○ 2026-08-05 08:40:50
○NSdns1.registrar-servers.com,2015-11-04 → 2016-08-12 · 4 obs
● 2015-11-04 18:02:00
● 2016-08-12 00:36:24
○ 2017-03-25 17:25:14
○ 2026-08-05 08:40:50
○NSdns10.hichina.com2017-03-25 → 2017-03-25 · 4 obs
○ 2016-08-12 00:36:24
● 2017-03-25 17:25:14
○ 2026-07-10 06:08:02
○ 2026-08-05 08:40:50
○NSdns2.registrar-servers.com2015-11-04 → 2016-08-12 · 4 obs
● 2015-11-04 18:02:00
● 2016-08-12 00:36:24
○ 2017-03-25 17:25:14
○ 2026-08-05 08:40:50
○NSdns3.registrar-servers.com2015-11-04 → 2016-08-12 · 4 obs
● 2015-11-04 18:02:00
● 2016-08-12 00:36:24
○ 2017-03-25 17:25:14
○ 2026-08-05 08:40:50
○NSdns4.registrar-servers.com2015-11-04 → 2016-08-12 · 4 obs
● 2015-11-04 18:02:00
● 2016-08-12 00:36:24
○ 2017-03-25 17:25:14
○ 2026-08-05 08:40:50
○NSdns5.registrar-servers.com2015-11-04 → 2016-08-12 · 4 obs
● 2015-11-04 18:02:00
● 2016-08-12 00:36:24
○ 2017-03-25 17:25:14
○ 2026-08-05 08:40:50
○NSdns9.hichina.com2017-03-25 → 2017-03-25 · 4 obs
○ 2016-08-12 00:36:24
● 2017-03-25 17:25:14
○ 2026-07-10 06:08:02
○ 2026-08-05 08:40:50
○NSexpire01.dnspod.net2026-07-10 → 2026-08-05 · 2 obs
○ 2026-07-10 06:08:02
○ 2026-08-05 08:40:50
○NSexpire02.dnspod.net2026-07-10 → 2026-08-05 · 2 obs
○ 2026-07-10 06:08:02
○ 2026-08-05 08:40:50
●NSns1.judns.com2026-07-10 → 2026-08-05 · 3 obs
○ 2017-03-25 17:25:14
● 2026-07-10 06:08:02
● 2026-08-05 08:40:50
●NSns1.julydns.com2026-07-10 → 2026-08-05 · 3 obs
○ 2017-03-25 17:25:14
● 2026-07-10 06:08:02
● 2026-08-05 08:40:50
●NSns2.judns.com2026-07-10 → 2026-08-05 · 3 obs
○ 2017-03-25 17:25:14
● 2026-07-10 06:08:02
● 2026-08-05 08:40:50
●NSns2.julydns.com2026-07-10 → 2026-08-05 · 3 obs
○ 2017-03-25 17:25:14
● 2026-07-10 06:08:02
● 2026-08-05 08:40:50
○MXeforward1.registrar-servers.com2015-11-04 → 2016-08-12 · 4 obs
● 2015-11-04 18:02:00
● 2016-08-12 00:36:24
○ 2017-03-25 17:25:14
○ 2026-08-05 08:40:50
○MXeforward2.registrar-servers.com2015-11-04 → 2016-08-12 · 4 obs
● 2015-11-04 18:02:00
● 2016-08-12 00:36:24
○ 2017-03-25 17:25:14
○ 2026-08-05 08:40:50
○MXeforward3.registrar-servers.com2015-11-04 → 2016-08-12 · 4 obs
● 2015-11-04 18:02:00
● 2016-08-12 00:36:24
○ 2017-03-25 17:25:14
○ 2026-08-05 08:40:50
○MXeforward4.registrar-servers.com2015-11-04 → 2016-08-12 · 4 obs
● 2015-11-04 18:02:00
● 2016-08-12 00:36:24
○ 2017-03-25 17:25:14
○ 2026-08-05 08:40:50
○MXeforward5.registrar-servers.com2015-11-04 → 2016-08-12 · 4 obs
● 2015-11-04 18:02:00
● 2016-08-12 00:36:24
○ 2017-03-25 17:25:14
○ 2026-08-05 08:40:50
○A192.64.119.2432015-11-04 → 2016-08-12 · 4 obs
● 2015-11-04 18:02:00
● 2016-08-12 00:36:24
○ 2017-03-25 17:25:14
○ 2026-08-05 08:40:50
○CNAMEdomainexpired.domain-expired.com2026-07-10 → 2026-08-05 · 2 obs
○ 2026-07-10 06:08:02
○ 2026-08-05 08:40:50

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
doctorchain.comns1.judns.com, ns2.judns.com2 records

✅ Authoritative Response

Server:162.159.27.251

NS records: ns1.judns.com, ns2.judns.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for doctorchain.com (unsigned zone)

⏱️ Timing

Total: 388ms | Queries: -

📄 Records

TypeCountSample Data
NS2ns1.julydns.com, ns2.julydns.com

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.judns.com, ns2.judns.com)

Analysis

Name Servers

doctorchain.com has four authoritative name servers: ns1.judns.com, ns2.judns.com, ns1.julydns.com and ns2.julydns.com.

doctorchain.com has at least partial name server overlap with other domains, such as jfaiyun.com, premierleague-douyin.com, hangfiao.com and two others.

It is common to see these name servers used together with name servers ns1.onclouddns.com and ns2.onclouddns.com.

ns1.judns.com and ns2.judns.com each resolve to 162.159.27.251, while ns1.julydns.com and ns2.julydns.com each resolve to 162.159.48.223.

Both ns1.judns.com and ns2.judns.com resolve to 162.159.27.251 IP addresses each.

Both ns1.julydns.com and ns2.julydns.com resolve to 162.159.48.223 IP addresses each.