cryptole.com - dns.ninja

`cryptole.com`

DNSSEC	⚠️ Not signed
A	54.215.31.113^{🇺🇸 Amazon54.215.0.0/17 EC2 SFO prefix}
		PTR	`ec2-54-215-31-113.us-west-1.compute.amazonaws.com`
NS	`ns1.dyna-ns.net` ⭐
		A	2400:cb00:2049:1::a29f:1a5c^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	2400:cb00:2049:1::a29f:1b9e^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.26.92^{Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.dyna-ns.net`
		A	162.159.27.158^{Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.dyna-ns.net`
NS	`ns2.dyna-ns.net`
		A	2400:cb00:2049:1::a29f:1805^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	2400:cb00:2049:1::a29f:1905^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.24.5^{Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.dyna-ns.net`
		A	162.159.25.5^{Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.dyna-ns.net`
SOA	`ns1.dyna-ns.net`hostmaster@cryptole.com 2026-07-01 #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=1785493757

Same first word

cryptole.com

Similar names

cortyple.com

polycert.com

tyleropc.com

coprytel.com

cyprotel.com

lytecorp.com

polycret.com

elcrypto.com

elcrypto.pro

polycret.eu

protecly.com

cryptelo.com

DNS History

19 records (3 active, 16 former)

○NSns1.afternic.com2026-04-04 → 2026-04-04 · 4 obs

○ 2017-08-14 20:40:34
● 2026-04-04 05:38:18
○ 2026-06-25 08:08:54
○ 2026-07-31 10:49:00

●NSns1.dyna-ns.net2026-06-25 → 2026-07-31 · 3 obs

○ 2026-04-04 05:38:18
● 2026-06-25 08:08:54
● 2026-07-31 10:49:00

○NSns2.afternic.com2026-04-04 → 2026-04-04 · 4 obs

○ 2017-08-14 20:40:34
● 2026-04-04 05:38:18
○ 2026-06-25 08:08:54
○ 2026-07-31 10:49:00

●NSns2.dyna-ns.net2026-06-25 → 2026-07-31 · 3 obs

○ 2026-04-04 05:38:18
● 2026-06-25 08:08:54
● 2026-07-31 10:49:00

○NSpdns11.domaincontrol.com2017-08-14 → 2017-08-14 · 3 obs

● 2017-08-14 20:40:34
○ 2026-04-04 05:38:18
○ 2026-07-31 10:49:00

○NSpdns12.domaincontrol.com2017-08-14 → 2017-08-14 · 3 obs

● 2017-08-14 20:40:34
○ 2026-04-04 05:38:18
○ 2026-07-31 10:49:00

○MX.2026-04-04 → 2026-07-31 · 2 obs

○ 2026-04-04 05:38:18
○ 2026-07-31 10:49:00

○A13.248.169.482026-04-04 → 2026-04-04 · 4 obs

○ 2017-08-14 20:40:34
● 2026-04-04 05:38:18
○ 2026-06-25 08:08:54
○ 2026-07-31 10:49:00

○A184.168.221.142017-08-14 → 2017-08-14 · 3 obs

● 2017-08-14 20:40:34
○ 2026-04-04 05:38:18
○ 2026-07-31 10:49:00

○A184.168.221.262017-08-14 → 2017-08-14 · 3 obs

● 2017-08-14 20:40:34
○ 2026-04-04 05:38:18
○ 2026-07-31 10:49:00

○A184.168.221.272017-08-14 → 2017-08-14 · 3 obs

● 2017-08-14 20:40:34
○ 2026-04-04 05:38:18
○ 2026-07-31 10:49:00

○A184.168.221.312017-08-14 → 2017-08-14 · 3 obs

● 2017-08-14 20:40:34
○ 2026-04-04 05:38:18
○ 2026-07-31 10:49:00

○A184.168.221.82017-08-14 → 2017-08-14 · 3 obs

● 2017-08-14 20:40:34
○ 2026-04-04 05:38:18
○ 2026-07-31 10:49:00

○A50.63.202.102017-08-14 → 2017-08-14 · 3 obs

● 2017-08-14 20:40:34
○ 2026-04-04 05:38:18
○ 2026-07-31 10:49:00

○A50.63.202.192017-08-14 → 2017-08-14 · 3 obs

● 2017-08-14 20:40:34
○ 2026-04-04 05:38:18
○ 2026-07-31 10:49:00

○A50.63.202.32017-08-14 → 2017-08-14 · 3 obs

● 2017-08-14 20:40:34
○ 2026-04-04 05:38:18
○ 2026-07-31 10:49:00

○A50.63.202.92017-08-14 → 2017-08-14 · 3 obs

● 2017-08-14 20:40:34
○ 2026-04-04 05:38:18
○ 2026-07-31 10:49:00

●A54.215.31.1132026-06-25 → 2026-07-31 · 9 obs

○ 2026-04-04 05:38:18
● 2026-06-25 08:08:54
○ 2026-07-01 18:21:08
● 2026-07-02 08:19:08
○ 2026-07-09 21:26:20
● 2026-07-09 22:21:42
○ 2026-07-10 11:57:22
● 2026-07-10 12:50:10
● 2026-07-31 10:49:00

○A76.223.54.1462026-04-04 → 2026-04-04 · 4 obs

○ 2017-08-14 20:40:34
● 2026-04-04 05:38:18
○ 2026-06-25 08:08:54
○ 2026-07-31 10:49: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...	-
cryptole.com	ns2.dyna-ns.net, ns1.dyna-ns.net	-

✅ Authoritative Response

Server:162.159.24.5

NS records: ns2.dyna-ns.net, ns1.dyna-ns.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for cryptole.com (unsigned zone)

⏱️ Timing

Total: 244ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`54.215.31.113`
NS	2	`ns1.dyna-ns.net, ns2.dyna-ns.net`
SOA	1	`ns1.dyna-ns.net hostmaster.cryptole.com`

Analysis

IP Addresses

cryptole.com has exactly one IP address — 54.215.31.113.

pandigon.com, y0h.com, www.76065.cc plus two other host names have IP numbers in common with cryptole.com.

Name Servers

cryptole.com has two authoritative name servers — ns1.dyna-ns.net and ns2.dyna-ns.net.

The name server configuration of cryptole.com is shared with other domains, for instance gov-zkh.vip, adiharriman.com, qeem.shop and two others.

Each of the hosts ns1.dyna-ns.net and ns2.dyna-ns.net has four IP addresses: ns1.dyna-ns.net points to 162.159.26.92, 162.159.27.158, 2400:cb00:2049:1::a29f:1a5c and 2400:cb00:2049:1::a29f:1b9e, and ns2.dyna-ns.net points to 162.159.24.5, 162.159.25.5, 2400:cb00:2049:1::a29f:1805 and 2400:cb00:2049:1::a29f:1905.