could.name - robtex.com
could.name
| DNSSEC | ⚠️ Not signed | ||||||
| A | 52.20.84.62🇺🇸 Amazon52.20.0.0/14 EC2 IAD prefix | ||||||
| PTR | ec2-52-20-84-62.compute-1.amazonaws.com | ||||||
| NS | ns1.atom.com ⭐ | ||||||
| A | 44.219.81.145🇺🇸 Amazon44.192.0.0/11 EC2 IAD prefix | ||||||
| NS | ns2.atom.com | ||||||
| A | 50.19.240.86🇺🇸 Amazon50.19.128.0/17 EC2 IAD prefix | ||||||
| SOA | ns1.atom.comhostmaster@could.name 2026-09-29 #1 | ||||||
name
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ac1.nstld.com ⭐ | ||||||
| NS | ac2.nstld.com | ||||||
| NS | ac3.nstld.com | ||||||
| NS | ac4.nstld.com | ||||||
| SOA | ac1.nstld.cominfo@verisign-grs.com serial=1792580625 | ||||||
Same first word
Similar names
Previous names
Next names
DNS History
9 records (3 active, 6 former)
●NSns1.atom.com2026-10-09 → 2026-10-21 · 3 obs
● 2026-10-09 17:13:34
● 2026-10-21 11:25:46
○NSns10.uadns.com2016-06-21 → 2017-03-19 · 4 obs
● 2017-03-19 11:46:42
○ 2020-01-28 11:45:56
○ 2026-10-21 11:25:46
○NSns11.uadns.com2016-06-21 → 2017-03-19 · 4 obs
● 2017-03-19 11:46:42
○ 2020-01-28 11:45:56
○ 2026-10-21 11:25:46
○NSns12.uadns.com2016-06-21 → 2017-03-19 · 4 obs
● 2017-03-19 11:46:42
○ 2020-01-28 11:45:56
○ 2026-10-21 11:25:46
●NSns2.atom.com2026-10-09 → 2026-10-21 · 3 obs
● 2026-10-09 17:13:34
● 2026-10-21 11:25:46
○MXmail.could.name2016-06-21 → 2017-03-19 · 4 obs
● 2017-03-19 11:46:42
○ 2020-01-28 11:45:56
○ 2026-10-21 11:25:46
○A185.104.45.272016-06-21 → 2016-06-21 · 3 obs
○ 2017-03-19 11:46:42
○ 2026-10-21 11:25:46
○A185.65.244.172017-03-19 → 2017-03-19 · 4 obs
● 2017-03-19 11:46:42
○ 2020-01-28 11:45:56
○ 2026-10-21 11:25:46
●A52.20.84.622026-10-09 → 2026-10-21 · 3 obs
● 2026-10-09 17:13:34
● 2026-10-21 11:25:46
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| name | ac3.nstld.com, ac2.nstld.com, ac1.nstld.com, ac4.nstld.com | 8 records |
| could.name | ns2.atom.com, ns1.atom.com | - |
✅ Authoritative Response
Server:50.19.240.86
NS records: ns2.atom.com, ns1.atom.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for could.name (unsigned zone)
⏱️ Timing
Total: 1431ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 52.20.84.62 |
| NS | 2 | ns1.atom.com, ns2.atom.com |
| SOA | 1 | ns1.atom.com hostmaster.could.name |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ac4.nstld.com, ac3.nstld.com, ac2.nstld.com...)
Analysis
IP Addresses
could.name points to a single IP number: 52.20.84.62.
Additional host names — maxdrip.com, other-service.net, funu.ai and two others — share IP numbers with could.name.
Name Servers
DNS delegation for could.name points to two name servers: ns1.atom.com and ns2.atom.com.
could.name shares its name server setup with other domains, including ascribe.ca, hyperorchestration.com, carista.net and two others.
could.name at least partially shares name servers with other domains, for instance openeyz.com, mythosneo.com and beautycaffe.com.
ns1.atom.com resolves to 44.219.81.145. ns2.atom.com resolves to 50.19.240.86. Both host names point to a single IP number.