`v2xdatacenter.com`

DNSSEC	⚠️ Not signed
NS	`f1g1ns1.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.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	`ivy.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	112.80.181.45^{🇨🇳 CHINA169-Backbone112.80.0.0/13 China Unicom CHINA169 Jiangsu Province Network}
		A	117.89.178.173^{🇨🇳 ChinaNet-NANJING-JISHAN-IDC117.89.176.0/21 JS-CT NJ-JS-IDC}
NS	`justin.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	36.155.149.176^{🇨🇳 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}
		A	129.211.176.239^{🇨🇳 TENCENT-NET-AP129.211.176.0/20}
SOA	`f1g1ns1.dnspod.net`nxdomainadmin@dnspod.com serial=1

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

Same first word

v2xdatacenter.com

DNS History

3 records (3 active, 0 former)

●NSf1g1ns1.dnspod.net2026-04-21 → 2026-05-08 · 2 obs

● 2026-04-21 15:57:28
● 2026-05-08 04:55:42

●NSivy.dnspod.net2026-04-21 → 2026-05-08 · 2 obs

● 2026-04-21 15:57:28
● 2026-05-08 04:55:42

●NSjustin.dnspod.net2026-04-21 → 2026-05-08 · 2 obs

● 2026-04-21 15:57:28
● 2026-05-08 04:55:42

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
v2xdatacenter.com	ivy.dnspod.net, justin.dnspod.net	-

✅ Authoritative Response

Server:1.14.119.35

NS records: ivy.dnspod.net, justin.dnspod.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for v2xdatacenter.com (unsigned zone)

⏱️ Timing

Total: 857ms | Queries: -

📄 Records

Type	Count	Sample Data
SOA	1	`f1g1ns1.dnspod.net nxdomainadmin.dnspod.`

Analysis

Name Servers

v2xdatacenter.com is delegated to three name servers: f1g1ns1.dnspod.net, ivy.dnspod.net and justin.dnspod.net.

v2xdatacenter.com at least partially shares its name servers with other domains, for instance huangyiyang.com, slaxh.com, lejucloud.com, faxingw.cn and dxftt.com.

These name servers are often used together with the name servers f1g1ns2.dnspod.net.

Host names with seven IP numbers: f1g1ns1.dnspod.net points to: 2402:4e00:1470:2::e, 1.12.0.4, 1.14.119.35, 111.13.13.35, 117.135.128.235, 125.94.59.235 and 163.177.5.35.

Host names with six IP numbers: ivy.dnspod.net points to: 2402:4e00:1470:2::e, 1.12.0.4, 1.14.119.35, 111.13.13.35, 112.80.181.45 and 117.89.178.173; justin.dnspod.net points to: 2402:4e00:111:fff::c, 1.12.0.1, 36.155.149.176, 101.227.168.35, 111.206.98.235 and 129.211.176.239.

Host names that point to 2402:4e00:1470:2::e: f1g1ns1.dnspod.net and ivy.dnspod.net; host names that point to 1.12.0.4: f1g1ns1.dnspod.net and ivy.dnspod.net; host names that point to 1.14.119.35: f1g1ns1.dnspod.net and ivy.dnspod.net; host names that point to 111.13.13.35: f1g1ns1.dnspod.net and ivy.dnspod.net.

v2xdatacenter.com - robtex.com