🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`context-reader.com`

DNSSEC	⚠️ Not signed
A	43.143.122.238^{🇨🇳 TENCENT-NET-AP43.143.64.0/18}
NS	`taurus.dnspod.net` ⭐
		A	2402:4e00:1470:2::e^{🇨🇳 TENCENT-NET-AP2402:4e00:1400::/40}
		A	1.12.0.4^{🇨🇳 TENCENT-NET-AP-CN1.12.0.0/20 ZL-IDC-BOM}
		A	1.14.119.35^{🇨🇳 TENCENT-NET-AP1.14.64.0/18}
		A	111.13.13.35^{🇨🇳 CHINAMOBILE-CN111.13.0.0/16 CMI (Customer Route)}
		A	117.89.178.35^{🇨🇳 ChinaNet-NANJING-JISHAN-IDC117.89.176.0/21 JS-CT NJ-JS-IDC}
		A	220.196.136.35^{🇨🇳 UNICOM-SHFT-IDC220.196.136.0/24}
NS	`fixture.dnspod.net`
		A	2402:4e00:111:fff::c^{🇨🇳 TENCENT-NET-AP2402:4e00::/35}
		A	1.12.0.1^{🇨🇳 TENCENT-NET-AP-CN1.12.0.0/20 ZL-IDC-BOM}
		A	1.13.76.35^{🇨🇳 TENCENT-NET-AP1.13.64.0/18}
		A	36.155.149.35^{🇨🇳 CMNET-Jiangsu-AP36.155.144.0/21 CMI (Customer Route)}
		A	101.227.168.35^{🇨🇳 SHANGHAITELECOM101.227.168.0/23 SHIDC}
		A	111.206.98.235^{🇨🇳 CHINA169-BJ111.206.98.0/24}
SOA	`taurus.dnspod.net`freednsadmin@dnspod.com serial=1785737107

`com`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.gtld-servers.net` ⭐
	NS	`b.gtld-servers.net`
	NS	`c.gtld-servers.net`
	NS	`d.gtld-servers.net`
	NS	`e.gtld-servers.net`
	NS	`f.gtld-servers.net`
	NS	`g.gtld-servers.net`
	NS	`h.gtld-servers.net`
	NS	`i.gtld-servers.net`
	NS	`j.gtld-servers.net`
	NS	`k.gtld-servers.net`
	NS	`l.gtld-servers.net`
	NS	`m.gtld-servers.net`
	SOA	`a.gtld-servers.net`nstld@verisign-grs.com serial=1790805464

Same first word

context-reader.workers.dev

context-reader.com

context-reader.pages.dev

Previous names

Next names

DNS History

3 records (3 active, 0 former)

●NSfixture.dnspod.net2026-09-11 → 2026-09-30 · 2 obs

● 2026-09-11 01:31:46
● 2026-09-30 22:27:22

●NStaurus.dnspod.net2026-09-11 → 2026-09-30 · 2 obs

● 2026-09-11 01:31:46
● 2026-09-30 22:27:22

●A43.143.122.2382026-09-11 → 2026-09-30 · 2 obs

● 2026-09-11 01:31:46
● 2026-09-30 22:27:22

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
context-reader.com	taurus.dnspod.net, fixture.dnspod.net	-

✅ Authoritative Response

Server:117.89.178.35

NS records: taurus.dnspod.net, fixture.dnspod.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for context-reader.com (unsigned zone)

⏱️ Timing

Total: 1056ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`43.143.122.238`
NS	2	`fixture.dnspod.net, taurus.dnspod.net`
SOA	1	`taurus.dnspod.net freednsadmin.dnspod.co`

Analysis

IP Addresses

context-reader.com resolves to one IP address: 43.143.122.238.

Name Servers

context-reader.com is delegated to two name servers: fixture.dnspod.net and taurus.dnspod.net.

context-reader.com uses the same name servers as several other domains — among them mqzww.com, weikefuwu01.com, tesps.com and two more.

The name servers for context-reader.com are partially shared with other domains like winnnnnnnn.com, 51shangqiang.com and icfengshui.com

It is common to see these name servers used together with name servers ns3.dnsv2.com and ns4.dnsv2.com.

Hostnames that resolve to 6 IP addresses:

fixture.dnspod.net resolves to 1.12.0.1, 1.13.76.35, 36.155.149.35 and 3 other IP addresses.

taurus.dnspod.net resolves to 1.12.0.4, 1.14.119.35, 111.13.13.35 and 3 other IP addresses.

context-reader.com - dns.ninja