cryptousa.com - robtex.com
cryptousa.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 52.20.84.62🇺🇸 Amazon | ||||||
| PTR | ec2-52-20-84-62.compute-1.amazonaws.com | ||||||
| NS | ns1.atom.com ⭐ | ||||||
| A | 44.219.81.145🇺🇸 Amazon | ||||||
| PTR | ec2-44-219-81-145.compute-1.amazonaws.com | ||||||
| NS | ns2.atom.com | ||||||
| A | 50.19.240.86🇺🇸 Amazon | ||||||
| PTR | ec2-50-19-240-86.compute-1.amazonaws.com | ||||||
| TXT | f0095018235b8109a2bf9f65674a1784b6971ed6 | ||||||
| SOA | ns1.atom.comhostmaster@cryptousa.com 2025-03-07 #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.netnstld@verisign-grs.com serial=1771291435 | ||||||
Same first word
cryptousa.com |
Similar names
DNS History
14 records (3 active, 11 former)
●NSns1.atom.com2026-02-21 → 2026-02-22 · 3 obs
○ 2017-03-15 04:40:14
● 2026-02-21 10:07:22
● 2026-02-22 04:57:40
● 2026-02-21 10:07:22
● 2026-02-22 04:57:40
○NSns1.qnetau.com2008-03-09 → 2008-03-09 · 3 obs
● 2008-03-09 10:15:52
○ 2015-08-18 12:44:56
○ 2026-02-22 04:57:40
○ 2015-08-18 12:44:56
○ 2026-02-22 04:57:40
●NSns2.atom.com2026-02-21 → 2026-02-22 · 3 obs
○ 2017-03-15 04:40:14
● 2026-02-21 10:07:22
● 2026-02-22 04:57:40
● 2026-02-21 10:07:22
● 2026-02-22 04:57:40
○NSns2.qnetau.com2008-03-09 → 2008-03-09 · 3 obs
● 2008-03-09 10:15:52
○ 2015-08-18 12:44:56
○ 2026-02-22 04:57:40
○ 2015-08-18 12:44:56
○ 2026-02-22 04:57:40
○NSns25.domaincontrol.com2015-08-18 → 2015-08-18 · 4 obs
○ 2008-03-09 10:15:52
● 2015-08-18 12:44:56
○ 2015-12-10 11:18:54
○ 2026-02-22 04:57:40
● 2015-08-18 12:44:56
○ 2015-12-10 11:18:54
○ 2026-02-22 04:57:40
○NSns26.domaincontrol.com2015-08-18 → 2015-08-18 · 4 obs
○ 2008-03-09 10:15:52
● 2015-08-18 12:44:56
○ 2015-12-10 11:18:54
○ 2026-02-22 04:57:40
● 2015-08-18 12:44:56
○ 2015-12-10 11:18:54
○ 2026-02-22 04:57:40
○NSns47.domaincontrol.com2016-06-30 → 2017-03-15 · 5 obs
○ 2015-12-10 11:18:54
● 2016-06-30 00:42:12
● 2017-03-15 04:40:14
○ 2026-02-21 10:07:22
○ 2026-02-22 04:57:40
● 2016-06-30 00:42:12
● 2017-03-15 04:40:14
○ 2026-02-21 10:07:22
○ 2026-02-22 04:57:40
○NSns48.domaincontrol.com2016-06-30 → 2017-03-15 · 5 obs
○ 2015-12-10 11:18:54
● 2016-06-30 00:42:12
● 2017-03-15 04:40:14
○ 2026-02-21 10:07:22
○ 2026-02-22 04:57:40
● 2016-06-30 00:42:12
● 2017-03-15 04:40:14
○ 2026-02-21 10:07:22
○ 2026-02-22 04:57:40
○MXmailstore1.secureserver.net2015-08-18 → 2017-03-15 · 8 obs
○ 2008-03-09 10:15:52
● 2015-08-18 12:44:56
○ 2015-12-10 11:18:54
○ 2016-03-12 20:34:20
● 2016-06-30 00:42:12
● 2017-03-15 04:40:14
○ 2026-02-21 10:07:22
○ 2026-02-22 04:57:40
● 2015-08-18 12:44:56
○ 2015-12-10 11:18:54
○ 2016-03-12 20:34:20
● 2016-06-30 00:42:12
● 2017-03-15 04:40:14
○ 2026-02-21 10:07:22
○ 2026-02-22 04:57:40
○MXsmtp.secureserver.net2015-08-18 → 2017-03-15 · 8 obs
○ 2008-03-09 10:15:52
● 2015-08-18 12:44:56
○ 2015-12-10 11:18:54
○ 2016-03-12 20:34:20
● 2016-06-30 00:42:12
● 2017-03-15 04:40:14
○ 2026-02-21 10:07:22
○ 2026-02-22 04:57:40
● 2015-08-18 12:44:56
○ 2015-12-10 11:18:54
○ 2016-03-12 20:34:20
● 2016-06-30 00:42:12
● 2017-03-15 04:40:14
○ 2026-02-21 10:07:22
○ 2026-02-22 04:57:40
○A184.168.221.222017-03-15 → 2017-03-15 · 4 obs
○ 2016-06-30 00:42:12
● 2017-03-15 04:40:14
○ 2026-02-21 10:07:22
○ 2026-02-22 04:57:40
● 2017-03-15 04:40:14
○ 2026-02-21 10:07:22
○ 2026-02-22 04:57:40
○A50.63.202.342015-08-18 → 2015-08-18 · 4 obs
○ 2008-03-09 10:15:52
● 2015-08-18 12:44:56
○ 2015-12-10 11:18:54
○ 2026-02-22 04:57:40
● 2015-08-18 12:44:56
○ 2015-12-10 11:18:54
○ 2026-02-22 04:57:40
○A50.63.202.82016-06-30 → 2016-06-30 · 4 obs
○ 2015-12-10 11:18:54
● 2016-06-30 00:42:12
○ 2017-03-15 04:40:14
○ 2026-02-22 04:57:40
● 2016-06-30 00:42:12
○ 2017-03-15 04:40:14
○ 2026-02-22 04:57:40
●A52.20.84.622026-02-21 → 2026-02-22 · 3 obs
○ 2017-03-15 04:40:14
● 2026-02-21 10:07:22
● 2026-02-22 04:57:40
● 2026-02-21 10:07:22
● 2026-02-22 04:57:40
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| cryptousa.com | ns1.atom.com, ns2.atom.com | - |
✅ Authoritative Response
Server: 44.219.81.145
NS records: ns1.atom.com, ns2.atom.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for cryptousa.com (unsigned zone)
⏱️ Timing
Total: 3091ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 52.20.84.62 |
| NS | 2 | ns2.atom.com, ns1.atom.com |
| TXT | 1 | f0095018235b8109a2bf9f65674a1784b6971ed6 |
| SOA | 1 | ns1.atom.com hostmaster.cryptousa.com |
AI analysis
cryptousa.com points to a single IP address: 52.20.84.62.
Other host names such as payme.es, www.stagecrew.com, smoothdevelopment.com, relieveu.com and wishsaver.com share IP numbers with cryptousa.com.
cryptousa.com is delegated to two name servers: ns1.atom.com and ns2.atom.com.
cryptousa.com uses the same name server setup as other domains, including iscc.com, rumoc.com, zoetas.com, gaspolice.com and veristake.com.
Hostnames with a single IP
ns1.atom.com resolves to: 44.219.81.145.
ns2.atom.com resolves to: 50.19.240.86.