podchip.com - dns.ninja

`podchip.com`

DNSSEC	⚠️ Not signed
A	35.213.134.148^{🇸🇬 Google35.213.128.0/18}
		PTR	`148.134.213.35.bc.googleusercontent.com`
NS	`ns1.myhostadmin.net` ⭐
		A	240e:d9:c200::2^{🇨🇳 CHINANET-SCIDC-AS-AP240e:d9:c000::/36 SICHUANIDC province network}
		A	60.247.150.254^{🇨🇳 CHINANET-SCIDC-AS-AP60.247.128.0/18 SICHUANIDC province network}
		A	118.123.249.114^{🇨🇳 CHINANET-SCIDC-AS-AP118.123.240.0/20 CHINANET SiChuan Telecom Internet Data Center}
		A	118.123.253.132^{🇨🇳 CHINANET-SCIDC-AS-AP118.123.240.0/20 CHINANET SiChuan Telecom Internet Data Center}
NS	`ns2.myhostadmin.net`
		A	240e:d9:c200:1::2^{🇨🇳 CHINANET-SCIDC-AS-AP240e:d9:c000::/36 SICHUANIDC province network}
		A	61.172.183.73^{🇨🇳 SHANGHAITELECOM61.172.182.0/23 SHIDC}
		A	61.240.129.143^{🇨🇳 CHINA169-Backbone61.240.128.0/19 CMI (Customer Route)}
		A	211.149.230.100^{🇨🇳 CHINANET-SCIDC-AS-AP211.149.224.0/19 chinanet SC province network-client}
NS	`ns3.myhostadmin.net`
		A	240e:d9:c200::2^{🇨🇳 CHINANET-SCIDC-AS-AP240e:d9:c000::/36 SICHUANIDC province network}
		A	61.172.183.77^{🇨🇳 SHANGHAITELECOM61.172.182.0/23 SHIDC}
		A	118.123.249.114^{🇨🇳 CHINANET-SCIDC-AS-AP118.123.240.0/20 CHINANET SiChuan Telecom Internet Data Center}
NS	`ns4.myhostadmin.net`
		A	240e:d9:c200:1::2^{🇨🇳 CHINANET-SCIDC-AS-AP240e:d9:c000::/36 SICHUANIDC province network}
		A	118.123.253.132^{🇨🇳 CHINANET-SCIDC-AS-AP118.123.240.0/20 CHINANET SiChuan Telecom Internet Data Center}
		A	211.149.230.100^{🇨🇳 CHINANET-SCIDC-AS-AP211.149.224.0/19 chinanet SC province network-client}
NS	`ns5.myhostadmin.net`
		A	240e:d9:c200::2^{🇨🇳 CHINANET-SCIDC-AS-AP240e:d9:c000::/36 SICHUANIDC province network}
		A	61.172.183.73^{🇨🇳 SHANGHAITELECOM61.172.182.0/23 SHIDC}
		A	118.123.249.114^{🇨🇳 CHINANET-SCIDC-AS-AP118.123.240.0/20 CHINANET SiChuan Telecom Internet Data Center}
NS	`ns6.myhostadmin.net`
		A	240e:d9:c200:1::2^{🇨🇳 CHINANET-SCIDC-AS-AP240e:d9:c000::/36 SICHUANIDC province network}
		A	60.247.150.13^{🇨🇳 CHINANET-SCIDC-AS-AP60.247.128.0/18 SICHUANIDC province network}
		A	118.123.253.132^{🇨🇳 CHINANET-SCIDC-AS-AP118.123.240.0/20 CHINANET SiChuan Telecom Internet Data Center}
MX	`mxdomain.qq.com` ⭐
SOA	`ns1.myhostadmin.net`dnsconct@myhostadmin.net 2020-08-07 #20

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

Same first word

podchip.com

Similar names

chippod.com

DNS History

18 records (8 active, 10 former)

○NSns1.above.com2016-04-15 → 2016-04-15 · 3 obs

● 2016-04-15 16:14:20
○ 2016-11-28 03:53:36
○ 2026-08-04 18:18:08

○NSns1.brainydns.com2016-11-28 → 2016-11-28 · 4 obs

○ 2016-04-15 16:14:20
● 2016-11-28 03:53:36
○ 2020-02-14 23:27:32
○ 2026-08-04 18:18:08

○NSns1.giow1012.siteground.us2020-02-14 → 2020-02-14 · 4 obs

○ 2016-11-28 03:53:36
● 2020-02-14 23:27:32
○ 2026-03-03 15:51:06
○ 2026-08-04 18:18:08

●NSns1.myhostadmin.net2026-03-03 → 2026-08-04 · 3 obs

○ 2020-02-14 23:27:32
● 2026-03-03 15:51:06
● 2026-08-04 18:18:08

○NSns2.above.com2016-04-15 → 2016-04-15 · 3 obs

● 2016-04-15 16:14:20
○ 2016-11-28 03:53:36
○ 2026-08-04 18:18:08

○NSns2.brainydns.com2016-11-28 → 2016-11-28 · 4 obs

○ 2016-04-15 16:14:20
● 2016-11-28 03:53:36
○ 2020-02-14 23:27:32
○ 2026-08-04 18:18:08

○NSns2.giow1012.siteground.us2020-02-14 → 2020-02-14 · 4 obs

○ 2016-11-28 03:53:36
● 2020-02-14 23:27:32
○ 2026-03-03 15:51:06
○ 2026-08-04 18:18:08

●NSns2.myhostadmin.net2026-03-03 → 2026-08-04 · 3 obs

