cryptorex.com - dns.ninja

`cryptorex.com`

DNSSEC	⚠️ Not signed
A	13.56.33.8^{🇺🇸 Amazon13.56.0.0/16 EC2 Region prefix}
		PTR	`ec2-13-56-33-8.us-west-1.compute.amazonaws.com`
NS	`ns1.brandbucket.com` ⭐
		A	2600:1f1c:800:8b01:2ba3:bb61:44fb:b361^{🇺🇸 Amazon2600:1f1c:800::/38 AMAZON AWS}
		A	54.241.53.41^{🇺🇸 Amazon54.241.0.0/17 EC2 SFO prefix}
			PTR	`ec2-54-241-53-41.us-west-1.compute.amazonaws.com`
NS	`ns2.brandbucket.com`
		A	2600:1f16:54:8701:4012:7e34:5c5f:95a8^{🇺🇸 Amazon2600:1f16::/38 AMAZON AWS}
		A	18.221.52.246^{🇺🇸 Amazon18.220.0.0/14 EC2 CMH prefix}
			PTR	`ec2-18-221-52-246.us-east-2.compute.amazonaws.com`
TXT	`27aab5373841b85aab94982ee19ab62f96481ed6`
TXT	`afternic-verification-cvgUQU8SkLxsjXcPBSk2CM`
TXT	`v=spf1 -all`
SOA	`ns1.brandbucket.com`mail@cryptorex.com 2024-03-05 #2

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

Same first word

cryptorex.com

cryptorex.net

cryptorex.space

Similar names

certproxy.com

cryoxpert.com

xerocrypt.github.io

rexcrypto.com

DNS History

21 records (3 active, 18 former)

○NSdns1.registrar-servers.com2016-07-08 → 2017-02-03 · 5 obs

○ 2015-09-24 02:39:12
● 2016-07-08 01:13:46
● 2017-02-03 17:12:12
○ 2026-03-28 14:08:36
○ 2026-08-06 18:06:40

○NSdns2.registrar-servers.com2016-07-08 → 2017-02-03 · 5 obs

○ 2015-09-24 02:39:12
● 2016-07-08 01:13:46
● 2017-02-03 17:12:12
○ 2026-03-28 14:08:36
○ 2026-08-06 18:06:40

○NSdns3.registrar-servers.com2016-07-08 → 2016-07-08 · 4 obs

○ 2015-09-24 02:39:12
● 2016-07-08 01:13:46
○ 2017-02-03 17:12:12
○ 2026-08-06 18:06:40

○NSdns4.registrar-servers.com2016-07-08 → 2016-07-08 · 4 obs

○ 2015-09-24 02:39:12
● 2016-07-08 01:13:46
○ 2017-02-03 17:12:12
○ 2026-08-06 18:06:40

○NSdns5.registrar-servers.com2016-07-08 → 2016-07-08 · 4 obs

○ 2015-09-24 02:39:12
● 2016-07-08 01:13:46
○ 2017-02-03 17:12:12
○ 2026-08-06 18:06:40

●NSns1.brandbucket.com2026-03-28 → 2026-08-06 · 3 obs

○ 2017-02-03 17:12:12
● 2026-03-28 14:08:36
● 2026-08-06 18:06:40

○NSns1.r01.ru2015-05-09 → 2015-05-09 · 3 obs

● 2015-05-09 17:43:50
○ 2015-09-24 02:39:12
○ 2026-08-06 18:06:40

●NSns2.brandbucket.com2026-03-28 → 2026-08-06 · 3 obs

○ 2017-02-03 17:12:12
● 2026-03-28 14:08:36
● 2026-08-06 18:06:40

○NSns2.r01.ru2015-05-09 → 2015-05-09 · 3 obs

● 2015-05-09 17:43:50
○ 2015-09-24 02:39:12
○ 2026-08-06 18:06:40

○MXeforward1.registrar-servers.com2016-07-08 → 2016-07-08 · 4 obs

○ 2015-09-24 02:39:12
● 2016-07-08 01:13:46
○ 2017-02-03 17:12:12
○ 2026-08-06 18:06:40

○MXeforward2.registrar-servers.com2016-07-08 → 2016-07-08 · 4 obs

