`cryptocopilot.app`

DNSSEC	⚠️ Not signed
A	13.248.213.45^{🇺🇸 Amazon13.248.208.0/20}
		PTR	`a67c48129651a0940.awsglobalaccelerator.com`
A	76.223.67.189^{🇺🇸 Amazon76.223.64.0/20}
NS	`ns67.domaincontrol.com` ⭐
		A	2603:5:2174::2c^{🇺🇸 GODADDY-DNS2603:5:2170::/44}
			PTR	`ns67.domaincontrol.com`
		A	97.74.103.44^{🇺🇸 GODADDY-DNS97.74.102.0/23}
			PTR	`ns67.domaincontrol.com`
NS	`ns68.domaincontrol.com`
		A	2603:5:2274::2c^{🇺🇸 GODADDY-DNS2603:5:2270::/44}
			PTR	`ns68.domaincontrol.com`
		A	173.201.71.44^{🇺🇸 GODADDY-DNS173.201.70.0/23}
			PTR	`ns68.domaincontrol.com`
TXT	`NETORGFT16103413.onmicrosoft.com`
TXT	`v=spf1 include:secureserver.net -all`
SOA	`ns67.domaincontrol.com`dns@jomax.net 2026-04-22 #0

`app`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns-tld1.charlestonroadregistry.com` ⭐
	NS	`ns-tld2.charlestonroadregistry.com`
	NS	`ns-tld3.charlestonroadregistry.com`
	NS	`ns-tld4.charlestonroadregistry.com`
	NS	`ns-tld5.charlestonroadregistry.com`
	SOA	`ns-tld1.charlestonroadregistry.com`cloud-dns-hostmaster@google.com serial=101427

⚠️ On DNS blocklist: tif
🔒 HSTS Preload (+subdomains)

Same first word

cryptocopilot.app

DNS History

7 records (4 active, 3 former)

●NSns67.domaincontrol.com2026-04-13 → 2026-04-27 · 2 obs

● 2026-04-13 08:06:54
● 2026-04-27 09:25:32

●NSns68.domaincontrol.com2026-04-13 → 2026-04-27 · 2 obs

● 2026-04-13 08:06:54
● 2026-04-27 09:25:32

○MXcryptocopilot-app.mail.protection.outlook.com2026-04-13 → 2026-04-13 · 3 obs

● 2026-04-13 08:06:54
○ 2026-04-23 21:48:54
○ 2026-04-27 09:25:32

●A13.248.213.452026-04-23 → 2026-04-27 · 3 obs

○ 2026-04-13 08:06:54
● 2026-04-23 21:48:54
● 2026-04-27 09:25:32

○A15.197.148.332026-04-13 → 2026-04-13 · 3 obs

● 2026-04-13 08:06:54
○ 2026-04-23 21:48:54
○ 2026-04-27 09:25:32

○A3.33.130.1902026-04-13 → 2026-04-13 · 3 obs

● 2026-04-13 08:06:54
○ 2026-04-23 21:48:54
○ 2026-04-27 09:25:32

●A76.223.67.1892026-04-23 → 2026-04-27 · 3 obs

○ 2026-04-13 08:06:54
● 2026-04-23 21:48:54
● 2026-04-27 09:25:32

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
app	ns-tld3.charlestonroadregistry.com, ns-tld5.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com...	-
cryptocopilot.app	ns67.domaincontrol.com, ns68.domaincontrol.com	-

✅ Authoritative Response

Server:97.74.103.44

NS records: ns67.domaincontrol.com, ns68.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for cryptocopilot.app (unsigned zone)

⏱️ Timing

Total: 311ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`76.223.67.189, 13.248.213.45`
NS	2	`ns67.domaincontrol.com, ns68.domaincontrol.com`
TXT	2	`NETORGFT16103413.onmicrosoft.com, v=spf1 include:secureserver.net -all`
SOA	1	`ns67.domaincontrol.com dns.jomax.net`

Analysis

IP Addresses

cryptocopilot.app points to two IP numbers: 13.248.213.45 and 76.223.67.189.

Other host names such as fromcal.com, zhensanguobt.com, taigamehay.org, inglistoncoroprate.com and llevame.link share IP numbers with cryptocopilot.app.

Name Servers

cryptocopilot.app is delegated to two name servers: ns67.domaincontrol.com and ns68.domaincontrol.com.

cryptocopilot.app uses the same name server setup as other domains, including tularecountykids.com, praxis-nicklas.de, fdef.com, robohell.com and luvmyvines.com.

cryptocopilot.app shares some name servers with other domains, for example ak8899.com.

Host names with two IP numbers:

ns67.domaincontrol.com points to 2603:5:2174::2c and 97.74.103.44.

ns68.domaincontrol.com points to 2603:5:2274::2c and 173.201.71.44.

cryptocopilot.app - robtex.com