protocolcloud.com - dns.ninja
protocolcloud.com
| 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 | ||||||
| PTR | ec2-44-219-81-145.compute-1.amazonaws.com | ||||||
| NS | ns2.atom.com | ||||||
| A | 50.19.240.86🇺🇸 Amazon50.19.128.0/17 EC2 IAD prefix | ||||||
| PTR | ec2-50-19-240-86.compute-1.amazonaws.com | ||||||
| SOA | ns1.atom.comhostmaster@protocolcloud.com 2025-07-29 #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=1780648549 | ||||||
Same first word
protocolcloud.com |
Similar names
DNS History
8 records (3 active, 5 former)
●NSns1.atom.com2026-03-23 → 2026-06-05 · 3 obs
● 2026-03-23 23:25:00
● 2026-06-05 08:43:14
●NSns2.atom.com2026-03-23 → 2026-06-05 · 3 obs
● 2026-03-23 23:25:00
● 2026-06-05 08:43:14
○NSns51.domaincontrol.com2015-08-23 → 2019-12-30 · 4 obs
● 2019-12-30 06:27:28
○ 2026-03-23 23:25:00
○ 2026-06-05 08:43:14
○NSns52.domaincontrol.com2015-08-23 → 2019-12-30 · 4 obs
● 2019-12-30 06:27:28
○ 2026-03-23 23:25:00
○ 2026-06-05 08:43:14
○MXmail.protocolcloud.com2015-08-23 → 2015-08-23 · 3 obs
○ 2015-12-14 11:46:46
○ 2026-06-05 08:43:14
○MXprotocolcloud-com.mail.protection.outlook.com2015-12-14 → 2019-12-30 · 5 obs
● 2015-12-14 11:46:46
● 2019-12-30 06:27:28
○ 2026-03-23 23:25:00
○ 2026-06-05 08:43:14
○A165.228.145.472015-08-23 → 2019-12-30 · 4 obs
● 2019-12-30 06:27:28
○ 2026-03-23 23:25:00
○ 2026-06-05 08:43:14
●A52.20.84.622026-03-23 → 2026-06-05 · 3 obs
● 2026-03-23 23:25:00
● 2026-06-05 08:43:14
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| protocolcloud.com | ns1.atom.com, ns2.atom.com | 2 records |
✅ Authoritative Response
Server:44.219.81.145
NS records: ns1.atom.com, ns2.atom.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for protocolcloud.com (unsigned zone)
⏱️ Timing
Total: 3058ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 52.20.84.62 |
| NS | 2 | ns2.atom.com, ns1.atom.com |
| SOA | 1 | ns1.atom.com hostmaster.protocolcloud.co |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.atom.com, ns2.atom.com)
Analysis
IP Addresses
protocolcloud.com resolves to just one IP address, 52.20.84.62.
Two other host names, along with boraboraboats.com, warmte.org and qonka.com, also share IP numbers with protocolcloud.com.
Name Servers
protocolcloud.com is delegated to two name servers: ns1.atom.com and ns2.atom.com.
protocolcloud.com shares its NS records with other domains, for example xszx.com, baycentral.com, thetechbase.com and two others.
protocolcloud.com shares at least some of its name servers with other domains, such as dubaiqa.com.
Both ns1.atom.com and ns2.atom.com have a single IP address each — ns1.atom.com resolves to 44.219.81.145 while ns2.atom.com resolves to 50.19.240.86.