`tri-citycollision.com`

DNSSEC	⚠️ Not signed
A	54.236.78.212^{🇺🇸 Amazon54.236.64.0/18 EC2 IAD prefix}
		PTR	`ec2-54-236-78-212.compute-1.amazonaws.com`
NS	`ns3.gkg.net` ⭐ ⚠️ Not in zone NS records
		A	2001:19f0:5:1c3:5400::100^{🇺🇸 AS-VULTR2001:19f0::/38 Vultr Assigned Prefix}
		A	149.154.59.2^{🇺🇸 CMN149.154.56.0/22}
			PTR	`ns3.gkg.net`
NS	`ns1.bdm.microsoftonline.com` ⚠️ Not in parent delegation
		A	2603:1061:0:700::d0^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-208.azure-dns.com`
		A	13.107.236.208^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-208.azure-dns.com`
NS	`ns2.bdm.microsoftonline.com` ⚠️ Not in parent delegation
		A	2620:1ec:8ec:700::d0^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-208.azure-dns.net`
		A	150.171.21.208^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-208.azure-dns.net`
NS	`ns3.bdm.microsoftonline.com` ⚠️ Not in parent delegation
		A	2a01:111:4000:700::d0^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-208.azure-dns.org`
		A	204.14.183.208^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-208.azure-dns.org`
NS	`ns4.bdm.microsoftonline.com` ⚠️ Not in parent delegation
		A	2620:1ec:bda:700::d0^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-208.azure-dns.info`
		A	208.84.5.208^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-208.azure-dns.info`
NS	`ns4.gkg.net` ⚠️ Not in zone NS records
		A	2001:19f0:8000:88a8:5400:ff:fe11:a867^{🇺🇸 AS-VULTR2001:19f0:8000::/38 Vultr Assigned Prefix}
		A	104.238.152.48^{🇺🇸 AS-VULTR104.238.152.0/22 Vultr Assigned Prefix}
			PTR	`ns4.gkg.net`
MX	`tricitycollision-com0i.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c902::3^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sj0pr03cu01703.inbound.protection.outlook.com`
		A	2a01:111:f403:c92c::2^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-dm2pr04cu00102.inbound.protection.outlook.com`
		A	2a01:111:f403:f901::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bl0pr02cu00601.inbound.protection.outlook.com`
		A	2a01:111:f403:f90b::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bn6pr04cu00100.inbound.protection.outlook.com`
		A	52.101.10.16^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bn6pr21cu00500.inbound.protection.outlook.com`
		A	52.101.11.10^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sa9pr03cu00202.inbound.protection.outlook.com`
		A	52.101.41.183^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-byapr04cu00307.inbound.protection.outlook.com`
		A	52.101.194.4^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-ch4pr04cu00104.inbound.protection.outlook.com`
TXT	`MS=`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
TXT	`MS=ms46321929`
SOA	`ns3.gkg.net`root@tri-citycollision.com serial=1754415834

`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=1785154722

WOT: SAFE (19/100)

Previously MX for

tri-citycollision.com

Same first word

tri-citycollision.com

DNS History

21 records (8 active, 13 former)

○NSdns.stabletransit.com2015-06-15 → 2019-01-02 · 5 obs

○ 2008-03-16 09:44:26
● 2015-06-15 13:11:44
● 2019-01-02 18:11:32
○ 2026-05-02 02:28:06
○ 2026-07-27 12:33:38

○NSdns1.stabletransit.com2015-06-15 → 2019-01-02 · 5 obs

○ 2008-03-16 09:44:26
● 2015-06-15 13:11:44
● 2019-01-02 18:11:32
○ 2026-05-02 02:28:06
○ 2026-07-27 12:33:38

○NSdns2.stabletransit.com2015-06-15 → 2019-01-02 · 5 obs

○ 2008-03-16 09:44:26
● 2015-06-15 13:11:44
● 2019-01-02 18:11:32
○ 2026-05-02 02:28:06
○ 2026-07-27 12:33:38

●NSns1.bdm.microsoftonline.com2026-05-02 → 2026-07-27 · 3 obs

○ 2019-01-02 18:11:32
● 2026-05-02 02:28:06
● 2026-07-27 12:33:38

○NSns1.eferi.com2008-03-16 → 2008-03-16 · 3 obs

● 2008-03-16 09:44:26
○ 2015-06-15 13:11:44
○ 2026-07-27 12:33:38

●NSns2.bdm.microsoftonline.com2026-05-02 → 2026-07-27 · 3 obs

○ 2019-01-02 18:11:32
● 2026-05-02 02:28:06
● 2026-07-27 12:33:38

○NSns2.eferi.com2008-03-16 → 2008-03-16 · 3 obs

● 2008-03-16 09:44:26
○ 2015-06-15 13:11:44
○ 2026-07-27 12:33:38

●NSns3.bdm.microsoftonline.com2026-05-02 → 2026-07-27 · 3 obs

○ 2019-01-02 18:11:32
● 2026-05-02 02:28:06
● 2026-07-27 12:33:38

●NSns3.gkg.net2026-05-02 → 2026-07-27 · 3 obs

○ 2019-01-02 18:11:32
● 2026-05-02 02:28:06
● 2026-07-27 12:33:38

