proloud.com - dns.ninja
proloud.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@proloud.com 2024-08-26 #3 | ||||||
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=1785486712 | ||||||
Same first word
Similar names
proludo.com |
loudpro.com |
produlo.com |
rodoplu.org |
proludo.ch |
proludo.de |
proludo.in |
drupool.com |
duropol.com |
rodoplu.com.tr |
ludopro.com |
orupold.net |
rodoplu.net |
duropol.de |
oldpour.com |
DNS History
17 records (3 active, 14 former)
●NSns1.atom.com2026-03-31 → 2026-07-31 · 3 obs
○ 2016-11-22 15:24:26
● 2026-03-31 01:11:44
● 2026-07-31 09:00:22
● 2026-03-31 01:11:44
● 2026-07-31 09:00:22
○NSns1.namebrightdns.com2015-08-22 → 2016-11-22 · 6 obs
● 2015-08-22 22:07:00
● 2016-02-20 23:52:20
○ 2016-05-05 15:43:18
● 2016-11-22 15:24:26
○ 2026-03-31 01:11:44
○ 2026-07-31 09:00:22
● 2016-02-20 23:52:20
○ 2016-05-05 15:43:18
● 2016-11-22 15:24:26
○ 2026-03-31 01:11:44
○ 2026-07-31 09:00:22
●NSns2.atom.com2026-03-31 → 2026-07-31 · 3 obs
○ 2016-11-22 15:24:26
● 2026-03-31 01:11:44
● 2026-07-31 09:00:22
● 2026-03-31 01:11:44
● 2026-07-31 09:00:22
○NSns2.namebrightdns.com2015-08-22 → 2016-11-22 · 6 obs
● 2015-08-22 22:07:00
● 2016-02-20 23:52:20
○ 2016-05-05 15:43:18
● 2016-11-22 15:24:26
○ 2026-03-31 01:11:44
○ 2026-07-31 09:00:22
● 2016-02-20 23:52:20
○ 2016-05-05 15:43:18
● 2016-11-22 15:24:26
○ 2026-03-31 01:11:44
○ 2026-07-31 09:00:22
○NSnsg1.namebrightdns.com2015-08-22 → 2016-05-05 · 6 obs
● 2015-08-22 22:07:00
○ 2015-11-19 10:56:10
○ 2016-02-20 23:52:20
● 2016-05-05 15:43:18
○ 2016-11-22 15:24:26
○ 2026-07-31 09:00:22
○ 2015-11-19 10:56:10
○ 2016-02-20 23:52:20
● 2016-05-05 15:43:18
○ 2016-11-22 15:24:26
○ 2026-07-31 09:00:22
○NSnsg2.namebrightdns.com2016-05-05 → 2016-05-05 · 4 obs
○ 2016-02-20 23:52:20
● 2016-05-05 15:43:18
○ 2016-11-22 15:24:26
○ 2026-07-31 09:00:22
● 2016-05-05 15:43:18
○ 2016-11-22 15:24:26
○ 2026-07-31 09:00:22
○A52.0.96.242016-02-20 → 2016-02-20 · 4 obs
○ 2015-11-19 10:56:10
● 2016-02-20 23:52:20
○ 2016-05-05 15:43:18
○ 2026-07-31 09:00:22
● 2016-02-20 23:52:20
○ 2016-05-05 15:43:18
○ 2026-07-31 09:00:22
●A52.20.84.622026-03-31 → 2026-07-31 · 3 obs
○ 2016-11-22 15:24:26
● 2026-03-31 01:11:44
● 2026-07-31 09:00:22
● 2026-03-31 01:11:44
● 2026-07-31 09:00:22
○A52.200.243.1232016-05-05 → 2016-05-05 · 4 obs
○ 2016-02-20 23:52:20
● 2016-05-05 15:43:18
○ 2016-11-22 15:24:26
○ 2026-07-31 09:00:22
● 2016-05-05 15:43:18
○ 2016-11-22 15:24:26
○ 2026-07-31 09:00:22
○A52.5.157.2202016-11-22 → 2016-11-22 · 4 obs
○ 2016-05-05 15:43:18
● 2016-11-22 15:24:26
○ 2026-03-31 01:11:44
○ 2026-07-31 09:00:22
● 2016-11-22 15:24:26
○ 2026-03-31 01:11:44
○ 2026-07-31 09:00:22
○A52.71.117.992016-02-20 → 2016-02-20 · 4 obs
○ 2015-11-19 10:56:10
● 2016-02-20 23:52:20
○ 2016-05-05 15:43:18
○ 2026-07-31 09:00:22
● 2016-02-20 23:52:20
○ 2016-05-05 15:43:18
○ 2026-07-31 09:00:22
○A54.152.144.2432016-05-05 → 2016-05-05 · 4 obs
○ 2016-02-20 23:52:20
● 2016-05-05 15:43:18
○ 2016-11-22 15:24:26
○ 2026-07-31 09:00:22
● 2016-05-05 15:43:18
○ 2016-11-22 15:24:26
○ 2026-07-31 09:00:22
○A54.174.31.2542015-08-22 → 2015-11-19 · 4 obs
● 2015-08-22 22:07:00
● 2015-11-19 10:56:10
○ 2016-02-20 23:52:20
○ 2026-07-31 09:00:22
● 2015-11-19 10:56:10
○ 2016-02-20 23:52:20
○ 2026-07-31 09:00:22
○A54.208.74.2152015-08-22 → 2015-11-19 · 4 obs
● 2015-08-22 22:07:00
● 2015-11-19 10:56:10
○ 2016-02-20 23:52:20
○ 2026-07-31 09:00:22
● 2015-11-19 10:56:10
○ 2016-02-20 23:52:20
○ 2026-07-31 09:00:22
○A54.84.53.382016-11-22 → 2016-11-22 · 4 obs
○ 2016-05-05 15:43:18
● 2016-11-22 15:24:26
○ 2026-03-31 01:11:44
○ 2026-07-31 09:00:22
● 2016-11-22 15:24:26
○ 2026-03-31 01:11:44
○ 2026-07-31 09:00:22
○CNAMEhdredirect-lb-399551664.us-east-1.elb.amazonaws.com2015-08-22 → 2016-05-05 · 4 obs
● 2015-08-22 22:07:00
● 2016-05-05 15:43:18
○ 2016-11-22 15:24:26
○ 2026-07-31 09:00:22
● 2016-05-05 15:43:18
○ 2016-11-22 15:24:26
○ 2026-07-31 09:00:22
○CNAMEhdredirect-lb3-890977680.us-east-1.elb.amazonaws.com2016-11-22 → 2016-11-22 · 4 obs
○ 2016-05-05 15:43:18
● 2016-11-22 15:24:26
○ 2026-03-31 01:11:44
○ 2026-07-31 09:00:22
● 2016-11-22 15:24:26
○ 2026-03-31 01:11:44
○ 2026-07-31 09:00:22
🔍 DNS Trace
Analysis
IP Addresses
proloud.com resolves to just one IP address, 52.20.84.62.
Two other host names, along with e(0x6469636b).com, actionjump.com and cognitiveai.tech, also share IP numbers with proloud.com.
Name Servers
proloud.com is served by two delegated name servers, ns1.atom.com and ns2.atom.com.
proloud.com shares its NS records with other domains, for example zoixa.com, luliq.com, valuelounge.com and two others.
The DNS delegation for proloud.com at least partly coincides with that of other domains, nassym.com being one example.
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.