bearops.com - dns.ninja
bearops.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@bearops.com 2025-02-07 #4 | ||||||
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=1780582084 | ||||||
Same first word
bearops.com |
Similar names
DNS History
31 records (3 active, 28 former)
●NSns1.atom.com2026-02-27 → 2026-06-04 · 3 obs
● 2026-02-27 07:22:40
● 2026-06-04 14:13:28
○NSns1.meganameservers.com2007-11-15 → 2007-11-15 · 3 obs
○ 2015-05-29 19:43:24
○ 2026-06-04 14:13:28
○NSns1.namebrightdns.com2015-10-29 → 2016-09-19 · 7 obs
● 2015-10-29 09:29:36
○ 2016-01-18 16:53:52
● 2016-04-10 05:10:02
● 2016-09-19 09:29:16
○ 2026-02-27 07:22:40
○ 2026-06-04 14:13:28
●NSns2.atom.com2026-02-27 → 2026-06-04 · 3 obs
● 2026-02-27 07:22:40
● 2026-06-04 14:13:28
○NSns2.meganameservers.com2007-11-15 → 2007-11-15 · 3 obs
○ 2015-05-29 19:43:24
○ 2026-06-04 14:13:28
○NSns2.namebrightdns.com2015-10-29 → 2016-09-19 · 7 obs
● 2015-10-29 09:29:36
○ 2016-01-18 16:53:52
● 2016-04-10 05:10:02
● 2016-09-19 09:29:16
○ 2026-02-27 07:22:40
○ 2026-06-04 14:13:28
○NSns3.meganameservers.com2007-11-15 → 2007-11-15 · 3 obs
○ 2015-05-29 19:43:24
○ 2026-06-04 14:13:28
○NSns49.domaincontrol.com2015-05-29 → 2015-05-29 · 4 obs
● 2015-05-29 19:43:24
○ 2015-10-29 09:29:36
○ 2026-06-04 14:13:28
○NSns50.domaincontrol.com2015-05-29 → 2015-05-29 · 4 obs
● 2015-05-29 19:43:24
○ 2015-10-29 09:29:36
○ 2026-06-04 14:13:28
○NSnsg1.namebrightdns.com2016-01-18 → 2016-01-18 · 4 obs
● 2016-01-18 16:53:52
○ 2016-04-10 05:10:02
○ 2026-06-04 14:13:28
○NSnsg2.namebrightdns.com2016-01-18 → 2016-01-18 · 4 obs
● 2016-01-18 16:53:52
○ 2016-04-10 05:10:02
○ 2026-06-04 14:13:28
○MXmailstore1.secureserver.net2015-05-29 → 2015-05-29 · 4 obs
● 2015-05-29 19:43:24
○ 2015-10-29 09:29:36
○ 2026-06-04 14:13:28
○MXmx1.megamailservers.com2007-11-15 → 2007-11-15 · 3 obs
○ 2015-05-29 19:43:24
○ 2026-06-04 14:13:28
○MXmx2.megamailservers.com2007-11-15 → 2007-11-15 · 3 obs
○ 2015-05-29 19:43:24
○ 2026-06-04 14:13:28
○MXmx3.megamailservers.com2007-11-15 → 2007-11-15 · 3 obs
○ 2015-05-29 19:43:24
○ 2026-06-04 14:13:28
○MXsmtp.secureserver.net2015-05-29 → 2015-05-29 · 4 obs
● 2015-05-29 19:43:24
○ 2015-10-29 09:29:36
○ 2026-06-04 14:13:28
○A107.23.198.2402016-09-19 → 2016-09-19 · 4 obs
● 2016-09-19 09:29:16
○ 2026-02-27 07:22:40
○ 2026-06-04 14:13:28
○A216.251.43.112007-11-15 → 2007-11-15 · 3 obs
○ 2015-05-29 19:43:24
○ 2026-06-04 14:13:28
○A50.63.202.602015-05-29 → 2015-05-29 · 4 obs
● 2015-05-29 19:43:24
○ 2015-10-29 09:29:36
○ 2026-06-04 14:13:28
●A52.20.84.622026-02-27 → 2026-06-04 · 3 obs
● 2026-02-27 07:22:40
● 2026-06-04 14:13:28
○A52.200.243.1232016-04-10 → 2016-04-10 · 4 obs
● 2016-04-10 05:10:02
○ 2016-09-19 09:29:16
○ 2026-06-04 14:13:28
○A52.206.43.2342016-09-19 → 2016-09-19 · 4 obs
● 2016-09-19 09:29:16
○ 2026-02-27 07:22:40
○ 2026-06-04 14:13:28
○A52.21.52.1092016-01-18 → 2016-01-18 · 4 obs
● 2016-01-18 16:53:52
○ 2016-04-10 05:10:02
○ 2026-06-04 14:13:28
○A52.4.72.1372016-09-19 → 2016-09-19 · 4 obs
● 2016-09-19 09:29:16
○ 2026-02-27 07:22:40
○ 2026-06-04 14:13:28
○A54.152.144.2432016-04-10 → 2016-04-10 · 4 obs
● 2016-04-10 05:10:02
○ 2016-09-19 09:29:16
○ 2026-06-04 14:13:28
○A54.174.31.2542015-10-29 → 2015-10-29 · 4 obs
● 2015-10-29 09:29:36
○ 2016-01-18 16:53:52
○ 2026-06-04 14:13:28
○A54.208.74.2152015-10-29 → 2015-10-29 · 4 obs
● 2015-10-29 09:29:36
○ 2016-01-18 16:53:52
○ 2026-06-04 14:13:28
○A54.209.174.1672016-01-18 → 2016-01-18 · 4 obs
● 2016-01-18 16:53:52
○ 2016-04-10 05:10:02
○ 2026-06-04 14:13:28
○A54.210.33.1902016-09-19 → 2016-09-19 · 4 obs
● 2016-09-19 09:29:16
○ 2026-02-27 07:22:40
○ 2026-06-04 14:13:28
○A54.236.123.2242016-09-19 → 2016-09-19 · 4 obs
● 2016-09-19 09:29:16
○ 2026-02-27 07:22:40
○ 2026-06-04 14:13:28
○CNAMEhdredirect-lb-399551664.us-east-1.elb.amazonaws.com2015-10-29 → 2016-09-19 · 4 obs
● 2016-09-19 09:29:16
○ 2026-02-27 07:22:40
○ 2026-06-04 14:13:28
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| bearops.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 bearops.com (unsigned zone)
⏱️ Timing
Total: 4671ms | 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.bearops.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.atom.com, ns2.atom.com)
Analysis
IP Addresses
bearops.com points to a single IP number: 52.20.84.62.
Additional host names — blancafe.com, finestbot.com, oasor.com and two others — share IP numbers with bearops.com.
Name Servers
bearops.com has two authoritative name servers — ns1.atom.com and ns2.atom.com.
bearops.com shares its name server setup with other domains, including koblu.com, mixgem.com, cashcor.com and two others.
bearops.com at least partially shares name servers with other domains, for instance careerform.com, xinsel.com and cubesi.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.