●NSns4.bdm.microsoftonline.com2026-05-02 → 2026-07-27 · 3 obs

○ 2019-01-02 18:11:32
● 2026-05-02 02:28:06
● 2026-07-27 12:33:38

●NSns4.gkg.net2026-05-02 → 2026-07-27 · 3 obs

○ 2019-01-02 18:11:32
● 2026-05-02 02:28:06
● 2026-07-27 12:33:38

○MXalt1.aspmx.l.google.com2015-06-15 → 2019-01-02 · 5 obs

○ 2008-03-16 09:44:26
● 2015-06-15 13:11:44
● 2019-01-02 18:11:32
○ 2026-05-02 02:28:06
○ 2026-07-27 12:33:38

○MXalt2.aspmx.l.google.com2015-06-15 → 2019-01-02 · 5 obs

○ 2008-03-16 09:44:26
● 2015-06-15 13:11:44
● 2019-01-02 18:11:32
○ 2026-05-02 02:28:06
○ 2026-07-27 12:33:38

○MXaspmx.l.google.com2015-06-15 → 2019-01-02 · 5 obs

○ 2008-03-16 09:44:26
● 2015-06-15 13:11:44
● 2019-01-02 18:11:32
○ 2026-05-02 02:28:06
○ 2026-07-27 12:33:38

○MXaspmx2.googlemail.com2015-06-15 → 2019-01-02 · 5 obs

○ 2008-03-16 09:44:26
● 2015-06-15 13:11:44
● 2019-01-02 18:11:32
○ 2026-05-02 02:28:06
○ 2026-07-27 12:33:38

○MXaspmx3.googlemail.com2015-06-15 → 2019-01-02 · 5 obs

○ 2008-03-16 09:44:26
● 2015-06-15 13:11:44
● 2019-01-02 18:11:32
○ 2026-05-02 02:28:06
○ 2026-07-27 12:33:38

○MXtri-citycollision.com2008-03-16 → 2008-03-16 · 3 obs

● 2008-03-16 09:44:26
○ 2015-06-15 13:11:44
○ 2026-07-27 12:33:38

●MXtricitycollision-com0i.mail.protection.outlook.com2026-05-02 → 2026-07-27 · 3 obs

○ 2019-01-02 18:11:32
● 2026-05-02 02:28:06
● 2026-07-27 12:33:38

○A184.106.80.1672015-06-15 → 2016-04-13 · 5 obs

○ 2008-03-16 09:44:26
● 2015-06-15 13:11:44
● 2016-04-13 08:24:20
○ 2016-12-25 21:30:28
○ 2026-07-27 12:33:38

●A54.236.78.2122016-12-25 → 2026-07-27 · 3 obs

○ 2016-04-13 08:24:20
● 2016-12-25 21:30:28
● 2026-07-27 12:33:38

○A64.34.164.1832008-03-16 → 2008-03-16 · 3 obs

● 2008-03-16 09:44:26
○ 2015-06-15 13:11:44
○ 2026-07-27 12:33:38

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, c.gtld-servers.net, m.gtld-servers.net, f.gtld-servers.net...	-
tri-citycollision.com	ns3.gkg.net, ns4.gkg.net	-

✅ Authoritative Response

Server:149.154.59.2

NS records: ns3.gkg.net, ns4.gkg.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for tri-citycollision.com (unsigned zone)

⏱️ Timing

Total: 681ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`54.236.78.212`
NS	4	`ns4.bdm.microsoftonline.com, ns1.bdm.microsoftonline.com...`
MX	1	`tricitycollision-com0i.mail.protection.o`
TXT	3	`v=spf1 include:spf.protection.outlook.co, MS=...`
SOA	1	`ns3.gkg.net root.tri-citycollision.com`

Analysis

IP Addresses

tri-citycollision.com has exactly one IP address — 54.236.78.212.

ec2-54-236-78-212.compute-1.amazonaws.com, for instance, is one of the other host names sharing IP numbers with tri-citycollision.com.

Name Servers

tri-citycollision.com delegates authority to 6 name servers: ns3.gkg.net, ns4.gkg.net, ns1.bdm.microsoftonline.com plus 3 other.

tri-citycollision.com shares at least some of its name servers with other domains, including idaptivetraining18.com, keyresourcing.com, pcs-oc.com and two others.

These name servers are frequently paired with the name servers ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com and ns4.bdm.microsoftonline.com.

Host names pointing to two IP addresses:

ns3.gkg.net directs traffic to 149.154.59.2 and 2001:19f0:5:1c3:5400::100.

ns4.gkg.net directs traffic to 104.238.152.48 and 2001:19f0:8000:88a8:5400:ff:fe11:a867.

ns1.bdm.microsoftonline.com directs traffic to 13.107.236.208 and 2603:1061:0:700::d0.

ns2.bdm.microsoftonline.com directs traffic to 150.171.21.208 and 2620:1ec:8ec:700::d0.

ns3.bdm.microsoftonline.com directs traffic to 204.14.183.208 and 2a01:111:4000:700::d0.

ns4.bdm.microsoftonline.com directs traffic to 208.84.5.208 and 2620:1ec:bda:700::d0.