bitsr.us - dns.ninja
bitsr.us
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.digitalocean.com ⭐ | ||||||
| A | 2606:4700:52::ac40:34d2🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns1.digitalocean.com | ||||||
| A | 172.64.52.210🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns1.digitalocean.com | ||||||
| NS | ns2.digitalocean.com | ||||||
| A | 2606:4700:5a::ac40:3515🇺🇸 Cloudflare2606:4700:5a::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns2.digitalocean.com | ||||||
| A | 172.64.53.21🇺🇸 Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns2.digitalocean.com | ||||||
| NS | ns3.digitalocean.com | ||||||
| A | 2606:4700:52::ac40:31d1🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns3.digitalocean.com | ||||||
| A | 172.64.49.209🇺🇸 Cloudflare172.64.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns3.digitalocean.com | ||||||
| SOA | ns1.digitalocean.comhostmaster@bitsr.us serial=0 | ||||||
us
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.cctld.us ⭐ | ||||||
| NS | b.cctld.us | ||||||
| NS | f.cctld.us | ||||||
| NS | k.cctld.us | ||||||
| NS | m.cctld.us | ||||||
| NS | n.cctld.us | ||||||
| NS | w.cctld.us | ||||||
| NS | x.cctld.us | ||||||
| NS | y.cctld.us | ||||||
| SOA | a.cctld.usadmin@tldns.godaddy serial=1782453952 | ||||||
Previously MX for
bitsr.us |
Same first word
bitsr.us |
Similar names
DNS History
19 records (3 active, 16 former)
○NSdns1.registrar-servers.com2015-08-19 → 2016-03-21 · 4 obs
● 2016-03-21 12:55:16
○ 2017-01-19 04:48:44
○ 2026-06-26 06:38:44
○NSdns2.registrar-servers.com2015-08-19 → 2016-03-21 · 4 obs
● 2016-03-21 12:55:16
○ 2017-01-19 04:48:44
○ 2026-06-26 06:38:44
○NSdns3.registrar-servers.com2015-08-19 → 2016-03-21 · 4 obs
● 2016-03-21 12:55:16
○ 2017-01-19 04:48:44
○ 2026-06-26 06:38:44
○NSdns4.registrar-servers.com2015-08-19 → 2016-03-21 · 4 obs
● 2016-03-21 12:55:16
○ 2017-01-19 04:48:44
○ 2026-06-26 06:38:44
○NSdns5.registrar-servers.com2015-08-19 → 2016-03-21 · 4 obs
● 2016-03-21 12:55:16
○ 2017-01-19 04:48:44
○ 2026-06-26 06:38:44
○NSns1.bitsr.us2017-01-19 → 2017-01-19 · 4 obs
● 2017-01-19 04:48:44
○ 2019-03-25 02:09:08
○ 2026-06-26 06:38:44
●NSns1.digitalocean.com2026-06-09 → 2026-06-26 · 3 obs
● 2026-06-09 11:36:54
● 2026-06-26 06:38:44
○NSns1.secureserver.net2017-01-19 → 2017-01-19 · 4 obs
● 2017-01-19 04:48:44
○ 2019-03-25 02:09:08
○ 2026-06-26 06:38:44
●NSns2.digitalocean.com2026-06-09 → 2026-06-26 · 3 obs
● 2026-06-09 11:36:54
● 2026-06-26 06:38:44
○NSns2.secureserver.net2017-01-19 → 2017-01-19 · 4 obs
● 2017-01-19 04:48:44
○ 2019-03-25 02:09:08
○ 2026-06-26 06:38:44
●NSns3.digitalocean.com2026-06-09 → 2026-06-26 · 3 obs
● 2026-06-09 11:36:54
● 2026-06-26 06:38:44
○MXbitsr.us2017-01-19 → 2017-01-19 · 4 obs
● 2017-01-19 04:48:44
○ 2019-03-25 02:09:08
○ 2026-06-26 06:38:44
○MXeforward1.registrar-servers.com2015-08-19 → 2016-03-21 · 4 obs
● 2016-03-21 12:55:16
○ 2017-01-19 04:48:44
○ 2026-06-26 06:38:44
○MXeforward2.registrar-servers.com2015-08-19 → 2016-03-21 · 4 obs
● 2016-03-21 12:55:16
○ 2017-01-19 04:48:44
○ 2026-06-26 06:38:44
○MXeforward3.registrar-servers.com2015-08-19 → 2016-03-21 · 4 obs
● 2016-03-21 12:55:16
○ 2017-01-19 04:48:44
○ 2026-06-26 06:38:44
○MXeforward4.registrar-servers.com2015-08-19 → 2016-03-21 · 4 obs
● 2016-03-21 12:55:16
○ 2017-01-19 04:48:44
○ 2026-06-26 06:38:44
○MXeforward5.registrar-servers.com2015-08-19 → 2016-03-21 · 4 obs
● 2016-03-21 12:55:16
○ 2017-01-19 04:48:44
○ 2026-06-26 06:38:44
○A162.255.119.2532015-08-19 → 2016-03-21 · 4 obs
● 2016-03-21 12:55:16
○ 2017-01-19 04:48:44
○ 2026-06-26 06:38:44
○A192.169.143.622017-01-19 → 2017-01-19 · 4 obs
● 2017-01-19 04:48:44
○ 2019-03-25 02:09:08
○ 2026-06-26 06:38:44
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| us | m.cctld.us, f.cctld.us, b.cctld.us, k.cctld.us... | - |
| bitsr.us | ns2.digitalocean.com, ns1.digitalocean.com, ns3.digitalocean.com | - |
✅ Authoritative Response
Server:172.64.53.21
NS records: ns2.digitalocean.com, ns1.digitalocean.com, ns3.digitalocean.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for bitsr.us (unsigned zone)
⏱️ Timing
Total: 378ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 3 | ns2.digitalocean.com, ns3.digitalocean.com... |
| SOA | 1 | ns1.digitalocean.com hostmaster.bitsr.us |
Analysis
Name Servers
bitsr.us has three name servers — ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com.
bitsr.us shares at least some of its name servers with other domains, including jandhfence.com, 1.0.0.7.6.1.8.0.0.0.0.0.0.0.0.0.1.d.0.0.0.0.4.0.0.8.8.a.4.0.6.2.ip6.arpa, 120.89.159.in-addr.arpa and two others.
Each of ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com points to two IP numbers. ns1.digitalocean.com points to 172.64.52.210 and 2606:4700:52::ac40:34d2. ns2.digitalocean.com points to 172.64.53.21 and 2606:4700:5a::ac40:3515. ns3.digitalocean.com points to 172.64.49.209 and 2606:4700:52::ac40:31d1.