`trafficverify.com`

DNSSEC	⚠️ Not signed
A	15.197.212.58^{🇺🇸 Amazon15.197.208.0/20}
		PTR	`af1f69020f2387294.awsglobalaccelerator.com`
NS	`dns1.name-services.com` ⭐
		A	2604:4000:2800:2000:64:98:148:137^{🇨🇦 TUCOWS-32604:4000:2800::/37 Tucows.com Co.}
			PTR	`dns1.name-services.com`
		A	64.98.148.137^{🇨🇦 TUCOWS-364.98.144.0/20 Tucows.com Co.}
			PTR	`dns1.name-services.com`
NS	`dns2.name-services.com`
		A	2604:4000:0:d:216:40:47:201^{🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000}
			PTR	`dns2.name-services.com`
		A	216.40.47.201^{🇨🇦 TUCOWS216.40.47.0/24 -BRA-BLK1.4/NET-216-40-47-0}
			PTR	`dns2.name-services.com`
NS	`dns3.name-services.com`
		A	2604:4000:2800:2000:64:98:148:138^{🇨🇦 TUCOWS-32604:4000:2800::/37 Tucows.com Co.}
			PTR	`dns3.name-services.com`
		A	64.98.148.138^{🇨🇦 TUCOWS-364.98.144.0/20 Tucows.com Co.}
			PTR	`dns3.name-services.com`
NS	`dns4.name-services.com`
		A	2604:4000:0:d:216:40:47:202^{🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000}
			PTR	`dns4.name-services.com`
		A	216.40.47.202^{🇨🇦 TUCOWS216.40.47.0/24 -BRA-BLK1.4/NET-216-40-47-0}
			PTR	`dns4.name-services.com`
NS	`dns5.name-services.com`
		A	2604:4000:2800:2000:64:98:148:139^{🇨🇦 TUCOWS-32604:4000:2800::/37 Tucows.com Co.}
			PTR	`dns5.name-services.com`
		A	64.98.148.139^{🇨🇦 TUCOWS-364.98.144.0/20 Tucows.com Co.}
			PTR	`dns5.name-services.com`
SOA	`dns1.name-services.com`info@name-services.com serial=1729450828

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

Same first word

trafficverify.com

DNS History

12 records (6 active, 6 former)

○NSbuy.internettraffic.com2015-06-23 → 2016-07-22 · 6 obs

● 2015-06-23 11:26:12
○ 2015-11-23 15:40:56
○ 2016-03-10 13:51:54
● 2016-07-22 09:43:50
○ 2017-05-14 09:38:04
○ 2026-03-24 20:48:16

●NSdns1.name-services.com2015-11-23 → 2026-03-24 · 6 obs

○ 2015-06-23 11:26:12
● 2015-11-23 15:40:56
● 2016-03-10 13:51:54
○ 2016-07-22 09:43:50
● 2017-05-14 09:38:04
● 2026-03-24 20:48:16

●NSdns2.name-services.com2015-11-23 → 2026-03-24 · 6 obs

○ 2015-06-23 11:26:12
● 2015-11-23 15:40:56
● 2016-03-10 13:51:54
○ 2016-07-22 09:43:50
● 2017-05-14 09:38:04
● 2026-03-24 20:48:16

●NSdns3.name-services.com2015-11-23 → 2026-03-24 · 6 obs

○ 2015-06-23 11:26:12
● 2015-11-23 15:40:56
● 2016-03-10 13:51:54
○ 2016-07-22 09:43:50
● 2017-05-14 09:38:04
● 2026-03-24 20:48:16

●NSdns4.name-services.com2015-11-23 → 2026-03-24 · 6 obs

○ 2015-06-23 11:26:12
● 2015-11-23 15:40:56
● 2016-03-10 13:51:54
○ 2016-07-22 09:43:50
● 2017-05-14 09:38:04
● 2026-03-24 20:48:16

●NSdns5.name-services.com2015-11-23 → 2026-03-24 · 6 obs

○ 2015-06-23 11:26:12
● 2015-11-23 15:40:56
● 2016-03-10 13:51:54
○ 2016-07-22 09:43:50
● 2017-05-14 09:38:04
● 2026-03-24 20:48:16

○NSsell.internettraffic.com2015-06-23 → 2016-07-22 · 6 obs

● 2015-06-23 11:26:12
○ 2015-11-23 15:40:56
○ 2016-03-10 13:51:54
● 2016-07-22 09:43:50
○ 2017-05-14 09:38:04
○ 2026-03-24 20:48:16

●A15.197.212.582026-03-08 → 2026-03-24 · 3 obs

○ 2017-05-14 09:38:04
● 2026-03-08 22:19:56
● 2026-03-24 20:48:16

○A208.88.52.2132017-05-14 → 2017-05-14 · 4 obs

○ 2016-07-22 09:43:50
● 2017-05-14 09:38:04
○ 2026-03-08 22:19:56
○ 2026-03-24 20:48:16

○A65.204.15.502015-11-23 → 2016-03-10 · 5 obs

○ 2015-06-23 11:26:12
● 2015-11-23 15:40:56
● 2016-03-10 13:51:54
○ 2016-07-22 09:43:50
○ 2026-03-24 20:48:16

○A69.172.201.1532016-07-22 → 2016-07-22 · 4 obs

○ 2016-03-10 13:51:54
● 2016-07-22 09:43:50
○ 2017-05-14 09:38:04
○ 2026-03-24 20:48:16

○A69.172.201.2082015-06-23 → 2015-06-23 · 3 obs

● 2015-06-23 11:26:12
○ 2015-11-23 15:40:56
○ 2026-03-24 20:48:16

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
trafficverify.com	dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com...	10 records

✅ Authoritative Response

Server:64.98.148.137

NS records: dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com, dns5.name-services.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for trafficverify.com (unsigned zone)

⏱️ Timing

Total: 168ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`15.197.212.58`
NS	5	`dns4.name-services.com, dns5.name-services.com...`
SOA	1	`dns1.name-services.com info.name-service`

📌 Glue Records Collected

Total: 10

Out-of-bailiwick: 10 (dns1.name-services.com, dns1.name-services.com, dns2.name-services.com...)

Analysis

IP Addresses

trafficverify.com points to a single IP: 15.197.212.58.

Other host names, for instance packetblue.com, server.bsghosting.com, matanshok.com, beavercountians.com and test.r-zone.me share IP numbers with trafficverify.com.

Name Servers

trafficverify.com is delegated to five name servers: dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com and dns5.name-services.com.

trafficverify.com partially shares name servers with other domains; examples include incometaxauditors.com, luck.digital, certifiedsaleservice.com, centilon.com and energeon.com.

Host names with two IP numbers:

dns1.name-services.com points to: 2604:4000:2800:2000:64:98:148:137 and 64.98.148.137

dns2.name-services.com points to: 2604:4000:0:d:216:40:47:201 and 216.40.47.201

dns3.name-services.com points to: 2604:4000:2800:2000:64:98:148:138 and 64.98.148.138

dns4.name-services.com points to: 2604:4000:0:d:216:40:47:202 and 216.40.47.202

dns5.name-services.com points to: 2604:4000:2800:2000:64:98:148:139 and 64.98.148.139

trafficverify.com - robtex.com