tmsdispatch.com - dns.ninja

`tmsdispatch.com`

DNSSEC	⚠️ Not signed
A	66.246.117.13^{🇺🇸 NAC66.246.0.0/16 Net Access Corporation}
NS	`ns1.protectedharbor.com` ⭐
		A	206.72.207.19^{🇺🇸 NJIIX-1206.72.192.0/20 Proxy by NJIIX.NET}
			PTR	`mail.protectedharbor.com`
NS	`ns2.protectedharbor.com`
		A	100.37.134.49^{🇺🇸 AS701100.37.0.0/16 MCI Communications Services, LLC d/b/a Verizon Business}
			PTR	`mail.technologyoptimizers.com`
MX	`tmsdispatch-com.p10.mxthunder.com` ⭐
		A	108.166.161.243^{🇺🇸 COREXCHANGE-AS108.166.160.0/19 CoreXchange 1950 Stemmons Frwy Suite 4006 Dallas, TX 75207}
		A	209.41.68.240^{🇺🇸 DATABANK209.41.68.0/24}
			PTR	`bolt101b.mxthunder.net`
MX	`tmsdispatch-com.p20.mxthunder.net`⁽²⁰⁾
		A	108.166.161.243^{🇺🇸 COREXCHANGE-AS108.166.160.0/19 CoreXchange 1950 Stemmons Frwy Suite 4006 Dallas, TX 75207}
MX	`tmsdispatch-com.p30.mxthunder.net`⁽³⁰⁾
		A	209.41.68.240^{🇺🇸 DATABANK209.41.68.0/24}
			PTR	`bolt101b.mxthunder.net`
MX	`tmsdispatch-com.p40.mxthunder.net`⁽⁴⁰⁾
		A	108.166.161.243^{🇺🇸 COREXCHANGE-AS108.166.160.0/19 CoreXchange 1950 Stemmons Frwy Suite 4006 Dallas, TX 75207}
		A	209.41.68.240^{🇺🇸 DATABANK209.41.68.0/24}
			PTR	`bolt101b.mxthunder.net`
TXT	`v=spf1 ip4:206.72.207.19 a:mail.protectedharbor.com include:spf.smtp2go.com -all`
SOA	`ns1.protectedharbor.com`postmaster@netmagicpro.com 2025-11-17 #1

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

Same first word

tmsdispatch.com

Similar names

dispatchtms.com

DNS History

11 records (7 active, 4 former)

○NSns1.domain.com2017-11-05 → 2017-11-05 · 3 obs

● 2017-11-05 04:24:32
○ 2026-03-09 00:25:20
○ 2026-08-10 12:07:38

●NSns1.protectedharbor.com2026-03-09 → 2026-08-10 · 3 obs

○ 2017-11-05 04:24:32
● 2026-03-09 00:25:20
● 2026-08-10 12:07:38

○NSns2.domain.com2017-11-05 → 2017-11-05 · 3 obs

● 2017-11-05 04:24:32
○ 2026-03-09 00:25:20
○ 2026-08-10 12:07:38

●NSns2.protectedharbor.com2026-03-09 → 2026-08-10 · 3 obs

○ 2017-11-05 04:24:32
● 2026-03-09 00:25:20
● 2026-08-10 12:07:38

○MXmx.tmsdispatch.com2017-11-05 → 2017-11-05 · 3 obs

● 2017-11-05 04:24:32
○ 2026-03-09 00:25:20
○ 2026-08-10 12:07:38

●MXtmsdispatch-com.p10.mxthunder.com2026-03-09 → 2026-08-10 · 3 obs

○ 2017-11-05 04:24:32
● 2026-03-09 00:25:20
● 2026-08-10 12:07:38

●MXtmsdispatch-com.p20.mxthunder.net2026-03-09 → 2026-08-10 · 3 obs

○ 2017-11-05 04:24:32
● 2026-03-09 00:25:20
● 2026-08-10 12:07:38

●MXtmsdispatch-com.p30.mxthunder.net2026-03-09 → 2026-08-10 · 3 obs

○ 2017-11-05 04:24:32
● 2026-03-09 00:25:20
● 2026-08-10 12:07:38

●MXtmsdispatch-com.p40.mxthunder.net2026-03-09 → 2026-08-10 · 3 obs

○ 2017-11-05 04:24:32
● 2026-03-09 00:25:20
● 2026-08-10 12:07:38

●A66.246.117.132026-03-09 → 2026-08-10 · 3 obs

○ 2017-11-05 04:24:32
● 2026-03-09 00:25:20
● 2026-08-10 12:07:38

○A66.96.162.1502017-11-05 → 2017-11-05 · 3 obs

● 2017-11-05 04:24:32
○ 2026-03-09 00:25:20
○ 2026-08-10 12:07:38

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
tmsdispatch.com	ns1.protectedharbor.com, ns2.protectedharbor.com	2 records

✅ Authoritative Response

Server:100.37.134.49

NS records: ns1.protectedharbor.com, ns2.protectedharbor.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for tmsdispatch.com (unsigned zone)

⏱️ Timing

Total: 130ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`66.246.117.13`
NS	2	`ns2.protectedharbor.com, ns1.protectedharbor.com`
MX	4	`tmsdispatch-com.p10.mxthunder.com (pri: , tmsdispatch-com.p20.mxthunder.net (pri: ...`
TXT	1	`v=spf1 ip4:206.72.207.19 a:mail.protecte`
SOA	1	`ns1.protectedharbor.com postmaster.netma`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.protectedharbor.com, ns2.protectedharbor.com)

Analysis

IP Addresses

tmsdispatch.com resolves to just one IP address, 66.246.117.13.

Two other host names, along with law-mp.com, vcssoftware.com and sabatage.com, also share IP numbers with tmsdispatch.com.

Name Servers

tmsdispatch.com is delegated to two name servers: ns1.protectedharbor.com and ns2.protectedharbor.com.

tmsdispatch.com shares its NS records with other domains, for example activedirectoryhelp.com, protectedtechnology.net, investecpc.com and two others.

There is at least partial name server overlap between tmsdispatch.com and other domains — suchfeincpas.com, alanpressmandmd.com, camanet.org and two more among them.

These name servers frequently co-occur with the name servers ns1.netmagic.biz and ns2.netmagic.biz.

ns1.protectedharbor.com → 206.72.207.19 and ns2.protectedharbor.com → 100.37.134.49: one IP number per host name.

Mail Servers

Mail for tmsdispatch.com is handled by four mail servers: tmsdispatch-com.p10.mxthunder.com, tmsdispatch-com.p20.mxthunder.net, tmsdispatch-com.p30.mxthunder.net and tmsdispatch-com.p40.mxthunder.net.

Some mail servers of tmsdispatch.com are also used by other domains, notably tmshome.com and tms-digital.com.

Host names that have two IP addresses:

tmsdispatch-com.p10.mxthunder.com points to 108.166.161.243 and 209.41.68.240.

tmsdispatch-com.p40.mxthunder.net points to 108.166.161.243 and 209.41.68.240.

Host names that point to one IP address:

tmsdispatch-com.p20.mxthunder.net points to 108.166.161.243.

tmsdispatch-com.p30.mxthunder.net points to 209.41.68.240.

Each of tmsdispatch-com.p10.mxthunder.com, tmsdispatch-com.p40.mxthunder.net and tmsdispatch-com.p20.mxthunder.net resolves to 108.166.161.243.

Each of tmsdispatch-com.p10.mxthunder.com, tmsdispatch-com.p40.mxthunder.net and tmsdispatch-com.p30.mxthunder.net resolves to 209.41.68.240.