badgerloop.com - robtex.com
badgerloop.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 139.59.225.255🇸🇬 DIGITALOCEAN139.59.224.0/20 DigitalOcean | ||||||
| NS | ns1-07.azure-dns.com ⭐ | ||||||
| A | 2603:1061:0:700::7🇺🇸 Microsoft2603:1000::/25 MICROSOFT | ||||||
| PTR | ns1-07.azure-dns.com | ||||||
| A | 13.107.236.7🇺🇸 Microsoft13.104.0.0/14 MICROSOFT | ||||||
| PTR | ns1-07.azure-dns.com | ||||||
| NS | ns2-07.azure-dns.net | ||||||
| A | 2620:1ec:8ec:700::7🇺🇸 Microsoft2620:1ec::/36 MICROSOFT | ||||||
| PTR | ns2-07.azure-dns.net | ||||||
| A | 150.171.21.7🇺🇸 Microsoft150.171.0.0/16 MICROSOFT | ||||||
| PTR | ns2-07.azure-dns.net | ||||||
| NS | ns3-07.azure-dns.org | ||||||
| A | 2a01:111:4000:700::7🇬🇧 Microsoft2a01:111:4000::/36 | ||||||
| PTR | ns3-07.azure-dns.org | ||||||
| A | 204.14.183.7🇺🇸 Microsoft204.14.180.0/22 | ||||||
| PTR | ns3-07.azure-dns.org | ||||||
| NS | ns4-07.azure-dns.info | ||||||
| A | 2620:1ec:bda:700::7🇺🇸 Microsoft2620:1ec::/36 MICROSOFT | ||||||
| PTR | ns4-07.azure-dns.info | ||||||
| A | 208.84.5.7🇺🇸 Microsoft208.84.0.0/21 MICROSOFT | ||||||
| PTR | ns4-07.azure-dns.info | ||||||
| SOA | ns1-07.azure-dns.comazuredns-hostmaster@microsoft.com serial=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=1784168277 | ||||||
Same first word
badgerloop.com |
DNS History
19 records (5 active, 14 former)
○NSns-1366.awsdns-42.org2016-04-15 → 2017-10-18 · 5 obs
● 2016-04-15 01:02:42
● 2017-10-18 05:32:14
○ 2026-04-07 01:43:54
○ 2026-07-16 02:36:38
○NSns-2019.awsdns-60.co.uk2016-04-15 → 2017-10-18 · 5 obs
● 2016-04-15 01:02:42
● 2017-10-18 05:32:14
○ 2026-04-07 01:43:54
○ 2026-07-16 02:36:38
○NSns-246.awsdns-30.com2016-04-15 → 2017-10-18 · 5 obs
● 2016-04-15 01:02:42
● 2017-10-18 05:32:14
○ 2026-04-07 01:43:54
○ 2026-07-16 02:36:38
○NSns-992.awsdns-60.net2016-04-15 → 2017-10-18 · 5 obs
● 2016-04-15 01:02:42
● 2017-10-18 05:32:14
○ 2026-04-07 01:43:54
○ 2026-07-16 02:36:38
●NSns1-07.azure-dns.com2026-04-07 → 2026-07-16 · 3 obs
● 2026-04-07 01:43:54
● 2026-07-16 02:36:38
●NSns2-07.azure-dns.net2026-04-07 → 2026-07-16 · 3 obs
● 2026-04-07 01:43:54
● 2026-07-16 02:36:38
●NSns3-07.azure-dns.org2026-04-07 → 2026-07-16 · 3 obs
● 2026-04-07 01:43:54
● 2026-07-16 02:36:38
●NSns4-07.azure-dns.info2026-04-07 → 2026-07-16 · 3 obs
● 2026-04-07 01:43:54
● 2026-07-16 02:36:38
○NSns71.domaincontrol.com2015-10-22 → 2016-01-04 · 4 obs
● 2016-01-04 03:49:08
○ 2016-04-15 01:02:42
○ 2026-07-16 02:36:38
○NSns72.domaincontrol.com2015-10-22 → 2016-01-04 · 4 obs
● 2016-01-04 03:49:08
○ 2016-04-15 01:02:42
○ 2026-07-16 02:36:38
○MXinbound-smtp.us-east-1.amazonaws.com2016-04-15 → 2017-01-08 · 5 obs
● 2016-04-15 01:02:42
● 2017-01-08 04:15:46
○ 2017-05-19 11:25:54
○ 2026-07-16 02:36:38
○MXmailstore1.secureserver.net2015-10-22 → 2016-01-04 · 4 obs
● 2016-01-04 03:49:08
○ 2016-04-15 01:02:42
○ 2026-07-16 02:36:38
○MXsmtp.secureserver.net2015-10-22 → 2016-01-04 · 4 obs
● 2016-01-04 03:49:08
○ 2016-04-15 01:02:42
○ 2026-07-16 02:36:38
○A107.180.47.132016-11-06 → 2017-01-08 · 5 obs
● 2016-11-06 08:23:16
● 2017-01-08 04:15:46
○ 2017-05-19 11:25:54
○ 2026-07-16 02:36:38
●A139.59.225.2552026-06-12 → 2026-07-16 · 3 obs
● 2026-06-12 02:07:58
● 2026-07-16 02:36:38
○A23.229.135.1032015-10-22 → 2016-04-15 · 4 obs
● 2016-04-15 01:02:42
○ 2016-11-06 08:23:16
○ 2026-07-16 02:36:38
○A34.208.17.1402017-07-06 → 2017-08-27 · 5 obs
● 2017-07-06 20:27:34
● 2017-08-27 19:58:28
○ 2017-10-18 05:32:14
○ 2026-07-16 02:36:38
○A54.68.65.1352017-10-18 → 2017-10-18 · 4 obs
● 2017-10-18 05:32:14
○ 2026-04-07 01:43:54
○ 2026-07-16 02:36:38
○A96.42.32.192017-05-19 → 2017-06-26 · 5 obs
● 2017-05-19 11:25:54
● 2017-06-26 11:50:42
○ 2017-07-06 20:27:34
○ 2026-07-16 02:36:38
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| badgerloop.com | ns1-07.azure-dns.com, ns2-07.azure-dns.net, ns3-07.azure-dns.org, ns4-07.azure-dns.info | 2 records |
✅ Authoritative Response
Server:150.171.21.7
NS records: ns1-07.azure-dns.com, ns2-07.azure-dns.net, ns3-07.azure-dns.org, ns4-07.azure-dns.info
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for badgerloop.com (unsigned zone)
⏱️ Timing
Total: 307ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 139.59.225.255 |
| NS | 4 | ns1-07.azure-dns.com, ns2-07.azure-dns.net... |
| SOA | 1 | ns1-07.azure-dns.com azuredns-hostmaster |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1-07.azure-dns.com, ns1-07.azure-dns.com)
Analysis
IP Addresses
badgerloop.com resolves to just one IP address, 139.59.225.255.
Two other host names, along with astra.net, cashsearchusa.com and powershell.no, also share IP numbers with badgerloop.com.
Name Servers
The NS records for badgerloop.com point to four name servers: ns1-07.azure-dns.com, ns4-07.azure-dns.info, ns2-07.azure-dns.net and ns3-07.azure-dns.org.
badgerloop.com has at least partial name server overlap with other domains, such as pepinieremicrosoft.net, omegawatch.net, bef.bio and two others.
ns1-07.azure-dns.com, ns4-07.azure-dns.info, ns2-07.azure-dns.net and ns3-07.azure-dns.org all point to exactly two IP numbers each: ns1-07.azure-dns.com → 13.107.236.7 and 2603:1061:0:700::7; ns4-07.azure-dns.info → 208.84.5.7 and 2620:1ec:bda:700::7; ns2-07.azure-dns.net → 150.171.21.7 and 2620:1ec:8ec:700::7; ns3-07.azure-dns.org → 204.14.183.7 and 2a01:111:4000:700::7.