tmdata.com.br - dns.ninja

`tmdata.com.br`

DNSSEC	⚠️ Not signed
A	216.68.132.87^{🇺🇸 FUSE-NET216.68.132.0/24}
		PTR	`kore-telematics-216-68-132-87.static.fuse.net`
NS	`ns1.dnscloud.ca` ⭐
		A	2a06:fb00:2::1:10^{🇧🇬 CLOUDNSNET2a06:fb00:2::/48 ClouDNS}
			PTR	`ns1.dnscloud.ca`
		A	45.83.248.10^{🇧🇬 CLOUDNSNET45.83.248.0/24 Cloud DNS Ltd}
			PTR	`ns1.dnscloud.ca`
NS	`ns2.dnscloud.ca`
		A	2a06:fb00:2::2:10^{🇧🇬 CLOUDNSNET2a06:fb00:2::/48 ClouDNS}
			PTR	`ns2.dnscloud.ca`
		A	45.83.249.10^{🇧🇬 CLOUDNSNET45.83.249.0/24 Cloud DNS Ltd}
			PTR	`ns2.dnscloud.ca`
NS	`ns3.dnscloud.ca`
		A	2a06:fb00:2::3:10^{🇧🇬 CLOUDNSNET2a06:fb00:2::/48 ClouDNS}
			PTR	`ns3.dnscloud.ca`
		A	45.83.250.10^{🇧🇬 CLOUDNSNET45.83.250.0/24 Cloud DNS Ltd}
			PTR	`ns3.dnscloud.ca`
NS	`ns4.dnscloud.ca`
		A	2a06:fb00:2::4:10^{🇧🇬 CLOUDNSNET2a06:fb00:2::/48 ClouDNS}
			PTR	`ns4.dnscloud.ca`
		A	45.83.251.10^{🇧🇬 CLOUDNSNET45.83.251.0/24 Cloud DNS Ltd}
			PTR	`ns4.dnscloud.ca`
MX	`tmdata.com.br` ⭐
		A	216.68.132.87^{🇺🇸 FUSE-NET216.68.132.0/24}
			PTR	`kore-telematics-216-68-132-87.static.fuse.net`
