ns.log4j.binaryedge.io - robtex.com
ns.log4j.binaryedge.io
| DNSSEC | β οΈ Not signed | ||||||
| A | 134.209.163.248πΊπΈ DIGITALOCEAN134.209.160.0/20 DigitalOcean | ||||||
log4j.binaryedge.io
| DNSSEC | β οΈ Not signed | ||||||
| A | 134.209.163.248πΊπΈ DIGITALOCEAN134.209.160.0/20 DigitalOcean | ||||||
| NS | ns.log4j.binaryedge.io β | ||||||
| NS | 74.207.228.185 β οΈ Not in parent delegation | ||||||
| NS | log4j-ns1.binaryedge.io β οΈ Not in zone NS records | ||||||
| NS | log4j-ns2.binaryedge.io β οΈ Not in zone NS records | ||||||
| SOA | ns.log4j.binaryedge.iohostmaster@log4j.binaryedge.io 2021-12-10 #2 | ||||||
NS for
Same first word
Similar names
DNS History
1 record (1 active, 0 former)
βA134.209.163.2482026-04-08 β 2026-04-25 Β· 2 obs
β 2026-04-08 04:25:28
β 2026-04-25 12:09:22
β 2026-04-25 12:09:22
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| io | a0.nic.io, a2.nic.io, b0.nic.io, c0.nic.io | - |
| binaryedge.io | amir.ns.cloudflare.com, ines.ns.cloudflare.com | - |
| log4j.binaryedge.io | log4j-ns1.binaryedge.io, log4j-ns2.binaryedge.io | 2 records |
β Authoritative Response
Server:74.207.228.185
NS records: log4j-ns1.binaryedge.io, log4j-ns2.binaryedge.io
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
No DS record for binaryedge.io (unsigned zone)
β±οΈ Timing
Total: 369ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 134.209.163.248 |
π Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (log4j-ns1.binaryedge.io, log4j-ns2.binaryedge.io)
Analysis
Name Server Role
ns.log4j.binaryedge.io serves as the name server for log4j.binaryedge.io.
log4j-ns1.binaryedge.io, log4j-ns2.binaryedge.io and 74.207.228.185 commonly serve as name servers alongside ns.log4j.binaryedge.io.
IP Addresses
ns.log4j.binaryedge.io maps to IP address 134.209.163.248.
Other host names for instance log4j.binaryedge.io and world443.log4j.binaryedge.io share IP numbers with ns.log4j.binaryedge.io.