ticketstravelnetwork.com - robtex.com
ticketstravelnetwork.com
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1771291435 | ||||||
Subdomains
www.ticketstravelnetwork.com |
Same first word
ticketstravelnetwork.com |
DNS History
9 records (8 active, 1 former)
●NSlily.ns.cloudflare.com2016-12-18 → 2026-03-18 · 2 obs
● 2026-03-18 08:46:20
●NSwoz.ns.cloudflare.com2016-12-18 → 2026-03-18 · 2 obs
● 2026-03-18 08:46:20
●MXalt1.aspmx.l.google.com2016-12-18 → 2026-03-18 · 2 obs
● 2026-03-18 08:46:20
●MXalt2.aspmx.l.google.com2016-12-18 → 2026-03-18 · 2 obs
● 2026-03-18 08:46:20
●MXaspmx.l.google.com2016-12-18 → 2026-03-18 · 2 obs
● 2026-03-18 08:46:20
●MXaspmx2.googlemail.com2016-12-18 → 2026-03-18 · 2 obs
● 2026-03-18 08:46:20
●MXaspmx3.googlemail.com2016-12-18 → 2026-03-18 · 2 obs
● 2026-03-18 08:46:20
○A148.251.54.2372016-12-18 → 2017-08-07 · 4 obs
● 2017-08-07 10:54:06
○ 2026-02-25 12:10:42
○ 2026-03-18 08:46:20
●A168.119.191.1212026-02-25 → 2026-03-18 · 3 obs
● 2026-02-25 12:10:42
● 2026-03-18 08:46:20
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| ticketstravelnetwork.com | lily.ns.cloudflare.com, woz.ns.cloudflare.com | 12 records |
✅ Authoritative Response
Server: 108.162.193.150
NS records: lily.ns.cloudflare.com, woz.ns.cloudflare.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for ticketstravelnetwork.com (unsigned zone)
⏱️ Timing
Total: 201ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 168.119.191.121 |
| NS | 2 | lily.ns.cloudflare.com, woz.ns.cloudflare.com |
| MX | 5 | aspmx.l.google.com (pri: 1), aspmx2.googlemail.com (pri: 10)... |
| TXT | 3 | google-site-verification=tEcks8N3fQGGY5B, knowbe4-site-verification=3155314115e3a6... |
| SOA | 1 | lily.ns.cloudflare.com dns.cloudflare.co |
📌 Glue Records Collected
Total: 12
Out-of-bailiwick: 12 (lily.ns.cloudflare.com, lily.ns.cloudflare.com, lily.ns.cloudflare.com...)
Analysis
Hierarchy
ticketstravelnetwork.com is the parent of www.ticketstravelnetwork.com.
IP Addresses
ticketstravelnetwork.com points to a single IP number: 168.119.191.121.
Other host names, for instance static.121.191.119.168.clients.your-server.de, share IP numbers with ticketstravelnetwork.com.
Name Servers
ticketstravelnetwork.com is delegated to two name servers: lily.ns.cloudflare.com and woz.ns.cloudflare.com.
ticketstravelnetwork.com shares the same name server setup as other domains, for example rossilivecat.com, hhfitness.co.uk, tickets.lv, mato.social and greatclubs.com.
ticketstravelnetwork.com at least partially shares name servers with other domains, for instance mylumavera.com, go-avon.com, adiber.com, hfocus.org and learnware.com.
These name servers are commonly used with ian.ns.cloudflare.com, jay.ns.cloudflare.com, roxy.ns.cloudflare.com and ivy.ns.cloudflare.com.
Host names with six IP numbers:
lily.ns.cloudflare.com points to: 2606:4700:50::adf5:3a82, 2803:f800:50::6ca2:c082, 2a06:98c1:50::ac40:2082, 108.162.192.130, 172.64.32.130 and 173.245.58.130; woz.ns.cloudflare.com points to: 2606:4700:58::adf5:3b96, 2803:f800:50::6ca2:c196, 2a06:98c1:50::ac40:2196, 108.162.193.150, 172.64.33.150 and 173.245.59.150.
Mail Servers
ticketstravelnetwork.com is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com, alt1.aspmx.l.google.com and alt2.aspmx.l.google.com.
ticketstravelnetwork.com shares mail servers with other domains at least partially, including ns500765.ns500699.ns500699.ns500734.ns500699.ns500699.ns500693.ns500693.ns500699.ns500588.ns500699.ns500693.ns500632.ns500588.ns500110.dtrkdll.com, ns500768.ns500758.ns500759.ns500758.ns500698.ns500698.ns500736.ns500736.ns500708.ns500698.ns500708.ns500619.ns500686.ns500619.ns500619.trackreceptor.com, ns500671.ns500742.ns500731.ns500742.ns500671.ns500731.ns500671.ns500688.ns500649.ns500671.ns500671.ns500666.ns500153.tenderladiesbz.com, ns500693.ns500693.ns500699.ns500734.ns500693.ns500734.ns500588.ns500588.ns500693.ns500699.ns500693.ns500683.ns500632.ns500468.ns500110.dtrkdll.com and ns500734.ns500693.ns500693.ns500693.ns500693.ns500699.ns500734.ns500699.ns500683.ns500632.ns500612.ns500612.ns500588.ns500112.dtrkdll.com.
these mail servers are often used with the mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx4.googlemail.com and aspmx5.googlemail.com.
Hosts with two IP numbers:
aspmx2.googlemail.com points to 2607:f8b0:4023:2801::1b and 192.178.128.27.
aspmx3.googlemail.com points to 2607:f8b0:4023:1015::1b and 172.253.135.26.
aspmx.l.google.com points to 2607:f8b0:4004:c19::1b and 172.253.62.27.
alt1.aspmx.l.google.com points to 2607:f8b0:4003:c30::1b and 74.125.27.26.
alt2.aspmx.l.google.com points to 2607:f8b0:4001:c70::1a and 192.178.209.26.