bind-0.tum.fail - robtex.com
bind-0.tum.fail
| DNSSEC | ⚠️ Not signed | ||||||
| A | 127.0.0.1 | ||||||
tum.fail
| DNSSEC | ⚠️ Not signed | ||||||
| A | 138.201.223.113🇩🇪 Hetzner138.201.0.0/16 HETZNER-RZ-BLK-ERX4 | ||||||
| NS | bind-0.tum.fail ⭐ | ||||||
| NS | a.ns.tum.fail | ||||||
| NS | b.ns.tum.fail | ||||||
| NS | c.ns.tum.fail | ||||||
| MX | a.mx.tum.fail ⭐ | ||||||
| MX | b.mx.tum.fail ⭐ | ||||||
| TXT | v=spf1 mx ip4:138.201.223.113 ip4:37.252.191.222 ip6:2a01:4f8:190:10e5:3::2 i... | ||||||
| SOA | bind-0.tum.failhostmaster@tum.fail 2025-11-18 #75 | ||||||
NS for
DNS History
1 record (1 active, 0 former)
●A127.0.0.12026-03-28 → 2026-04-24 · 2 obs
● 2026-03-28 00:00:54
● 2026-04-24 16:24:38
● 2026-04-24 16:24:38
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| fail | v2n1.nic.fail, v0n2.nic.fail, v0n0.nic.fail, v0n1.nic.fail... | 12 records |
| tum.fail | b.ns.tum.fail, a.ns.tum.fail, c.ns.tum.fail | 5 records |
✅ Authoritative Response
Server:37.252.191.222
NS records: b.ns.tum.fail, a.ns.tum.fail, c.ns.tum.fail
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for tum.fail (unsigned zone)
⏱️ Timing
Total: 439ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 127.0.0.1 |
📌 Glue Records Collected
Total: 17
In-bailiwick: 17 (v2n1.nic.fail, v2n0.nic.fail, v0n3.nic.fail...)
Analysis
Name Server Role
bind-0.tum.fail serves as the name server for tum.fail.
a.ns.tum.fail, b.ns.tum.fail and c.ns.tum.fail commonly serve as name servers together with bind-0.tum.fail.
IP Addresses
bind-0.tum.fail resolves to one IP number: 127.0.0.1.
Other host names, for instance sryjneed.host.sk, mx.winglobal.co.kr, da2.io, 173.254.252.173.static.quadranet.com and server-54-230-87-77.lax3.r.cloudfront.ne share IP numbers with bind-0.tum.fail.