🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`ptreverse.net`

DNSSEC	⚠️ Not signed
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`
TXT	`v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all`
SOA	`dns1.name-services.com`info@name-services.com serial=1743532567

`net`

	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=1792822046

Same first word

ptreverse.net

ptreverse.com

ptreverse.org

Similar names

Previous names

Next names

DNS History

6 records (5 active, 1 former)

●NSdns1.name-services.com2015-08-21 → 2026-10-24 · 2 obs

● 2015-08-21 00:02:50
● 2026-10-24 06:34:52

●NSdns2.name-services.com2015-08-21 → 2026-10-24 · 2 obs

● 2015-08-21 00:02:50
● 2026-10-24 06:34:52

●NSdns3.name-services.com2015-08-21 → 2026-10-24 · 2 obs

● 2015-08-21 00:02:50
● 2026-10-24 06:34:52

●NSdns4.name-services.com2015-08-21 → 2026-10-24 · 2 obs

● 2015-08-21 00:02:50
● 2026-10-24 06:34:52

●NSdns5.name-services.com2015-08-21 → 2026-10-24 · 2 obs

● 2015-08-21 00:02:50
● 2026-10-24 06:34:52

○A72.32.194.1172015-08-21 → 2017-04-05 · 4 obs

● 2015-08-21 00:02:50
● 2017-04-05 23:35:20
○ 2026-09-07 01:06:46
○ 2026-10-24 06:34:52

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	e.gtld-servers.net, l.gtld-servers.net, i.gtld-servers.net, d.gtld-servers.net...	-
ptreverse.net	dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com...	-

✅ Authoritative Response

Server:216.40.47.202

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 ptreverse.net (unsigned zone)

⏱️ Timing

Total: 1175ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	5	`dns3.name-services.com, dns5.name-services.com...`
TXT	1	`v=spf1 include:%{ir}.%{v}.%{d}.spf.has.p`
SOA	1	`dns1.name-services.com info.name-service`

Analysis

Name Servers

Five name servers handle delegation for ptreverse.net: dns1.name-services.com, dns2.name-services.com, dns3.name-services.com and two others.

The name servers of ptreverse.net overlap at least partially with those of other domains — among them magnesafety.com, nevaio.com, bencher.net and two more.

These name servers commonly appear alongside the name servers dns4.name-services.com and dns5.name-services.com.

Host names pointing to two IP addresses:

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

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

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

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

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