binarysecurity.no - dns.ninja
binarysecurity.no
no
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | charm.norid.no ⭐ | ||||||
| NS | i.nic.no | ||||||
| NS | njet.norid.no | ||||||
| NS | not.norid.no | ||||||
| NS | x.nic.no | ||||||
| NS | y.nic.no | ||||||
| NS | z.nic.no | ||||||
| SOA | charm.norid.nohostmaster@norid.no 2026-06-27 #51 | ||||||
Same first word
binarysecurity.no |
DNS History
17 records (17 active, 0 former)
●NSns-cloud-a1.googledomains.com2026-02-19 → 2026-06-27 · 2 obs
● 2026-06-27 15:09:44
●NSns-cloud-a2.googledomains.com2026-02-19 → 2026-06-27 · 2 obs
● 2026-06-27 15:09:44
●NSns-cloud-a3.googledomains.com2026-02-19 → 2026-06-27 · 2 obs
● 2026-06-27 15:09:44
●NSns-cloud-a4.googledomains.com2026-02-19 → 2026-06-27 · 2 obs
● 2026-06-27 15:09:44
●MXalt1.aspmx.l.google.com2026-02-19 → 2026-06-27 · 2 obs
● 2026-06-27 15:09:44
●MXalt2.aspmx.l.google.com2026-02-19 → 2026-06-27 · 2 obs
● 2026-06-27 15:09:44
●MXalt3.aspmx.l.google.com2026-02-19 → 2026-06-27 · 2 obs
● 2026-06-27 15:09:44
●MXalt4.aspmx.l.google.com2026-02-19 → 2026-06-27 · 2 obs
● 2026-06-27 15:09:44
●MXaspmx.l.google.com2026-02-19 → 2026-06-27 · 2 obs
● 2026-06-27 15:09:44
●A2001:4860:4802:32::152026-02-19 → 2026-06-27 · 2 obs
● 2026-06-27 15:09:44
●A2001:4860:4802:34::152026-02-19 → 2026-06-27 · 2 obs
● 2026-06-27 15:09:44
●A2001:4860:4802:36::152026-02-19 → 2026-06-27 · 2 obs
● 2026-06-27 15:09:44
●A2001:4860:4802:38::152026-02-19 → 2026-06-27 · 2 obs
● 2026-06-27 15:09:44
●A216.239.32.212026-02-19 → 2026-06-27 · 2 obs
● 2026-06-27 15:09:44
●A216.239.34.212026-02-19 → 2026-06-27 · 2 obs
● 2026-06-27 15:09:44
●A216.239.36.212026-02-19 → 2026-06-27 · 2 obs
● 2026-06-27 15:09:44
●A216.239.38.212026-02-19 → 2026-06-27 · 2 obs
● 2026-06-27 15:09:44
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| no | x.nic.no, njet.norid.no, i.nic.no, not.norid.no... | 11 records |
| binarysecurity.no | ns-cloud-a3.googledomains.com, ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a4.googledomains.com | - |
✅ Authoritative Response
Server:216.239.38.106
NS records: ns-cloud-a3.googledomains.com, ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a4.googledomains.com
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 2485ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 4 | 216.239.32.21, 216.239.38.21... |
| AAAA | 4 | 2001:4860:4802:36::15, 2001:4860:4802:32::15... |
| NS | 4 | ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com... |
| MX | 5 | alt1.aspmx.l.google.com (pri: 5), aspmx.l.google.com (pri: 1)... |
| TXT | 4 | google-site-verification=yE23VHidvgh0d3S, v=spf1 include:_spf.google.com -all... |
| SOA | 1 | ns-cloud-a1.googledomains.com cloud-dns- |
📌 Glue Records Collected
Total: 11
In-bailiwick: 11 (i.nic.no, x.nic.no, y.nic.no...)
Analysis
IP Addresses
With 8 IP addresses in total, binarysecurity.no resolves to 216.239.32.21, 216.239.34.21, 216.239.36.21 and 5 other.
Among the host names that share IP numbers with binarysecurity.no are backlink.win, imsold.mobi, abermax.com and two others.
Name Servers
The domain binarysecurity.no is delegated to these four name servers: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com and ns-cloud-a4.googledomains.com.
The name servers of binarysecurity.no overlap at least partially with those of other domains — among them keeski.com, woodfralivespace.com, bakebuds.com and two more.
Each of the four hosts ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com and ns-cloud-a4.googledomains.com has two IP addresses. ns-cloud-a1.googledomains.com points to 216.239.32.106 and 2001:4860:4802:32::6a. ns-cloud-a2.googledomains.com points to 216.239.34.106 and 2001:4860:4802:34::6a. ns-cloud-a3.googledomains.com points to 216.239.36.106 and 2001:4860:4802:36::6a. ns-cloud-a4.googledomains.com points to 216.239.38.106 and 2001:4860:4802:38::6a.
Mail Servers
Five mail servers handle binarysecurity.no: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
binarysecurity.no shares at least some of its mail servers with other domains — for example ns500742.ns500731.ns500671.ns500742.ns500704.ns500731.ns500291.ns500649.ns500649.ns500671.lusty(0x736c7574)z.com, ns500731.ns500731.ns500731.ns500671.ns500731.ns500671.ns500731.ns500705.ns500688.ns500704.ns500704.ns500688.ns500705.ns500705.ns500291.ns500688.tenderladiesbz.com, ns500758.ns500758.ns500698.ns500758.ns500736.ns500698.ns500698.ns500735.ns500708.ns500698.ns500708.ns500576.ns500652.ns500576.trackreceptor.com and two more.
It is common for these mail servers to co-occur with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com as mail servers.
Hosts with two IP numbers each:
aspmx.l.google.com directs traffic to 142.251.163.27 and 2607:f8b0:4004:c0b::1a.
alt1.aspmx.l.google.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1a.
alt3.aspmx.l.google.com directs traffic to 192.178.223.27 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com directs traffic to 172.253.157.27 and 2a00:1450:400c:c23::1b.