ticketscom.de - robtex.com
ticketscom.de
| DNSSEC | ⚠️ Not signed | ||||||
| A | 23.88.34.196🇩🇪 Hetzner23.88.0.0/17 HETZNER-DC | ||||||
| PTR | static.196.34.88.23.clients.your-server.de | ||||||
| NS | ns1.redirectdom.com ⭐ | ||||||
| A | 168.119.46.105🇩🇪 Hetzner168.119.0.0/16 HETZNER-DC | ||||||
| PTR | ns1.redirectdom.com | ||||||
| NS | ns2.redirectdom.com | ||||||
| A | 51.195.125.195🇫🇷 OVH51.195.0.0/16 | ||||||
| PTR | ns2.redirectdom.com | ||||||
| SOA | ns1.redirectdom.comdnsmaster@ns1.redirectdom.com 2025-05-08 #2 | ||||||
de
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | f.nic.de ⭐ | ||||||
| NS | a.nic.de | ||||||
| NS | l.de.net ⚠️ Not in parent delegation | ||||||
| NS | n.de.net ⚠️ Not in parent delegation | ||||||
| NS | s.de.net ⚠️ Not in parent delegation | ||||||
| NS | z.nic.de | ||||||
| SOA | f.nic.dedns-operations@denic.de serial=1785275088 | ||||||
Same first word
ticketscom.de |
ticketscom.com |
Similar names
DNS History
18 records (3 active, 15 former)
○NSns1.domainname.at2018-12-20 → 2018-12-20 · 3 obs
○ 2017-02-11 10:13:06
● 2018-12-20 11:21:56
○ 2026-07-28 21:49:16
● 2018-12-20 11:21:56
○ 2026-07-28 21:49:16
○NSns1.oxilion.nl2015-08-09 → 2015-08-09 · 3 obs
● 2015-08-09 13:44:30
○ 2015-11-29 11:34:52
○ 2026-07-28 21:49:16
○ 2015-11-29 11:34:52
○ 2026-07-28 21:49:16
●NSns1.redirectdom.com2018-12-20 → 2026-07-28 · 3 obs
○ 2017-02-11 10:13:06
● 2018-12-20 11:21:56
● 2026-07-28 21:49:16
● 2018-12-20 11:21:56
● 2026-07-28 21:49:16
○NSns2.oxilion.nl2015-08-09 → 2015-08-09 · 3 obs
● 2015-08-09 13:44:30
○ 2015-11-29 11:34:52
○ 2026-07-28 21:49:16
○ 2015-11-29 11:34:52
○ 2026-07-28 21:49:16
●NSns2.redirectdom.com2018-12-20 → 2026-07-28 · 3 obs
○ 2017-02-11 10:13:06
● 2018-12-20 11:21:56
● 2026-07-28 21:49:16
● 2018-12-20 11:21:56
● 2026-07-28 21:49:16
○NSns3.oxilion.net2015-08-09 → 2015-08-09 · 3 obs
● 2015-08-09 13:44:30
○ 2015-11-29 11:34:52
○ 2026-07-28 21:49:16
○ 2015-11-29 11:34:52
○ 2026-07-28 21:49:16
○NSns33.rookdns.com2017-02-11 → 2017-02-11 · 4 obs
○ 2015-11-29 11:34:52
● 2017-02-11 10:13:06
○ 2018-12-20 11:21:56
○ 2026-07-28 21:49:16
● 2017-02-11 10:13:06
○ 2018-12-20 11:21:56
○ 2026-07-28 21:49:16
○NSns34.rookdns.com2017-02-11 → 2017-02-11 · 4 obs
○ 2015-11-29 11:34:52
● 2017-02-11 10:13:06
○ 2018-12-20 11:21:56
○ 2026-07-28 21:49:16
● 2017-02-11 10:13:06
○ 2018-12-20 11:21:56
○ 2026-07-28 21:49:16
○MXfallbackmx.spamexperts.eu2015-08-09 → 2015-08-09 · 3 obs
● 2015-08-09 13:44:30
○ 2015-11-29 11:34:52
○ 2026-07-28 21:49:16
○ 2015-11-29 11:34:52
○ 2026-07-28 21:49:16
○MXlastmx.spamexperts.net2015-08-09 → 2015-08-09 · 3 obs
● 2015-08-09 13:44:30
○ 2015-11-29 11:34:52
○ 2026-07-28 21:49:16
○ 2015-11-29 11:34:52
○ 2026-07-28 21:49:16
○MXmx.spamexperts.com2015-08-09 → 2015-08-09 · 3 obs
● 2015-08-09 13:44:30
○ 2015-11-29 11:34:52
○ 2026-07-28 21:49:16
○ 2015-11-29 11:34:52
○ 2026-07-28 21:49:16
○MXstatic.51.2.69.159.clients.your-server.de2018-12-20 → 2018-12-20 · 3 obs
○ 2015-11-29 11:34:52
● 2018-12-20 11:21:56
○ 2026-07-28 21:49:16
● 2018-12-20 11:21:56
○ 2026-07-28 21:49:16
○A141.8.224.1752017-02-11 → 2017-02-11 · 4 obs
○ 2016-06-21 09:30:00
● 2017-02-11 10:13:06
○ 2018-12-20 11:21:56
○ 2026-07-28 21:49:16
● 2017-02-11 10:13:06
○ 2018-12-20 11:21:56
○ 2026-07-28 21:49:16
○A176.9.83.2292018-12-20 → 2018-12-20 · 3 obs
○ 2017-02-11 10:13:06
● 2018-12-20 11:21:56
○ 2026-07-28 21:49:16
● 2018-12-20 11:21:56
○ 2026-07-28 21:49:16
●A23.88.34.1962026-07-28 → 2026-07-28 · 2 obs
○ 2018-12-20 11:21:56
● 2026-07-28 21:49:16
● 2026-07-28 21:49:16
○A46.4.13.972016-03-01 → 2016-06-21 · 5 obs
○ 2015-11-29 11:34:52
● 2016-03-01 16:54:58
● 2016-06-21 09:30:00
○ 2017-02-11 10:13:06
○ 2026-07-28 21:49:16
● 2016-03-01 16:54:58
● 2016-06-21 09:30:00
○ 2017-02-11 10:13:06
○ 2026-07-28 21:49:16
○A87.253.130.332015-08-09 → 2015-08-09 · 3 obs
● 2015-08-09 13:44:30
○ 2015-11-29 11:34:52
○ 2026-07-28 21:49:16
○ 2015-11-29 11:34:52
○ 2026-07-28 21:49:16
○PTRns33.rookdns.com2017-02-11 → 2017-02-11 · 3 obs
● 2017-02-11 10:13:06
○ 2018-12-20 11:21:56
○ 2026-07-28 21:49:16
○ 2018-12-20 11:21:56
○ 2026-07-28 21:49:16
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| de | a.nic.de, z.nic.de, f.nic.de | - |
| ticketscom.de | ns2.redirectdom.com, ns1.redirectdom.com | - |
✅ Authoritative Response
Server:168.119.46.105
NS records: ns2.redirectdom.com, ns1.redirectdom.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for ticketscom.de (unsigned zone)
⏱️ Timing
Total: 890ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 23.88.34.196 |
| NS | 2 | ns2.redirectdom.com, ns1.redirectdom.com |
| SOA | 1 | ns1.redirectdom.com dnsmaster.ns1.redire |
Analysis
IP Addresses
ticketscom.de resolves to just one IP address, 23.88.34.196.
Two other host names, along with kometer.de, karnevalforum.de and paarfoto.de, also share IP numbers with ticketscom.de.
Name Servers
ticketscom.de uses two name servers for its delegation: ns1.redirectdom.com and ns2.redirectdom.com.
ticketscom.de shares its NS records with other domains, for example the-newstime.de, troedlershop.de, kreuzfahrten-und-schiffe.de and two others.
Each of ns1.redirectdom.com and ns2.redirectdom.com has one IP address: ns1.redirectdom.com uses 168.119.46.105 and ns2.redirectdom.com uses 51.195.125.195.