MX	`aspmx.l.google.com`⁽¹⁾
		A	2607:f8b0:4004:c1b::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`wv-in-f26.1e100.net`
		A	142.251.16.26^{🇺🇸 Google142.251.16.0/24}
			PTR	`bl-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1a^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f26.1e100.net`
		A	192.178.223.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1b^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f27.1e100.net`
		A	172.253.157.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`v=spf1 include:22720.meuspf.com include:_spf.uni5.net include:_spf.google.com...`
SOA	`ns1.dnscloud.ca`support@cloudns.net 2026-07-09 #30

`com.br`

	DNSSEC	⚠️ Not signed
	NS	`a.dns.br` ⭐ ⚠️ Not in parent delegation
	NS	`b.dns.br` ⚠️ Not in parent delegation
	NS	`c.dns.br` ⚠️ Not in parent delegation
	NS	`d.dns.br` ⚠️ Not in parent delegation
	NS	`e.dns.br` ⚠️ Not in parent delegation
	NS	`f.dns.br` ⚠️ Not in parent delegation
	SOA	`a.dns.br`hostmaster@registro.br serial=2026219356

WOT: SAFE (60/100)
rank #526393 globally
rank #3738 in the tld
WOT: SAFE (69/100)

MX for

tmdata.com.br

Same first word

tmdata.com

tmdata.com.br

tmdata.be

Similar names

tadmat.com

mdatta.com

mtdata.com

mtdata.co.nz

datamt.net

matdat.org

datatm.com

mtdata.se

mtdata.net

matdat.com

tamdat.net

amdatt.com

mtdata.fi

tamtad.com

tatamd.com

matdat.net

mtdata.international

mtdata.us

mtdata.co.jp

mtdata.co.kr

datmat.com

mtdata.jp

dattam.com

datatm.ir

mattda.ly

tamdat.com

datamt.com

mtdata.com.au

mtdata.ru

matdat.se

DNS History

26 records (11 active, 15 former)

○NSbrs.poa.stech.com.br2015-10-16 → 2015-10-16 · 4 obs

○ 2015-06-13 00:27:00
● 2015-10-16 05:16:38
○ 2016-01-17 06:16:20
○ 2026-08-07 14:58:04

○NSdns1.cronic.com.br2015-06-13 → 2016-04-02 · 6 obs

● 2015-06-13 00:27:00
○ 2015-10-16 05:16:38
● 2016-01-17 06:16:20
● 2016-04-02 07:58:06
○ 2017-04-05 14:16:42
○ 2026-08-07 14:58:04

○NSdns2.cronic.com.br2015-06-13 → 2016-04-02 · 6 obs

● 2015-06-13 00:27:00
○ 2015-10-16 05:16:38
● 2016-01-17 06:16:20
● 2016-04-02 07:58:06
○ 2017-04-05 14:16:42
○ 2026-08-07 14:58:04

○NSdns3.cronic.com.br2015-06-13 → 2016-04-02 · 6 obs

● 2015-06-13 00:27:00
○ 2015-10-16 05:16:38
● 2016-01-17 06:16:20
● 2016-04-02 07:58:06
○ 2017-04-05 14:16:42
○ 2026-08-07 14:58:04

○NSdns3001.playunix.com.br2017-04-05 → 2017-07-22 · 5 obs

○ 2016-04-02 07:58:06
● 2017-04-05 14:16:42
● 2017-07-22 12:13:56
○ 2026-04-11 21:47:38
○ 2026-08-07 14:58:04

○NSdns3002.playunix.com.br2017-04-05 → 2017-07-22 · 5 obs

○ 2016-04-02 07:58:06
● 2017-04-05 14:16:42
● 2017-07-22 12:13:56
○ 2026-04-11 21:47:38
○ 2026-08-07 14:58:04

○NSdns4.cronic.com.br2015-06-13 → 2016-04-02 · 6 obs

● 2015-06-13 00:27:00
○ 2015-10-16 05:16:38
● 2016-01-17 06:16:20
● 2016-04-02 07:58:06
○ 2017-04-05 14:16:42
○ 2026-08-07 14:58:04

○NSns1.brsite.net2015-10-16 → 2015-10-16 · 4 obs

○ 2015-06-13 00:27:00
● 2015-10-16 05:16:38
○ 2016-01-17 06:16:20
○ 2026-08-07 14:58:04

●NSns1.dnscloud.ca2026-04-11 → 2026-08-07 · 3 obs

○ 2017-07-22 12:13:56
● 2026-04-11 21:47:38
● 2026-08-07 14:58:04

○NSns2.brsite.net2015-10-16 → 2015-10-16 · 4 obs

○ 2015-06-13 00:27:00
● 2015-10-16 05:16:38
○ 2016-01-17 06:16:20
○ 2026-08-07 14:58:04

●NSns2.dnscloud.ca2026-04-11 → 2026-08-07 · 3 obs

○ 2017-07-22 12:13:56
● 2026-04-11 21:47:38
● 2026-08-07 14:58:04

●NSns3.dnscloud.ca2026-04-11 → 2026-08-07 · 3 obs

○ 2017-07-22 12:13:56
● 2026-04-11 21:47:38
● 2026-08-07 14:58:04

●NSns4.dnscloud.ca2026-04-11 → 2026-08-07 · 3 obs

○ 2017-07-22 12:13:56
● 2026-04-11 21:47:38
● 2026-08-07 14:58:04

●MXalt1.aspmx.l.google.com2015-06-13 → 2026-08-07 · 2 obs

● 2015-06-13 00:27:00
● 2026-08-07 14:58:04

●MXalt2.aspmx.l.google.com2015-06-13 → 2026-08-07 · 2 obs

● 2015-06-13 00:27:00
● 2026-08-07 14:58:04

●MXalt3.aspmx.l.google.com2016-04-02 → 2026-08-07 · 3 obs

○ 2016-01-17 06:16:20
● 2016-04-02 07:58:06
● 2026-08-07 14:58:04

●MXalt4.aspmx.l.google.com2016-04-02 → 2026-08-07 · 3 obs

○ 2016-01-17 06:16:20
● 2016-04-02 07:58:06
● 2026-08-07 14:58:04

●MXaspmx.l.google.com2015-06-13 → 2026-08-07 · 2 obs

● 2015-06-13 00:27:00
● 2026-08-07 14:58:04

○MXaspmx2.googlemail.com2015-06-13 → 2016-01-17 · 4 obs

● 2015-06-13 00:27:00
● 2016-01-17 06:16:20
○ 2016-04-02 07:58:06
○ 2026-08-07 14:58:04

○MXaspmx3.googlemail.com2015-06-13 → 2016-01-17 · 4 obs

● 2015-06-13 00:27:00
● 2016-01-17 06:16:20
○ 2016-04-02 07:58:06
○ 2026-08-07 14:58:04

○MXaspmx4.googlemail.com2015-06-13 → 2016-01-17 · 4 obs

● 2015-06-13 00:27:00
● 2016-01-17 06:16:20
○ 2016-04-02 07:58:06
○ 2026-08-07 14:58:04

○MXaspmx5.googlemail.com2015-06-13 → 2016-01-17 · 4 obs

● 2015-06-13 00:27:00
● 2016-01-17 06:16:20
○ 2016-04-02 07:58:06
○ 2026-08-07 14:58:04

●MXtmdata.com.br2017-04-05 → 2026-08-07 · 3 obs

○ 2016-04-02 07:58:06
● 2017-04-05 14:16:42
● 2026-08-07 14:58:04

○A177.12.164.1112015-06-13 → 2016-04-02 · 6 obs

● 2015-06-13 00:27:00
○ 2015-10-16 05:16:38
● 2016-01-17 06:16:20
● 2016-04-02 07:58:06
○ 2017-04-05 14:16:42
○ 2026-08-07 14:58:04

○A201.20.37.242015-10-16 → 2015-10-16 · 4 obs

○ 2015-06-13 00:27:00
● 2015-10-16 05:16:38
○ 2016-01-17 06:16:20
○ 2026-08-07 14:58:04

●A216.68.132.872026-04-11 → 2026-08-07 · 3 obs

○ 2017-04-05 14:16:42
● 2026-04-11 21:47:38
● 2026-08-07 14:58:04

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
br	a.dns.br, b.dns.br, c.dns.br, d.dns.br...	-
tmdata.com.br	ns1.dnscloud.ca, ns2.dnscloud.ca, ns3.dnscloud.ca, ns4.dnscloud.ca	-

✅ Authoritative Response

Server:45.83.248.10

NS records: ns1.dnscloud.ca, ns2.dnscloud.ca, ns3.dnscloud.ca, ns4.dnscloud.ca

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for tmdata.com.br (unsigned zone)

⏱️ Timing

Total: 827ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`216.68.132.87`
NS	4	`ns4.dnscloud.ca, ns3.dnscloud.ca...`
MX	6	`alt2.aspmx.l.google.com (pri: 5), tmdata.com.br (pri: 0)...`
TXT	1	`v=spf1 include:22720.meuspf.com include:`
SOA	1	`ns1.dnscloud.ca support.cloudns.net`

Analysis

Mail Server Role

tmdata.com.br handles its own mail, functioning as its own mail server.

As mail servers, aspmx.l.google.com, alt1.aspmx.l.google.com and alt2.aspmx.l.google.com are often used in combination with tmdata.com.br.

IP Addresses

tmdata.com.br resolves to just one IP address, 216.68.132.87.

racowireless.com, kore-telematics-216-68-132-87.static.fuse.net and www.koretelematics.com are examples of other host names that share IP numbers with tmdata.com.br.

Name Servers

The NS records for tmdata.com.br point to four name servers: ns1.dnscloud.ca, ns2.dnscloud.ca, ns3.dnscloud.ca and ns4.dnscloud.ca.

tmdata.com.br has at least partial name server overlap with other domains, such as dekalbperformance.com, koredatalink.com, funxauto.com and two others.

It is common to see these name servers used together with name servers ns0.xname.org and ns1.xname.org.

ns1.dnscloud.ca, ns2.dnscloud.ca, ns3.dnscloud.ca and ns4.dnscloud.ca all point to exactly two IP numbers each: ns1.dnscloud.ca → 45.83.248.10 and 2a06:fb00:2::1:10; ns2.dnscloud.ca → 45.83.249.10 and 2a06:fb00:2::2:10; ns3.dnscloud.ca → 45.83.250.10 and 2a06:fb00:2::3:10; ns4.dnscloud.ca → 45.83.251.10 and 2a06:fb00:2::4:10.

Mail Servers

tmdata.com.br is served by 6 mail servers: tmdata.com.br, aspmx.l.google.com and alt1.aspmx.l.google.com, plus 3 more.

There is at least a partial MX overlap between tmdata.com.br and other domains, including lumbex.com, finloo.vn, ns500759.ns500759.ns500698.ns500735.ns500735.ns500736.ns500735.ns500736.ns500708.ns500708.ns500652.ns500652.trackreceptor.com and two others.

These mail servers tend to appear in combination with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.

Host names that have two IP addresses:

The A records for aspmx.l.google.com return 142.251.16.26 and 2607:f8b0:4004:c1b::1a.

The A records for alt1.aspmx.l.google.com return 108.177.123.27 and 2800:3f0:4003:c0f::1a.

The A records for alt2.aspmx.l.google.com return 172.253.116.27 and 2a00:1450:400b:c02::1a.

The A records for alt3.aspmx.l.google.com return 192.178.223.26 and 2a00:1450:4009:c0f::1a.

The A records for alt4.aspmx.l.google.com return 172.253.157.27 and 2a00:1450:400c:c23::1b.

Host names that point to one IP address:

tmdata.com.br resolves to the IP address 216.68.132.87.