potentialrelationship.com - dns.ninja

`potentialrelationship.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3034::ac43:c53c^{🇺🇸 Cloudflare2606:4700:3034::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3036::6815:44a9^{🇺🇸 Cloudflare2606:4700:3036::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.68.169^{Cloudflare104.21.64.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.197.60^{🇺🇸 Cloudflare172.67.192.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`boyd.ns.cloudflare.com` ⭐
		A	2606:4700:58::adf5:3b4b^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`boyd.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c14b^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`boyd.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:214b^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`boyd.ns.cloudflare.com`
		A	108.162.193.75^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`boyd.ns.cloudflare.com`
		A	172.64.33.75^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`boyd.ns.cloudflare.com`
		A	173.245.59.75^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`boyd.ns.cloudflare.com`
NS	`kate.ns.cloudflare.com`
		A	2606:4700:50::adf5:3a7c^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kate.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c07c^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`kate.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:207c^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`kate.ns.cloudflare.com`
		A	108.162.192.124^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kate.ns.cloudflare.com`
		A	172.64.32.124^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kate.ns.cloudflare.com`
		A	173.245.58.124^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kate.ns.cloudflare.com`
MX	`route1.mx.cloudflare.net` ⭐
		A	2606:4700:f5::b^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::c^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::d^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.11^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.12^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.13^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
MX	`route3.mx.cloudflare.net`⁽⁵⁴⁾
		A	2606:4700:f5::11^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::12^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::13^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.23^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.24^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.25^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
MX	`route2.mx.cloudflare.net`⁽⁶⁷⁾
		A	2606:4700:f5::e^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::f^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::10^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.17^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.18^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.19^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.68.169, 172.67.197.60
		IPv6 hints	2606:4700:3034::ac43:c53c, 2606:4700:3036::6815:44a9
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=106, name=cloudflare-ech.com
SOA	`boyd.ns.cloudflare.com`dns@cloudflare.com serial=2410497837

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

Same first word

potentialrelationship.com

DNS History

9 records (9 active, 0 former)

●NSboyd.ns.cloudflare.com2026-07-17 → 2026-07-28 · 2 obs

● 2026-07-17 05:32:20
● 2026-07-28 17:11:00

●NSkate.ns.cloudflare.com2026-07-17 → 2026-07-28 · 2 obs

● 2026-07-17 05:32:20
● 2026-07-28 17:11:00

●MXroute1.mx.cloudflare.net2026-07-17 → 2026-07-28 · 2 obs

● 2026-07-17 05:32:20
● 2026-07-28 17:11:00

●MXroute2.mx.cloudflare.net2026-07-17 → 2026-07-28 · 2 obs

● 2026-07-17 05:32:20
● 2026-07-28 17:11:00

●MXroute3.mx.cloudflare.net2026-07-17 → 2026-07-28 · 2 obs

● 2026-07-17 05:32:20
● 2026-07-28 17:11:00

●A104.21.68.1692026-07-17 → 2026-07-28 · 2 obs

● 2026-07-17 05:32:20
● 2026-07-28 17:11:00

●A172.67.197.602026-07-17 → 2026-07-28 · 2 obs

● 2026-07-17 05:32:20
● 2026-07-28 17:11:00

●A2606:4700:3034::ac43:c53c2026-07-17 → 2026-07-28 · 2 obs

● 2026-07-17 05:32:20
● 2026-07-28 17:11:00

●A2606:4700:3036::6815:44a92026-07-17 → 2026-07-28 · 2 obs

● 2026-07-17 05:32:20
● 2026-07-28 17:11:00

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
potentialrelationship.com	kate.ns.cloudflare.com, boyd.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.192.124

NS records: kate.ns.cloudflare.com, boyd.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for potentialrelationship.com (unsigned zone)

⏱️ Timing

Total: 173ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.67.197.60, 104.21.68.169`
AAAA	2	`2606:4700:3034::ac43:c53c, 2606:4700:3036::6815:44a9`
NS	2	`boyd.ns.cloudflare.com, kate.ns.cloudflare.com`
MX	3	`route1.mx.cloudflare.net (pri: 27), route3.mx.cloudflare.net (pri: 54)...`
TXT	1	`v=spf1 include:_spf.mx.cloudflare.net ~a`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`boyd.ns.cloudflare.com dns.cloudflare.co`

📌 Glue Records Collected

Total: 12

Out-of-bailiwick: 12 (kate.ns.cloudflare.com, kate.ns.cloudflare.com, kate.ns.cloudflare.com...)

Analysis

IP Addresses

potentialrelationship.com points to the four IP addresses 104.21.68.169, 172.67.197.60, 2606:4700:3034::ac43:c53c and 2606:4700:3036::6815:44a9.

Among the host names that share IP numbers with potentialrelationship.com are beautycos.it, untangled.finance, forum.migrationhelp.com.au and two others.

Name Servers

potentialrelationship.com is delegated to two name servers: boyd.ns.cloudflare.com and kate.ns.cloudflare.com.

potentialrelationship.com has the same name server delegation as a number of other domains, such as social-friend.com, kingyolo.com, passionease.com and two more.

There is at least partial name server overlap between potentialrelationship.com and other domains — uzinfo.com, new-pc-app.com, mobobeat.com and two more among them.

Host names resolving to 6 IP numbers:

boyd.ns.cloudflare.com resolves to 108.162.193.75, 172.64.33.75, 173.245.59.75 and 3 other IP addresses.

kate.ns.cloudflare.com resolves to 108.162.192.124, 172.64.32.124, 173.245.58.124 and 3 other IP addresses.

Mail Servers

Incoming mail for potentialrelationship.com is delivered via three mail servers: route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

potentialrelationship.com shares at least some of its mail servers with other domains — for example dealershipshirts.com, katematch.com, mohawkapps.com and two more.

Host names resolving to 6 IP numbers:

route1.mx.cloudflare.net resolves to 162.159.205.11, 162.159.205.12, 162.159.205.13 and 3 other IP addresses.

route2.mx.cloudflare.net resolves to 162.159.205.17, 162.159.205.18, 162.159.205.19 and 3 other IP addresses.

route3.mx.cloudflare.net resolves to 162.159.205.23, 162.159.205.24, 162.159.205.25 and 3 other IP addresses.