`phoenix-ticketing.com`

DNSSEC	⚠️ Not signed
NS	`ns1.systemdns.com` ⭐
		A	2604:4000:0:d:216:40:47:90^{🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000}
			PTR	`ns1.systemdns.com`
		A	216.40.47.90^{🇨🇦 TUCOWS216.40.47.0/24 -BRA-BLK1.4/NET-216-40-47-0}
			PTR	`ns1.systemdns.com`
NS	`ns2.systemdns.com`
		A	2604:4000:2800:d:64:99:148:16^{🇨🇦 TUCOWS-32604:4000:2800::/37 Tucows.com Co.}
			PTR	`ns2.systemdns.com`
		A	64.98.148.16^{🇨🇦 TUCOWS-364.98.144.0/20 Tucows.com Co.}
			PTR	`ns2.systemdns.com`
NS	`ns3.systemdns.com`
		A	2604:4000:0:d:64:99:96:36^{🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000}
			PTR	`ns3.systemdns.com`
		A	64.99.96.36^{🇨🇦 TUCOWS64.99.96.0/24 -BRA-BLK2.7.2}
			PTR	`ns3.systemdns.com`
MX	`mx.phoenix-ticketing.com.cust.b.hostedemail.com` ⭐
		A	64.98.38.4^{🇨🇦 TUCOWS-364.98.38.0/24 IPv4 Allow}
			PTR	`mx.b.hostedemail.com`
SOA	`ns1.systemdns.com`hostmaster@systemdns.com serial=1752479539

`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.net`nstld@verisign-grs.com serial=1778400946

Same first word

phoenix-ticketing.com

DNS History

4 records (4 active, 0 former)

●NSns1.systemdns.com2020-03-03 → 2026-05-10 · 2 obs

● 2020-03-03 07:14:06
● 2026-05-10 08:40:52

●NSns2.systemdns.com2020-03-03 → 2026-05-10 · 2 obs

● 2020-03-03 07:14:06
● 2026-05-10 08:40:52

●NSns3.systemdns.com2020-03-03 → 2026-05-10 · 2 obs

● 2020-03-03 07:14:06
● 2026-05-10 08:40:52

●MXmx.phoenix-ticketing.com.cust.b.hostedemail.com2020-03-03 → 2026-05-10 · 2 obs

● 2020-03-03 07:14:06
● 2026-05-10 08:40:52

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
phoenix-ticketing.com	ns1.systemdns.com, ns2.systemdns.com, ns3.systemdns.com	6 records

✅ Authoritative Response

Server:64.98.148.16

NS records: ns1.systemdns.com, ns2.systemdns.com, ns3.systemdns.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for phoenix-ticketing.com (unsigned zone)

⏱️ Timing

Total: 190ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	3	`ns2.systemdns.com, ns3.systemdns.com...`
MX	1	`mx.phoenix-ticketing.com.cust.b.hostedem`
SOA	1	`ns1.systemdns.com hostmaster.systemdns.c`

📌 Glue Records Collected

Total: 6

Out-of-bailiwick: 6 (ns1.systemdns.com, ns1.systemdns.com, ns2.systemdns.com...)

Analysis

Name Servers

phoenix-ticketing.com is delegated to three name servers: ns1.systemdns.com, ns2.systemdns.com and ns3.systemdns.com.

phoenix-ticketing.com at least partially shares name servers with other domains, for instance dmiheatingandair.com, mooseview.com, opensrs.mobi, counterweightmedia.com and halalmeatandgroceries.com.

Host names with two IP numbers:

Host ns1.systemdns.com points to 2604:4000:0:d:216:40:47:90 and 216.40.47.90.

Host ns2.systemdns.com points to 2604:4000:2800:d:64:99:148:16 and 64.98.148.16.

Host ns3.systemdns.com points to 2604:4000:0:d:64:99:96:36 and 64.99.96.36.

Mail Servers

phoenix-ticketing.com is handled by a single mail server, mx.phoenix-ticketing.com.cust.b.hostedemail.com.

Host name mx.phoenix-ticketing.com.cust.b.hostedemail.com points to IP address 64.98.38.4.

phoenix-ticketing.com - robtex.com