○ 2015-09-24 02:39:12
● 2016-07-08 01:13:46
○ 2017-02-03 17:12:12
○ 2026-08-06 18:06:40

○MXeforward3.registrar-servers.com2016-07-08 → 2016-07-08 · 4 obs

○ 2015-09-24 02:39:12
● 2016-07-08 01:13:46
○ 2017-02-03 17:12:12
○ 2026-08-06 18:06:40

○MXeforward4.registrar-servers.com2016-07-08 → 2016-07-08 · 4 obs

○ 2015-09-24 02:39:12
● 2016-07-08 01:13:46
○ 2017-02-03 17:12:12
○ 2026-08-06 18:06:40

○MXeforward5.registrar-servers.com2016-07-08 → 2016-07-08 · 4 obs

○ 2015-09-24 02:39:12
● 2016-07-08 01:13:46
○ 2017-02-03 17:12:12
○ 2026-08-06 18:06:40

○MXmx.yandex.ru2015-05-09 → 2015-05-09 · 3 obs

● 2015-05-09 17:43:50
○ 2015-09-24 02:39:12
○ 2026-08-06 18:06:40

○MXmx.zoho.com2017-02-03 → 2017-02-03 · 4 obs

○ 2016-07-08 01:13:46
● 2017-02-03 17:12:12
○ 2026-03-28 14:08:36
○ 2026-08-06 18:06:40

○MXmx2.zoho.com2017-02-03 → 2017-02-03 · 4 obs

○ 2016-07-08 01:13:46
● 2017-02-03 17:12:12
○ 2026-03-28 14:08:36
○ 2026-08-06 18:06:40

●A13.56.33.82026-03-28 → 2026-08-06 · 3 obs

○ 2017-02-03 17:12:12
● 2026-03-28 14:08:36
● 2026-08-06 18:06:40

○A162.255.119.2492017-02-03 → 2017-02-03 · 4 obs

○ 2016-07-08 01:13:46
● 2017-02-03 17:12:12
○ 2026-03-28 14:08:36
○ 2026-08-06 18:06:40

○A162.255.119.2502016-07-08 → 2016-07-08 · 4 obs

○ 2015-09-24 02:39:12
● 2016-07-08 01:13:46
○ 2017-02-03 17:12:12
○ 2026-08-06 18:06:40

○A176.9.138.1132015-05-09 → 2015-05-09 · 3 obs

● 2015-05-09 17:43:50
○ 2015-09-24 02:39:12
○ 2026-08-06 18:06:40

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	e.gtld-servers.net, l.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net...	-
cryptorex.com	ns1.brandbucket.com, ns2.brandbucket.com	2 records

✅ Authoritative Response

Server:18.221.52.246

NS records: ns1.brandbucket.com, ns2.brandbucket.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for cryptorex.com (unsigned zone)

⏱️ Timing

Total: 189ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`13.56.33.8`
NS	2	`ns2.brandbucket.com, ns1.brandbucket.com`
TXT	3	`v=spf1 -all, afternic-verification-cvgUQU8SkLxsjXcPBS...`
SOA	1	`ns1.brandbucket.com mail.cryptorex.com`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.brandbucket.com, ns2.brandbucket.com)

Analysis

IP Addresses

cryptorex.com resolves to one IP address: 13.56.33.8.

setupsocial.com, sustaineers.com, norono.com and two other host names share IP numbers with cryptorex.com.

Name Servers

DNS delegation for cryptorex.com points to two name servers: ns1.brandbucket.com and ns2.brandbucket.com.

cryptorex.com uses the same name servers as several other domains — among them admarcom.com, seoaspect.com, exjee.com and two more.

cryptorex.com shares at least some of its name servers with other domains, such as focusphase.com and highbottle.com.

These name servers are frequently paired with the name servers verification-crni5nmdhiy5dwpuvebupt.ns101.verify.hn and verification-z5atyvddcsxaefgezfdzrc.ns101.verify.hn.

ns1.brandbucket.com directs to 54.241.53.41 and 2600:1f1c:800:8b01:2ba3:bb61:44fb:b361. ns2.brandbucket.com directs to 18.221.52.246 and 2600:1f16:54:8701:4012:7e34:5c5f:95a8. Each host name carries two IP addresses.