lead.berlin - dns.ninja
lead.berlin
berlin
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | z.dns.nic.berlin ⭐ | ||||||
| NS | a.dns.nic.berlin | ||||||
| NS | m.dns.nic.berlin | ||||||
| NS | n.dns.nic.berlin | ||||||
| SOA | z.dns.nic.berlinhostmaster@tld-box.at serial=1785953107 | ||||||
Subdomains
Same first word
Similar names
DNS History
9 records (7 active, 2 former)
●NSns1.name.com2026-02-16 → 2026-08-05 · 3 obs
● 2026-02-16 09:22:52
● 2026-08-05 18:13:00
●MXlead-berlin.mail.protection.outlook.com2026-02-16 → 2026-08-05 · 3 obs
● 2026-02-16 09:22:52
● 2026-08-05 18:13:00
○MXmail.lead.berlin2018-07-06 → 2018-07-06 · 3 obs
○ 2026-02-16 09:22:52
○ 2026-08-05 18:13:00
○A195.253.75.2122018-07-06 → 2018-07-06 · 3 obs
○ 2026-02-16 09:22:52
○ 2026-08-05 18:13:00
●A75.2.60.52026-02-16 → 2026-08-05 · 3 obs
● 2026-02-16 09:22:52
● 2026-08-05 18:13:00
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| berlin | m.dns.nic.berlin, n.dns.nic.berlin, a.dns.nic.berlin | 6 records |
| lead.berlin | ns1ksz.name.com, ns2fhn.name.com, ns3dgj.name.com, ns4hmp.name.com | - |
✅ Authoritative Response
Server:163.114.217.17
NS records: ns1ksz.name.com, ns2fhn.name.com, ns3dgj.name.com, ns4hmp.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for lead.berlin (unsigned zone)
⏱️ Timing
Total: 680ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 75.2.60.5 |
| NS | 4 | ns1ksz.name.com, ns2fhn.name.com... |
| MX | 1 | lead-berlin.mail.protection.outlook.com |
| TXT | 4 | MS=ms35648225, v=spf1 include:emsd1.com include:spf.pro... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
📌 Glue Records Collected
Total: 6
In-bailiwick: 6 (a.dns.nic.berlin, m.dns.nic.berlin, n.dns.nic.berlin...)
Analysis
Hierarchy
www.lead.berlin and mail.lead.berlin each fall under lead.berlin as their parent domain.
IP Addresses
lead.berlin resolves to just one IP address, 75.2.60.5.
Two other host names, along with dev-pm.com, responsibility.ch and coefficientlabs.com, also share IP numbers with lead.berlin.
Name Servers
lead.berlin delegates to five name servers: ns1.name.com, ns1ksz.name.com, ns2fhn.name.com and two others.
lead.berlin has at least partial name server overlap with other domains, such as vrcoordinator.com, thebestdiner.com, sunesisprop.com and two others.
ns4hmp.name.com, ns3dgj.name.com and ns4fqz.name.com — plus 7 other name servers — are commonly paired with these name servers.
Host names that have two IP addresses:
ns1.name.com maps to two IP addresses — 163.114.216.17 and 2a00:edc0:107::1.
ns1ksz.name.com maps to two IP addresses — 163.114.216.17 and 2a00:edc0:107::1.
ns2fhn.name.com maps to two IP addresses — 163.114.216.49 and 2402:cf80:107::1.
ns3dgj.name.com maps to two IP addresses — 163.114.217.17 and 2a00:edc0:107::49.
ns4hmp.name.com maps to two IP addresses — 163.114.217.49 and 2402:cf80:107::49.
These two host names — ns1.name.com and ns1ksz.name.com — each point to 2a00:edc0:107::1 IP addresses.
These two host names — ns1.name.com and ns1ksz.name.com — each point to 163.114.216.17 IP addresses.
Mail Servers
The sole mail server for lead.berlin is lead-berlin.mail.protection.outlook.com.
With 8 IP addresses total, lead-berlin.mail.protection.outlook.com resolves to 52.101.68.0, 52.101.68.5, 52.101.68.16 and 5 others.