vipticketpro.com - robtex.com
vipticketpro.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=1775203357 | ||||||
Previously MX for
vipticketpro.com |
Subdomains
www.vipticketpro.com |
Same first word
vipticketpro.com |
DNS History
9 records (4 active, 5 former)
●NSadi.ns.cloudflare.com2026-04-02 → 2026-04-03 · 3 obs
● 2026-04-02 17:02:08
● 2026-04-03 08:29:58
●NSjeremy.ns.cloudflare.com2026-04-02 → 2026-04-03 · 3 obs
● 2026-04-02 17:02:08
● 2026-04-03 08:29:58
○NSns51.1and1.com2015-05-25 → 2017-04-10 · 4 obs
● 2017-04-10 01:53:18
○ 2026-04-02 17:02:08
○ 2026-04-03 08:29:58
○NSns52.1and1.com2015-05-25 → 2017-04-10 · 4 obs
● 2017-04-10 01:53:18
○ 2026-04-02 17:02:08
○ 2026-04-03 08:29:58
○MXmx01.1and1.com2015-05-25 → 2017-04-10 · 4 obs
● 2017-04-10 01:53:18
○ 2026-04-02 17:02:08
○ 2026-04-03 08:29:58
●MXvipticketpro-com.mail.protection.outlook.com2026-04-02 → 2026-04-03 · 3 obs
● 2026-04-02 17:02:08
● 2026-04-03 08:29:58
○MXvipticketpro.com2015-05-25 → 2017-04-10 · 4 obs
● 2017-04-10 01:53:18
○ 2026-04-02 17:02:08
○ 2026-04-03 08:29:58
○A108.175.8.322015-05-25 → 2017-04-10 · 4 obs
● 2017-04-10 01:53:18
○ 2026-04-02 17:02:08
○ 2026-04-03 08:29:58
●A160.153.181.2282026-04-02 → 2026-04-03 · 3 obs
● 2026-04-02 17:02:08
● 2026-04-03 08:29:58
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| vipticketpro.com | adi.ns.cloudflare.com, jeremy.ns.cloudflare.com | 12 records |
✅ Authoritative Response
Server:108.162.193.180
NS records: adi.ns.cloudflare.com, jeremy.ns.cloudflare.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for vipticketpro.com (unsigned zone)
⏱️ Timing
Total: 279ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 160.153.181.228 |
| NS | 2 | adi.ns.cloudflare.com, jeremy.ns.cloudflare.com |
| MX | 1 | vipticketpro-com.mail.protection.outlook |
| TXT | 2 | MS=ms23194674, v=spf1 include:secureserver.net -all |
| SOA | 1 | adi.ns.cloudflare.com dns.cloudflare.com |
📌 Glue Records Collected
Total: 12
Out-of-bailiwick: 12 (adi.ns.cloudflare.com, adi.ns.cloudflare.com, adi.ns.cloudflare.com...)
Analysis
Hierarchy
vipticketpro.com is a parent of www.vipticketpro.com.
IP Addresses
vipticketpro.com points to a single IP address: 160.153.181.228.
Name Servers
vipticketpro.com is delegated to two name servers: adi.ns.cloudflare.com and jeremy.ns.cloudflare.com.
vipticketpro.com uses the same name server setup as other domains, including ifbbparana.com.br, torr.se, rbcreations.nl, thegameispon.com and groeilichtinstallaties.nl.
At least part of the name servers for vipticketpro.com are shared with other domains, for instance bizcloud.pro, earnmog.com, brdice-login.com, wallbangerssportsbar.com and traderplatinum.com.
These name servers are commonly used with damien.ns.cloudflare.com, carl.ns.cloudflare.com, joyce.ns.cloudflare.com and neil.ns.cloudflare.com.
Host names with six IP numbers:
adi.ns.cloudflare.com points to: 2606:4700:50::adf5:3a38, 2803:f800:50::6ca2:c038, 2a06:98c1:50::ac40:2038, 108.162.192.56, 172.64.32.56 and 173.245.58.56.
jeremy.ns.cloudflare.com points to: 2606:4700:58::adf5:3bb4, 2803:f800:50::6ca2:c1b4, 2a06:98c1:50::ac40:21b4, 108.162.193.180, 172.64.33.180 and 173.245.59.180.
Mail Servers
The mail server for vipticketpro.com is vipticketpro-com.mail.protection.outlook.com.
vipticketpro-com.mail.protection.outlook.com points to eight IP numbers: 2a01:111:f403:c942::, 2a01:111:f403:c942::2, 2a01:111:f403:c942::3, 2a01:111:f403:c944::1, 52.101.190.0, 52.101.190.1, 52.101.192.0 and 52.101.192.1.