mx.34.amsterdam - robtex.com
mx.34.amsterdam
| DNSSEC | ⚠️ Not signed | ||||||
| A | 91.195.241.232🇩🇪 SEDO91.195.240.0/23 -NET-PI | ||||||
| NS | sl1.sedo.com ⭐ ⚠️ Not in parent delegation | ||||||
| A | 91.195.240.173🇩🇪 SEDO91.195.240.0/23 -NET-PI | ||||||
| NS | sl2.sedo.com ⚠️ Not in parent delegation | ||||||
| A | 91.195.241.173🇩🇪 SEDO91.195.240.0/23 -NET-PI | ||||||
| MX | localhost ⭐ | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | sl1.sedo.comhostmaster@sedo.de 2018-05-16 #1 | ||||||
34.amsterdam
| DNSSEC | ⚠️ Not signed | ||||||
| A | 91.195.241.232🇩🇪 SEDO91.195.240.0/23 -NET-PI | ||||||
| NS | sl1.sedo.com ⭐ | ||||||
| NS | sl2.sedo.com | ||||||
| MX | localhost ⭐ | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | sl1.sedo.comhostmaster@sedo.de 2018-05-16 #1 | ||||||
Previously MX for
Same first word
Similar names
DNS History
8 records (4 active, 4 former)
○NSns1.undeveloped.com2016-12-14 → 2016-12-14 · 3 obs
○ 2026-03-06 08:23:16
○ 2026-04-11 19:23:14
○NSns2.undeveloped.com2016-12-14 → 2016-12-14 · 3 obs
○ 2026-03-06 08:23:16
○ 2026-04-11 19:23:14
●NSsl1.sedo.com2026-03-06 → 2026-04-11 · 3 obs
● 2026-03-06 08:23:16
● 2026-04-11 19:23:14
●NSsl2.sedo.com2026-03-06 → 2026-04-11 · 3 obs
● 2026-03-06 08:23:16
● 2026-04-11 19:23:14
●MXlocalhost2026-03-06 → 2026-04-11 · 3 obs
● 2026-03-06 08:23:16
● 2026-04-11 19:23:14
○MXmx.mx.34.amsterdam2016-12-14 → 2016-12-14 · 3 obs
○ 2026-03-06 08:23:16
○ 2026-04-11 19:23:14
○A52.58.78.162016-12-14 → 2016-12-14 · 3 obs
○ 2026-03-06 08:23:16
○ 2026-04-11 19:23:14
●A91.195.241.2322026-03-06 → 2026-04-11 · 3 obs
● 2026-03-06 08:23:16
● 2026-04-11 19:23:14
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| amsterdam | ns3.dns.amsterdam, ns1.dns.amsterdam, ns4.dns.amsterdam | 6 records |
| 34.amsterdam | sl1.sedo.com, sl2.sedo.com | - |
✅ Authoritative Response
Server:91.195.241.173
NS records: sl1.sedo.com, sl2.sedo.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for 34.amsterdam (unsigned zone)
⏱️ Timing
Total: 505ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 91.195.241.232 |
| NS | 2 | sl2.sedo.com, sl1.sedo.com |
| MX | 1 | localhost (pri: 0) |
| TXT | 1 | v=spf1 -all |
| SOA | 1 | sl1.sedo.com hostmaster.sedo.de |
📌 Glue Records Collected
Total: 6
In-bailiwick: 6 (ns3.dns.amsterdam, ns3.dns.amsterdam, ns1.dns.amsterdam...)
Analysis
IP Addresses
mx.34.amsterdam resolves to one IP number: 91.195.241.232.
Other host names, for instance pzss.net, 70-33.84.64.master-link.com, insource.eu, unitel.ch and topcode.de share IP numbers with mx.34.amsterdam.
Name Servers
mx.34.amsterdam's delegation uses two name servers: sl1.sedo.com and sl2.sedo.com.
mx.34.amsterdam uses the same name server setup as other domains, such as labra.eu, ruba.in, mx.mx.mx.4.amsterdam, fitnessjunkie.de and baex.eu.
Host names with a single IP address: sl1.sedo.com points to 91.195.240.173; sl2.sedo.com points to 91.195.241.173.
Mail Servers
A single mail server handles mx.34.amsterdam, localhost.
mx.34.amsterdam shares the same mail server setup as other domains, for instance mail.grosser-dreesch.de, tife.com, ns1.srbs.in, aimhire.de and wjun.jc-net.com.