IPLIST.NET - cortex-tickets.de
Search for IP or hostnames:
cortex-tickets.de checked at 2025-09-17T15:18:28.124Z 143ms 77/77/77 100% R:16cortex-tickets.de
| MX | mail.cortex-media.de | ||||||
| A | 2a01:4f8:212:1cc5::222 🇩🇪 Hetzner | ||||||
| PTR | mail.cortex-media.de | ||||||
| A | 136.243.217.222🇩🇪 Hetzner | ||||||
| PTR | mail.cortex-media.de | ||||||
| NS | dns102.ovh.net | ||||||
| A | 2001:41d0:d00:fc00::2 🇫🇷 OVH | ||||||
| PTR | dns102.ovh.net | ||||||
| A | 5.196.38.181🇫🇷 OVH | ||||||
| PTR | dns102.ovh.net | ||||||
| NS | ns102.ovh.net | ||||||
| A | 2001:41d0:b00:f600::2 🇫🇷 OVH | ||||||
| PTR | ns102.ovh.net | ||||||
| A | 5.135.54.1🇧🇪 OVH | ||||||
| PTR | ns102.ovh.net | ||||||
| A | 2a01:4f8:212:1cc5::216 🇩🇪 Hetzner | ||||||
| PTR | cortex-tickets.de | ||||||
| A | 136.243.217.216🇩🇪 Hetzner | ||||||
| PTR | cortex-tickets.de | ||||||
de
| NS | a.nic.de | ||||||
| NS | f.nic.de | ||||||
| NS | z.nic.de | ||||||
| NS | l.de.net | ||||||
| NS | n.de.net | ||||||
| NS | s.de.net | ||||||
PTR for
6.1.2.0.0.0.0.0.0.0.0.0.0.0.0.0.5.c.c.1.2.1.2.0.8.f.4.0.1.0.a.2.ip6.arpa |
216.217.243.136.in-addr.arpa |
Starts with same word
cortex-tickets.de |
Starts similarily
cortex-tickets.de |
AI analysis
cortex-tickets.de resolves to two IP numbers: 2a01:4f8:212:1cc5::216 and 136.243.217.216.
cortex-tickets.de has two name servers: dns102.ovh.net and ns102.ovh.net.
cortex-tickets.de shares the same name server setup as other domains, for example sillagesparis.net, atol-opticien.fr, kintambo.cd, skutery-zakopane.pl and hotelbardolino.com.
cortex-tickets.de partially shares name servers with other domains, for instance 50.32.213.in-addr.arpa.
Host names with two IP numbers:
dns102.ovh.net points to: 2001:41d0:d00:fc00::2 and 5.196.38.181; ns102.ovh.net points to: 2001:41d0:b00:f600::2 and 5.135.54.1.
cortex-tickets.de is handled by a single mail server, mail.cortex-media.de.
cortex-tickets.de uses the same mail server setup as other domains, for example fhrk.de, peri-exchange.com and cortex-media.de.
mail.cortex-media.de resolves to two IPs: 2a01:4f8:212:1cc5::222 and 136.243.217.222.