code.brussels - dns.ninja
code.brussels
| DNSSEC | ⚠️ Not signed | ||||||
| A | 178.128.248.56🇳🇱 DIGITALOCEAN178.128.240.0/20 DigitalOcean | ||||||
| PTR | code.brussels | ||||||
| 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@code.brussels serial=0 | ||||||
brussels
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.nsset.brussels ⭐ | ||||||
| NS | b.nsset.brussels | ||||||
| NS | c.nsset.brussels | ||||||
| NS | d.nsset.brussels | ||||||
| NS | y.nsset.brussels | ||||||
| NS | z.nsset.brussels | ||||||
| SOA | a.nsset.brusselsbrussels-hostmaster@dnsbelgium.be serial=1517618715 | ||||||
PTR for
Same first word
Similar names
DNS History
4 records (4 active, 0 former)
●NSns1.digitalocean.com2026-04-05 → 2026-06-04 · 2 obs
● 2026-06-04 10:13:00
●NSns2.digitalocean.com2026-04-05 → 2026-06-04 · 2 obs
● 2026-06-04 10:13:00
●NSns3.digitalocean.com2026-04-05 → 2026-06-04 · 2 obs
● 2026-06-04 10:13:00
●A178.128.248.562026-04-05 → 2026-06-04 · 2 obs
● 2026-06-04 10:13:00
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| brussels | a.nsset.brussels, b.nsset.brussels, c.nsset.brussels, d.nsset.brussels... | 12 records |
| code.brussels | ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com | - |
✅ Authoritative Response
Server:172.64.52.210
NS records: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for code.brussels (unsigned zone)
⏱️ Timing
Total: 389ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 178.128.248.56 |
| NS | 3 | ns2.digitalocean.com, ns3.digitalocean.com... |
| SOA | 1 | ns1.digitalocean.com hostmaster.code.bru |
📌 Glue Records Collected
Total: 12
In-bailiwick: 12 (a.nsset.brussels, a.nsset.brussels, b.nsset.brussels...)
Analysis
IP Addresses
code.brussels has exactly one IP address — 178.128.248.56.
fanarena.com, for instance, is one of the other host names sharing IP numbers with code.brussels.
Name Servers
The authoritative name servers for code.brussels are ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com — three in total.
code.brussels has at least partial name server overlap with other domains, such as www.onlinearsenal.com, safetyknights.com, pages.land and two others.
ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com all resolve to exactly two IP numbers apiece: ns1.digitalocean.com → 172.64.52.210 and 2606:4700:52::ac40:34d2; ns2.digitalocean.com → 172.64.53.21 and 2606:4700:5a::ac40:3515; ns3.digitalocean.com → 172.64.49.209 and 2606:4700:52::ac40:31d1.