○ 2020-02-14 23:27:32
● 2026-03-03 15:51:06
● 2026-08-04 18:18:08

●NSns3.myhostadmin.net2026-03-03 → 2026-08-04 · 3 obs

○ 2020-02-14 23:27:32
● 2026-03-03 15:51:06
● 2026-08-04 18:18:08

●NSns4.myhostadmin.net2026-03-03 → 2026-08-04 · 3 obs

○ 2020-02-14 23:27:32
● 2026-03-03 15:51:06
● 2026-08-04 18:18:08

●NSns5.myhostadmin.net2026-03-03 → 2026-08-04 · 3 obs

○ 2020-02-14 23:27:32
● 2026-03-03 15:51:06
● 2026-08-04 18:18:08

●NSns6.myhostadmin.net2026-03-03 → 2026-08-04 · 3 obs

○ 2020-02-14 23:27:32
● 2026-03-03 15:51:06
● 2026-08-04 18:18:08

○MXmail.post-host.net2016-04-15 → 2016-04-15 · 3 obs

● 2016-04-15 16:14:20
○ 2016-11-28 03:53:36
○ 2026-08-04 18:18:08

●MXmxdomain.qq.com2020-02-14 → 2026-08-04 · 3 obs

○ 2016-11-28 03:53:36
● 2020-02-14 23:27:32
● 2026-08-04 18:18:08

○A103.224.182.2362016-04-15 → 2016-04-15 · 3 obs

● 2016-04-15 16:14:20
○ 2016-11-28 03:53:36
○ 2026-08-04 18:18:08

○A158.69.143.1052016-11-28 → 2016-11-28 · 4 obs

○ 2016-04-15 16:14:20
● 2016-11-28 03:53:36
○ 2020-02-14 23:27:32
○ 2026-08-04 18:18:08

●A35.213.134.1482026-03-03 → 2026-08-04 · 3 obs

○ 2020-02-14 23:27:32
● 2026-03-03 15:51:06
● 2026-08-04 18:18:08

○A35.224.84.452020-02-14 → 2020-02-14 · 4 obs

○ 2016-11-28 03:53:36
● 2020-02-14 23:27:32
○ 2026-03-03 15:51:06
○ 2026-08-04 18:18:08

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
podchip.com	ns1.myhostadmin.net, ns2.myhostadmin.net, ns3.myhostadmin.net, ns4.myhostadmin.net...	-

✅ Authoritative Response

Server:60.247.150.13

NS records: ns1.myhostadmin.net, ns2.myhostadmin.net, ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for podchip.com (unsigned zone)

⏱️ Timing

Total: 3157ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`35.213.134.148`
NS	6	`ns6.myhostadmin.net, ns3.myhostadmin.net...`
MX	1	`mxdomain.qq.com (pri: 10)`
SOA	1	`ns1.myhostadmin.net dnsconct.myhostadmin`

Analysis

IP Addresses

podchip.com resolves to one IP address: 35.213.134.148.

pislo.com, sealpour.com, ysobscare.com.tw and two other host names share IP numbers with podchip.com.

Name Servers

podchip.com is served by 6 authoritative name servers — among them ns1.myhostadmin.net, ns2.myhostadmin.net, ns3.myhostadmin.net and 3 others.

The name servers of podchip.com overlap at least partially with those of other domains — among them huayaoele.com, maxtv.cn, aoyamed.com and two more.

These name servers commonly appear in delegations together with ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net and 6 other.

Hosts that point to four IP numbers:

ns1.myhostadmin.net resolves to 60.247.150.254, 118.123.249.114, 118.123.253.132 and 240e:d9:c200::2.

ns2.myhostadmin.net resolves to 61.172.183.73, 61.240.129.143, 211.149.230.100 and 240e:d9:c200:1::2.

Hostnames that resolve to three IP addresses:

The hostname ns3.myhostadmin.net points to 61.172.183.77, 118.123.249.114 and 240e:d9:c200::2.

The hostname ns4.myhostadmin.net points to 118.123.253.132, 211.149.230.100 and 240e:d9:c200:1::2.

The hostname ns5.myhostadmin.net points to 61.172.183.73, 118.123.249.114 and 240e:d9:c200::2.

The hostname ns6.myhostadmin.net points to 60.247.150.13, 118.123.253.132 and 240e:d9:c200:1::2.

The host names ns1.myhostadmin.net, ns3.myhostadmin.net and ns5.myhostadmin.net each resolve to 240e:d9:c200::2.

The host names ns1.myhostadmin.net, ns3.myhostadmin.net and ns5.myhostadmin.net each resolve to 118.123.249.114.

The host names ns1.myhostadmin.net, ns4.myhostadmin.net and ns6.myhostadmin.net each resolve to 118.123.253.132.

The host names ns2.myhostadmin.net, ns4.myhostadmin.net and ns6.myhostadmin.net each resolve to 240e:d9:c200:1::2.

ns2.myhostadmin.net along with ns5.myhostadmin.net each resolve to 61.172.183.73 IP addresses.

ns2.myhostadmin.net along with ns4.myhostadmin.net each resolve to 211.149.230.100 IP addresses.

Mail Servers

Mail for podchip.com is handled by a single mail server, mxdomain.qq.com.

podchip.com uses an identical mail server configuration to several other domains — among them whhack.com, pstatp.com, luwei.org and two more.

podchip.com has at least partial mail server overlap with other domains such as ktxmedia.com, hrlee.com, jxls.net and two more.

The mail servers mxn.mxhichina.com and mxw.mxhichina.com are commonly paired with these mail servers.