piggycloud.com - robtex.com
piggycloud.com
| DNSSEC | ⚠️ Not signed | ||||||
| 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@piggycloud.com 2025-05-15 #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=1776003327 | ||||||
Same first word
piggycloud.com |
Similar names
DNS History
19 records (2 active, 17 former)
○NSns09.domaincontrol.com2016-03-31 → 2016-03-31 · 4 obs
○ 2015-12-14 23:04:48
● 2016-03-31 09:35:26
○ 2016-09-22 16:55:40
○ 2026-04-12 14:19:44
● 2016-03-31 09:35:26
○ 2016-09-22 16:55:40
○ 2026-04-12 14:19:44
○NSns1.above.com2017-11-19 → 2017-11-19 · 4 obs
○ 2016-09-22 16:55:40
● 2017-11-19 18:13:12
○ 2026-02-27 01:42:38
○ 2026-04-12 14:19:44
● 2017-11-19 18:13:12
○ 2026-02-27 01:42:38
○ 2026-04-12 14:19:44
●NSns1.atom.com2026-02-27 → 2026-04-12 · 3 obs
○ 2017-11-19 18:13:12
● 2026-02-27 01:42:38
● 2026-04-12 14:19:44
● 2026-02-27 01:42:38
● 2026-04-12 14:19:44
○NSns1.sedoparking.com2016-09-22 → 2016-09-22 · 4 obs
○ 2016-03-31 09:35:26
● 2016-09-22 16:55:40
○ 2017-11-19 18:13:12
○ 2026-04-12 14:19:44
● 2016-09-22 16:55:40
○ 2017-11-19 18:13:12
○ 2026-04-12 14:19:44
○NSns10.domaincontrol.com2016-03-31 → 2016-03-31 · 4 obs
○ 2015-12-14 23:04:48
● 2016-03-31 09:35:26
○ 2016-09-22 16:55:40
○ 2026-04-12 14:19:44
● 2016-03-31 09:35:26
○ 2016-09-22 16:55:40
○ 2026-04-12 14:19:44
○NSns2.above.com2017-11-19 → 2017-11-19 · 4 obs
○ 2016-09-22 16:55:40
● 2017-11-19 18:13:12
○ 2026-02-27 01:42:38
○ 2026-04-12 14:19:44
● 2017-11-19 18:13:12
○ 2026-02-27 01:42:38
○ 2026-04-12 14:19:44
●NSns2.atom.com2026-02-27 → 2026-04-12 · 3 obs
○ 2017-11-19 18:13:12
● 2026-02-27 01:42:38
● 2026-04-12 14:19:44
● 2026-02-27 01:42:38
● 2026-04-12 14:19:44
○NSns2.sedoparking.com2016-09-22 → 2016-09-22 · 4 obs
○ 2016-03-31 09:35:26
● 2016-09-22 16:55:40
○ 2017-11-19 18:13:12
○ 2026-04-12 14:19:44
● 2016-09-22 16:55:40
○ 2017-11-19 18:13:12
○ 2026-04-12 14:19:44
○NSns57.domaincontrol.com2015-12-14 → 2015-12-14 · 3 obs
● 2015-12-14 23:04:48
○ 2016-03-31 09:35:26
○ 2026-04-12 14:19:44
○ 2016-03-31 09:35:26
○ 2026-04-12 14:19:44
○NSns58.domaincontrol.com2015-12-14 → 2015-12-14 · 3 obs
● 2015-12-14 23:04:48
○ 2016-03-31 09:35:26
○ 2026-04-12 14:19:44
○ 2016-03-31 09:35:26
○ 2026-04-12 14:19:44
○MXlocalhost2016-09-22 → 2016-09-22 · 4 obs
○ 2016-03-31 09:35:26
● 2016-09-22 16:55:40
○ 2017-11-19 18:13:12
○ 2026-04-12 14:19:44
● 2016-09-22 16:55:40
○ 2017-11-19 18:13:12
○ 2026-04-12 14:19:44
○MXmailstore1.secureserver.net2015-12-14 → 2016-03-31 · 4 obs
● 2015-12-14 23:04:48
● 2016-03-31 09:35:26
○ 2016-09-22 16:55:40
○ 2026-04-12 14:19:44
● 2016-03-31 09:35:26
○ 2016-09-22 16:55:40
○ 2026-04-12 14:19:44
○MXmx92.m1bp.com2017-11-19 → 2017-11-19 · 4 obs
○ 2016-09-22 16:55:40
● 2017-11-19 18:13:12
○ 2026-02-27 01:42:38
○ 2026-04-12 14:19:44
● 2017-11-19 18:13:12
○ 2026-02-27 01:42:38
○ 2026-04-12 14:19:44
○MXmx92.mb5p.com2017-11-19 → 2017-11-19 · 4 obs
○ 2016-09-22 16:55:40
● 2017-11-19 18:13:12
○ 2026-02-27 01:42:38
○ 2026-04-12 14:19:44
● 2017-11-19 18:13:12
○ 2026-02-27 01:42:38
○ 2026-04-12 14:19:44
○MXsmtp.secureserver.net2015-12-14 → 2016-03-31 · 4 obs
● 2015-12-14 23:04:48
● 2016-03-31 09:35:26
○ 2016-09-22 16:55:40
○ 2026-04-12 14:19:44
● 2016-03-31 09:35:26
○ 2016-09-22 16:55:40
○ 2026-04-12 14:19:44
○A103.224.182.2442017-11-19 → 2017-11-19 · 4 obs
○ 2016-09-22 16:55:40
● 2017-11-19 18:13:12
○ 2026-02-27 01:42:38
○ 2026-04-12 14:19:44
● 2017-11-19 18:13:12
○ 2026-02-27 01:42:38
○ 2026-04-12 14:19:44
○A184.168.221.532016-03-31 → 2016-03-31 · 4 obs
○ 2015-12-14 23:04:48
● 2016-03-31 09:35:26
○ 2016-09-22 16:55:40
○ 2026-04-12 14:19:44
● 2016-03-31 09:35:26
○ 2016-09-22 16:55:40
○ 2026-04-12 14:19:44
○A50.63.202.572015-12-14 → 2015-12-14 · 3 obs
● 2015-12-14 23:04:48
○ 2016-03-31 09:35:26
○ 2026-04-12 14:19:44
○ 2016-03-31 09:35:26
○ 2026-04-12 14:19:44
○A72.52.4.1192016-09-22 → 2016-09-22 · 4 obs
○ 2016-03-31 09:35:26
● 2016-09-22 16:55:40
○ 2017-11-19 18:13:12
○ 2026-04-12 14:19:44
● 2016-09-22 16:55:40
○ 2017-11-19 18:13:12
○ 2026-04-12 14:19:44
🔍 DNS Trace
Analysis
Name Servers
piggycloud.com's delegation uses two name servers, ns1.atom.com and ns2.atom.com.
piggycloud.com shares the same name server setup as other domains, for example readkick.com, datavale.com, forwardcleaning.com, optipic.com and miamialerts.com.
piggycloud.com at least partially shares name servers with other domains; for instance fomo.net.
These name servers are often used together with verification-yhehuhyrvixzqbtydgzisf.ns101.verify.hn.
Host names with a single IP:
ns1.atom.com points to 44.219.81.145.
ns2.atom.com points to 50.19.240.86.