bagodo.com - dns.ninja
bagodo.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@bagodo.com 2026-05-16 #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=1785007797 | ||||||
Same first word
bagodo.com |
Similar names
DNS History
17 records (3 active, 14 former)
○NSdns1.namecheaphosting.com2018-07-17 → 2018-07-17 · 4 obs
○ 2016-05-10 00:46:30
● 2018-07-17 11:16:58
○ 2026-03-01 20:00:10
○ 2026-07-25 19:52:52
● 2018-07-17 11:16:58
○ 2026-03-01 20:00:10
○ 2026-07-25 19:52:52
○NSdns101.registrar-servers.com2026-03-01 → 2026-03-31 · 5 obs
○ 2018-07-17 11:16:58
● 2026-03-01 20:00:10
● 2026-03-31 12:12:00
○ 2026-05-24 16:37:36
○ 2026-07-25 19:52:52
● 2026-03-01 20:00:10
● 2026-03-31 12:12:00
○ 2026-05-24 16:37:36
○ 2026-07-25 19:52:52
○NSdns102.registrar-servers.com2026-03-01 → 2026-03-31 · 5 obs
○ 2018-07-17 11:16:58
● 2026-03-01 20:00:10
● 2026-03-31 12:12:00
○ 2026-05-24 16:37:36
○ 2026-07-25 19:52:52
● 2026-03-01 20:00:10
● 2026-03-31 12:12:00
○ 2026-05-24 16:37:36
○ 2026-07-25 19:52:52
○NSdns2.namecheaphosting.com2018-07-17 → 2018-07-17 · 4 obs
○ 2016-05-10 00:46:30
● 2018-07-17 11:16:58
○ 2026-03-01 20:00:10
○ 2026-07-25 19:52:52
● 2018-07-17 11:16:58
○ 2026-03-01 20:00:10
○ 2026-07-25 19:52:52
●NSns1.atom.com2026-05-24 → 2026-07-25 · 3 obs
○ 2026-03-31 12:12:00
● 2026-05-24 16:37:36
● 2026-07-25 19:52:52
● 2026-05-24 16:37:36
● 2026-07-25 19:52:52
●NSns2.atom.com2026-05-24 → 2026-07-25 · 3 obs
○ 2026-03-31 12:12:00
● 2026-05-24 16:37:36
● 2026-07-25 19:52:52
● 2026-05-24 16:37:36
● 2026-07-25 19:52:52
○NSns75.domaincontrol.com2015-05-20 → 2015-12-18 · 4 obs
● 2015-05-20 11:39:44
● 2015-12-18 03:49:40
○ 2016-05-10 00:46:30
○ 2026-07-25 19:52:52
● 2015-12-18 03:49:40
○ 2016-05-10 00:46:30
○ 2026-07-25 19:52:52
○NSns76.domaincontrol.com2015-05-20 → 2015-12-18 · 4 obs
● 2015-05-20 11:39:44
● 2015-12-18 03:49:40
○ 2016-05-10 00:46:30
○ 2026-07-25 19:52:52
● 2015-12-18 03:49:40
○ 2016-05-10 00:46:30
○ 2026-07-25 19:52:52
○MXmail.bagodo.com2018-07-17 → 2018-07-17 · 4 obs
○ 2016-05-10 00:46:30
● 2018-07-17 11:16:58
○ 2026-03-01 20:00:10
○ 2026-07-25 19:52:52
● 2018-07-17 11:16:58
○ 2026-03-01 20:00:10
○ 2026-07-25 19:52:52
○MXmailstore1.secureserver.net2015-05-20 → 2015-12-18 · 4 obs
● 2015-05-20 11:39:44
● 2015-12-18 03:49:40
○ 2016-05-10 00:46:30
○ 2026-07-25 19:52:52
● 2015-12-18 03:49:40
○ 2016-05-10 00:46:30
○ 2026-07-25 19:52:52
○MXmx.plingest.com2026-03-01 → 2026-03-31 · 5 obs
○ 2018-07-17 11:16:58
● 2026-03-01 20:00:10
● 2026-03-31 12:12:00
○ 2026-05-24 16:37:36
○ 2026-07-25 19:52:52
● 2026-03-01 20:00:10
● 2026-03-31 12:12:00
○ 2026-05-24 16:37:36
○ 2026-07-25 19:52:52
○MXsmtp.secureserver.net2015-05-20 → 2015-12-18 · 4 obs
● 2015-05-20 11:39:44
● 2015-12-18 03:49:40
○ 2016-05-10 00:46:30
○ 2026-07-25 19:52:52
● 2015-12-18 03:49:40
○ 2016-05-10 00:46:30
○ 2026-07-25 19:52:52
○A172.234.24.2112026-03-01 → 2026-03-31 · 5 obs
○ 2018-07-17 11:16:58
● 2026-03-01 20:00:10
● 2026-03-31 12:12:00
○ 2026-05-24 16:37:36
○ 2026-07-25 19:52:52
● 2026-03-01 20:00:10
● 2026-03-31 12:12:00
○ 2026-05-24 16:37:36
○ 2026-07-25 19:52:52
○A172.239.57.1172026-03-01 → 2026-03-31 · 5 obs
○ 2018-07-17 11:16:58
● 2026-03-01 20:00:10
● 2026-03-31 12:12:00
○ 2026-05-24 16:37:36
○ 2026-07-25 19:52:52
● 2026-03-01 20:00:10
● 2026-03-31 12:12:00
○ 2026-05-24 16:37:36
○ 2026-07-25 19:52:52
○A184.168.221.502015-05-20 → 2015-12-18 · 4 obs
● 2015-05-20 11:39:44
● 2015-12-18 03:49:40
○ 2016-05-10 00:46:30
○ 2026-07-25 19:52:52
● 2015-12-18 03:49:40
○ 2016-05-10 00:46:30
○ 2026-07-25 19:52:52
○A198.54.126.1442018-07-17 → 2018-07-17 · 4 obs
○ 2016-05-10 00:46:30
● 2018-07-17 11:16:58
○ 2026-03-01 20:00:10
○ 2026-07-25 19:52:52
● 2018-07-17 11:16:58
○ 2026-03-01 20:00:10
○ 2026-07-25 19:52:52
●A52.20.84.622026-05-24 → 2026-07-25 · 3 obs
○ 2026-03-31 12:12:00
● 2026-05-24 16:37:36
● 2026-07-25 19:52:52
● 2026-05-24 16:37:36
● 2026-07-25 19:52:52
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| bagodo.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 bagodo.com (unsigned zone)
⏱️ Timing
Total: 3089ms | 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.bagodo.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.atom.com, ns2.atom.com)
Analysis
IP Addresses
bagodo.com resolves to one IP address: 52.20.84.62.
100fm.com, zrevo.com, stealthmark.com and two other host names share IP numbers with bagodo.com.
Name Servers
The NS records for bagodo.com delegate to ns1.atom.com and ns2.atom.com.
bagodo.com uses the same name servers as several other domains — among them roboelec.com, gemdream.com, owwi.com and two more.
Some of bagodo.com's name servers are also used by other domains, including rushzoo.com, elzozo.info, tinybell.com and tunden.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.