bandprotocol.com - dns.ninja
bandprotocol.com
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=1783471981 | ||||||
rank #76927 in the tld
📈 Tranco rank: #619,295
Same first word
bandprotocol.com |
DNS History
10 records (8 active, 2 former)
●NSjanet.ns.cloudflare.com2018-05-16 → 2026-07-08 · 2 obs
● 2026-07-08 01:09:54
●NSray.ns.cloudflare.com2018-05-16 → 2026-07-08 · 2 obs
● 2026-07-08 01:09:54
●MXalt1.aspmx.l.google.com2018-05-16 → 2026-07-08 · 2 obs
● 2026-07-08 01:09:54
●MXalt2.aspmx.l.google.com2018-05-16 → 2026-07-08 · 2 obs
● 2026-07-08 01:09:54
●MXaspmx.l.google.com2018-05-16 → 2026-07-08 · 2 obs
● 2026-07-08 01:09:54
●MXaspmx2.googlemail.com2018-05-16 → 2026-07-08 · 2 obs
● 2026-07-08 01:09:54
●MXaspmx3.googlemail.com2018-05-16 → 2026-07-08 · 2 obs
● 2026-07-08 01:09:54
○A104.198.14.522020-12-17 → 2020-12-17 · 3 obs
○ 2021-10-26 19:14:56
○ 2026-07-08 01:09:54
○A75.2.60.52021-10-26 → 2021-10-26 · 4 obs
● 2021-10-26 19:14:56
○ 2026-03-29 08:21:32
○ 2026-07-08 01:09:54
●A76.76.21.212026-03-29 → 2026-07-08 · 3 obs
● 2026-03-29 08:21:32
● 2026-07-08 01:09:54
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| bandprotocol.com | ray.ns.cloudflare.com, janet.ns.cloudflare.com | 12 records |
✅ Authoritative Response
Server:172.64.32.169
NS records: ray.ns.cloudflare.com, janet.ns.cloudflare.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for bandprotocol.com (unsigned zone)
⏱️ Timing
Total: 165ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 76.76.21.21 |
| NS | 2 | janet.ns.cloudflare.com, ray.ns.cloudflare.com |
| MX | 5 | aspmx.l.google.com (pri: 1), aspmx2.googlemail.com (pri: 10)... |
| TXT | 7 | google-site-verification=6tl4Vb4uakRyUFK, google-site-verification=F8_c1kmM-aDnxZ2... |
| SOA | 1 | janet.ns.cloudflare.com dns.cloudflare.c |
📌 Glue Records Collected
Total: 12
Out-of-bailiwick: 12 (ray.ns.cloudflare.com, ray.ns.cloudflare.com, ray.ns.cloudflare.com...)
Analysis
IP Addresses
bandprotocol.com points to a single IP number: 76.76.21.21.
Additional host names — altadaily.com, kognise.dev, bjazds.com and two others — share IP numbers with bandprotocol.com.
Name Servers
Two name servers handle the delegation for bandprotocol.com: janet.ns.cloudflare.com and ray.ns.cloudflare.com.
bandprotocol.com shares its name server setup with other domains, including fabiclosa.click, sweetfeet.uk.com, interface.com.mx and two others.
The name servers of bandprotocol.com overlap at least partially with those of other domains — among them evo888h5.com, fallingblue.com, ebsderots.nl and two more.
These name servers commonly appear alongside the name servers wells.ns.cloudflare.com and marjory.ns.cloudflare.com.
Host names with 6 IP numbers:
janet.ns.cloudflare.com resolves to 108.162.192.169, 172.64.32.169 and 173.245.58.169 among others, with 3 other IP addresses in total.
ray.ns.cloudflare.com resolves to 108.162.193.138, 172.64.33.138 and 173.245.59.138 among others, with 3 other IP addresses in total.
Mail Servers
Five mail servers handle bandprotocol.com: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
bandprotocol.com shares mail servers — at least in part — with other domains, including ns500698.ns500759.ns500698.ns500698.ns500698.ns500736.ns500736.ns500735.ns500735.ns500735.ns500708.ns500708.ns500708.ns500576.ns500686.ns500652.ns500619.trackreceptor.com, ns500841.ns500795.ns500795.ns500795.ns500821.ns500794.ns500795.lustypartnersfinder.com, cardinalcontent.com and two others.
These mail servers are frequently used alongside mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 other.
Host names with two IP numbers:
aspmx2.googlemail.com resolves to two addresses: 108.177.123.26 and 2800:3f0:4003:c0f::1a.
aspmx3.googlemail.com resolves to two addresses: 172.253.116.27 and 2a00:1450:400b:c02::1b.
aspmx.l.google.com resolves to two addresses: 142.251.167.27 and 2607:f8b0:4004:c21::1a.
alt1.aspmx.l.google.com resolves to two addresses: 108.177.123.26 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.26 and 2a00:1450:400b:c02::1b.
aspmx2.googlemail.com along with alt1.aspmx.l.google.com each resolve to 2800:3f0:4003:c0f::1a IP addresses.
aspmx2.googlemail.com along with alt1.aspmx.l.google.com each resolve to 108.177.123.26 IP addresses.
aspmx3.googlemail.com along with alt2.aspmx.l.google.com each resolve to 2a00:1450:400b:c02::1b IP addresses.