peapowtech.com - dns.ninja

`peapowtech.com`

DNSSEC	⚠️ Not signed
NS	`f1g1ns1.dnspod.net` ⭐ ⚠️ Not in parent delegation
		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.135.128.235^{🇨🇳 CHINAMOBILE-CN117.135.128.0/24 CMI (Customer Route)}
			PTR	`(root)`
		A	125.94.59.235^{🇨🇳 CHINANET-BACKBONE125.88.0.0/13 chinanet Guangdong network}
		A	163.177.5.35^{🇨🇳 UNICOM-GuangZhou-IDC163.177.5.0/24}
NS	`f1g1ns2.dnspod.net` ⚠️ Not in parent delegation
		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	106.39.207.235^{🇨🇳 CHINA-1106.39.192.0/19 China Telecom Beijing Co. Ltd.}
		A	111.206.98.235^{🇨🇳 CHINA169-BJ111.206.98.0/24}
		A	220.196.136.35^{🇨🇳 UNICOM-SHFT-IDC220.196.136.0/24}
NS	`lead.dnspod.net` ⚠️ Not in zone NS records
		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}
NS	`rugby.dnspod.net` ⚠️ Not in zone NS records
		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}
SOA	`f1g1ns1.dnspod.net`freednsadmin@dnspod.com serial=1762309450

`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=1783451171

Same first word

peapowtech.com

DNS History

5 records (4 active, 1 former)

●NSf1g1ns1.dnspod.net2026-04-12 → 2026-07-07 · 2 obs

● 2026-04-12 14:15:28
● 2026-07-07 19:09:12

●NSf1g1ns2.dnspod.net2026-04-12 → 2026-07-07 · 2 obs

● 2026-04-12 14:15:28
● 2026-07-07 19:09:12

●NSlead.dnspod.net2026-04-12 → 2026-07-07 · 2 obs

● 2026-04-12 14:15:28
● 2026-07-07 19:09:12

●NSrugby.dnspod.net2026-04-12 → 2026-07-07 · 2 obs

● 2026-04-12 14:15:28
● 2026-07-07 19:09:12

○CNAMEall.apigw4.8il8eo8i.com2026-04-12 → 2026-04-12 · 3 obs

● 2026-04-12 14:15:28
○ 2026-04-17 12:36:26
○ 2026-07-07 19:09:12

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	i.gtld-servers.net, c.gtld-servers.net, g.gtld-servers.net, a.gtld-servers.net...	-
peapowtech.com	rugby.dnspod.net, lead.dnspod.net	-

✅ Authoritative Response

Server:1.12.0.1

NS records: rugby.dnspod.net, lead.dnspod.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for peapowtech.com (unsigned zone)

⏱️ Timing

Total: 1936ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`f1g1ns2.dnspod.net, f1g1ns1.dnspod.net`
SOA	1	`f1g1ns1.dnspod.net freednsadmin.dnspod.c`

Analysis

Name Servers

The domain peapowtech.com is delegated to these four name servers: f1g1ns1.dnspod.net, f1g1ns2.dnspod.net, lead.dnspod.net and rugby.dnspod.net.

The name servers of peapowtech.com overlap at least partially with those of other domains — among them updatemssoft.com, jinchengpifubing.com, elitescloud.com and two more.

These name servers commonly appear in delegations together with ns3.dnsv4.com, ns4.dnsv4.com, a.dnspod.com and 3 other.

Host names resolving to 8 IP numbers:

Hostname f1g1ns2.dnspod.net directs to 1.12.0.1, 1.13.76.35 and 36.155.149.35 along with 5 other IP addresses.

Host names resolving to 7 IP numbers:

Hostname f1g1ns1.dnspod.net directs to 1.12.0.4, 1.14.119.35 and 111.13.13.35 along with 4 other IP addresses.

Host names resolving to 6 IP numbers:

Hostname lead.dnspod.net directs to 1.12.0.1, 1.13.76.35 and 36.155.149.35 along with 3 other IP addresses.

Hostname rugby.dnspod.net directs to 1.12.0.4, 1.14.119.35 and 111.13.13.35 along with 3 other IP addresses.

Both f1g1ns2.dnspod.net and lead.dnspod.net resolve to 2402:4e00:111:fff::c IP addresses each.

Both f1g1ns2.dnspod.net and lead.dnspod.net resolve to 1.12.0.1 IP addresses each.

Both f1g1ns2.dnspod.net and lead.dnspod.net resolve to 1.13.76.35 IP addresses each.

Both f1g1ns2.dnspod.net and lead.dnspod.net resolve to 36.155.149.35 IP addresses each.

Both f1g1ns2.dnspod.net and lead.dnspod.net resolve to 101.227.168.35 IP addresses each.

Both f1g1ns2.dnspod.net and lead.dnspod.net resolve to 111.206.98.235 IP addresses each.

Both f1g1ns2.dnspod.net and rugby.dnspod.net resolve to 220.196.136.35 IP addresses each.

Both f1g1ns1.dnspod.net and rugby.dnspod.net resolve to 2402:4e00:1470:2::e IP addresses each.

Both f1g1ns1.dnspod.net and rugby.dnspod.net resolve to 1.12.0.4 IP addresses each.

Both f1g1ns1.dnspod.net and rugby.dnspod.net resolve to 1.14.119.35 IP addresses each.

Both f1g1ns1.dnspod.net and rugby.dnspod.net resolve to 111.13.13.35 IP addresses each.