`telematicspartner.com`

DNSSEC	⚠️ Not signed
A	13.248.169.48^{🇺🇸 Amazon13.248.160.0/20}
		PTR	`a904c694c05102f30.awsglobalaccelerator.com`
A	76.223.54.146^{🇺🇸 Amazon76.223.48.0/20}
NS	`ns1.afternic.com` ⭐
		A	2603:5:2126::45^{🇺🇸 GODADDY-DNS2603:5:2120::/44}
			PTR	`ns1.afternic.com`
		A	97.74.98.69^{🇺🇸 GODADDY-DNS97.74.98.0/23}
			PTR	`ns1.afternic.com`
NS	`ns2.afternic.com`
		A	2603:5:2226::45^{🇺🇸 GODADDY-DNS2603:5:2220::/44}
			PTR	`ns2.afternic.com`
		A	173.201.66.69^{🇺🇸 GODADDY-DNS173.201.66.0/23}
			PTR	`ns2.afternic.com`
NS	`verification-d3jclucsp89ganyqbydeny.ns101.verify.hn` ⚠️ Not in zone NS records
		A	13.248.169.48^{🇺🇸 Amazon13.248.160.0/20}
			PTR	`a904c694c05102f30.awsglobalaccelerator.com`
		A	76.223.54.146^{🇺🇸 Amazon76.223.48.0/20}
			PTR	`a904c694c05102f30.awsglobalaccelerator.com`
TXT	`v=spf1 -all`
SOA	`ns1.afternic.com`dns@jomax.net serial=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=1776100932

Same first word

telematicspartner.com

DNS History

12 records (5 active, 7 former)

●NSns1.afternic.com2026-03-14 → 2026-04-13 · 3 obs

○ 2017-04-08 07:30:06
● 2026-03-14 15:57:50
● 2026-04-13 17:33:18

●NSns2.afternic.com2026-03-14 → 2026-04-13 · 3 obs

○ 2017-04-08 07:30:06
● 2026-03-14 15:57:50
● 2026-04-13 17:33:18

○NSns55.1und1.de2015-08-03 → 2017-04-08 · 4 obs

● 2015-08-03 13:50:40
● 2017-04-08 07:30:06
○ 2026-03-14 15:57:50
○ 2026-04-13 17:33:18

○NSns56.1und1.de2015-08-03 → 2017-04-08 · 4 obs

● 2015-08-03 13:50:40
● 2017-04-08 07:30:06
○ 2026-03-14 15:57:50
○ 2026-04-13 17:33:18

●NSverification-d3jclucsp89ganyqbydeny.ns101.verify.hn2026-03-14 → 2026-04-13 · 3 obs

○ 2017-04-08 07:30:06
● 2026-03-14 15:57:50
● 2026-04-13 17:33:18

○MX.2026-03-14 → 2026-04-13 · 2 obs

○ 2026-03-14 15:57:50
○ 2026-04-13 17:33:18

○MXmx00.kundenserver.de2015-08-03 → 2017-04-08 · 4 obs

● 2015-08-03 13:50:40
● 2017-04-08 07:30:06
○ 2026-03-14 15:57:50
○ 2026-04-13 17:33:18

○MXmx01.kundenserver.de2015-08-03 → 2017-04-08 · 4 obs

● 2015-08-03 13:50:40
● 2017-04-08 07:30:06
○ 2026-03-14 15:57:50
○ 2026-04-13 17:33:18

●A13.248.169.482026-03-14 → 2026-04-13 · 3 obs

○ 2017-04-08 07:30:06
● 2026-03-14 15:57:50
● 2026-04-13 17:33:18

○A217.160.233.1422016-07-12 → 2017-04-08 · 5 obs

○ 2016-03-09 21:08:30
● 2016-07-12 13:59:48
● 2017-04-08 07:30:06
○ 2026-03-14 15:57:50
○ 2026-04-13 17:33:18

●A76.223.54.1462026-03-14 → 2026-04-13 · 3 obs

○ 2017-04-08 07:30:06
● 2026-03-14 15:57:50
● 2026-04-13 17:33:18

○A82.165.209.862015-08-03 → 2016-03-09 · 4 obs

● 2015-08-03 13:50:40
● 2016-03-09 21:08:30
○ 2016-07-12 13:59:48
○ 2026-04-13 17:33:18

🔍 DNS Trace

Analysis

IP Addresses

telematicspartner.com points to two IPs: 13.248.169.48 and 76.223.54.146.

Other host names, for instance lasecurityservices.com, www.baesel.com, mail.frenchholidayhouses.com, atot.net and avaloncorp.com share IP numbers with telematicspartner.com.

Name Servers

telematicspartner.com is delegated to name servers ns1.afternic.com, ns2.afternic.com and verification-d3jclucsp89ganyqbydeny.ns101.verify.hn.

telematicspartner.com at least partially shares name servers with other domains such as modelnexus.com, 2a.logika.sitex.us, mte.xbox.uhqh.com, smtp2.synertiq.com and dc.seomarketing.la.

These name servers are commonly used with verification-iryqusbri9xlks4ssi7d4w.ns101.verify.hn and verification-ycbo3rwb8mhutnirdaxagl.ns101.verify.hn.

Host names with two IP numbers:

ns1.afternic.com points to 2603:5:2126::45 and 97.74.98.69.

ns2.afternic.com points to 2603:5:2226::45 and 173.201.66.69.

verification-d3jclucsp89ganyqbydeny.ns101.verify.hn points to 13.248.169.48 and 76.223.54.146.

telematicspartner.com - robtex.com