in2motion.com - dns.ninja

`in2motion.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	`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	`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	`verification-vesbet7nkettdw2mc9cgox.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	`ns2.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=1784955312

Same first word

in2motion.com.au

in2motion.eu

in2motion.dk

in2motion.com

in2motion.de

Similar names

2inmotion.de

DNS History

25 records (5 active, 20 former)

○NSbuy.internettraffic.com2015-07-09 → 2015-07-09 · 4 obs

○ 2008-03-09 19:46:04
● 2015-07-09 20:20:52
○ 2015-11-10 11:43:14
○ 2026-07-25 05:10:38

●NSns1.afternic.com2026-03-31 → 2026-07-25 · 3 obs

○ 2018-11-08 09:01:54
● 2026-03-31 02:49:58
● 2026-07-25 05:10:38

○NSns1.sedoparking.com2015-11-10 → 2017-02-05 · 5 obs

○ 2015-07-09 20:20:52
● 2015-11-10 11:43:14
● 2017-02-05 11:41:28
○ 2018-11-08 09:01:54
○ 2026-07-25 05:10:38

○NSns1.serverhome.com2008-03-09 → 2008-03-09 · 3 obs

● 2008-03-09 19:46:04
○ 2015-07-09 20:20:52
○ 2026-07-25 05:10:38

●NSns2.afternic.com2026-03-31 → 2026-07-25 · 3 obs

○ 2018-11-08 09:01:54
● 2026-03-31 02:49:58
● 2026-07-25 05:10:38

○NSns2.sedoparking.com2015-11-10 → 2017-02-05 · 5 obs

○ 2015-07-09 20:20:52
● 2015-11-10 11:43:14
● 2017-02-05 11:41:28
○ 2018-11-08 09:01:54
○ 2026-07-25 05:10:38

○NSns2.serverhome.com2008-03-09 → 2008-03-09 · 3 obs

● 2008-03-09 19:46:04
○ 2015-07-09 20:20:52
○ 2026-07-25 05:10:38

○NSns63.domaincontrol.com2018-11-08 → 2018-11-08 · 4 obs

○ 2017-02-05 11:41:28
● 2018-11-08 09:01:54
○ 2026-03-31 02:49:58
○ 2026-07-25 05:10:38

○NSns64.domaincontrol.com2018-11-08 → 2018-11-08 · 4 obs

○ 2017-02-05 11:41:28
● 2018-11-08 09:01:54
○ 2026-03-31 02:49:58
○ 2026-07-25 05:10:38

○NSsell.internettraffic.com2015-07-09 → 2015-07-09 · 4 obs

○ 2008-03-09 19:46:04
● 2015-07-09 20:20:52
○ 2015-11-10 11:43:14
○ 2026-07-25 05:10:38

●NSverification-vesbet7nkettdw2mc9cgox.ns101.verify.hn2026-03-31 → 2026-07-25 · 3 obs

○ 2018-11-08 09:01:54
● 2026-03-31 02:49:58
● 2026-07-25 05:10:38

○MXlocalhost2017-02-05 → 2017-02-05 · 4 obs

○ 2016-04-18 08:24:38
● 2017-02-05 11:41:28
○ 2018-11-08 09:01:54
○ 2026-07-25 05:10:38

○MXmail.nickstel.com2015-11-10 → 2016-04-18 · 4 obs

● 2015-11-10 11:43:14
● 2016-04-18 08:24:38
○ 2017-02-05 11:41:28
○ 2026-07-25 05:10:38

●A13.248.169.482026-03-31 → 2026-07-25 · 3 obs

○ 2018-11-08 09:01:54
● 2026-03-31 02:49:58
● 2026-07-25 05:10:38

○A184.168.221.822018-11-08 → 2018-11-08 · 4 obs

○ 2017-02-05 11:41:28
● 2018-11-08 09:01:54
○ 2026-03-31 02:49:58
○ 2026-07-25 05:10:38

○A184.168.221.852018-11-08 → 2018-11-08 · 4 obs

○ 2017-02-05 11:41:28
● 2018-11-08 09:01:54
○ 2026-03-31 02:49:58
○ 2026-07-25 05:10:38

○A184.168.221.952018-11-08 → 2018-11-08 · 4 obs

○ 2017-02-05 11:41:28
● 2018-11-08 09:01:54
○ 2026-03-31 02:49:58
○ 2026-07-25 05:10:38

○A50.63.202.652018-11-08 → 2018-11-08 · 4 obs

○ 2017-02-05 11:41:28
● 2018-11-08 09:01:54
○ 2026-03-31 02:49:58
○ 2026-07-25 05:10:38

○A50.63.202.672018-11-08 → 2018-11-08 · 4 obs

○ 2017-02-05 11:41:28
● 2018-11-08 09:01:54
○ 2026-03-31 02:49:58
○ 2026-07-25 05:10:38

○A50.63.202.942018-11-08 → 2018-11-08 · 4 obs

○ 2017-02-05 11:41:28
● 2018-11-08 09:01:54
○ 2026-03-31 02:49:58
○ 2026-07-25 05:10:38

○A50.63.202.952018-11-08 → 2018-11-08 · 4 obs

○ 2017-02-05 11:41:28
● 2018-11-08 09:01:54
○ 2026-03-31 02:49:58
○ 2026-07-25 05:10:38

○A66.45.246.1382008-03-09 → 2008-03-09 · 3 obs

● 2008-03-09 19:46:04
○ 2015-07-09 20:20:52
○ 2026-07-25 05:10:38

○A69.172.201.2082015-07-09 → 2015-07-09 · 4 obs

○ 2008-03-09 19:46:04
● 2015-07-09 20:20:52
○ 2015-11-10 11:43:14
○ 2026-07-25 05:10:38

○A72.52.4.1212015-11-10 → 2017-02-05 · 5 obs

○ 2015-07-09 20:20:52
● 2015-11-10 11:43:14
● 2017-02-05 11:41:28
○ 2018-11-08 09:01:54
○ 2026-07-25 05:10:38

●A76.223.54.1462026-03-31 → 2026-07-25 · 3 obs

○ 2018-11-08 09:01:54
● 2026-03-31 02:49:58
● 2026-07-25 05:10:38

🔍 DNS Trace

Analysis

IP Addresses

in2motion.com resolves to the IP addresses 13.248.169.48 and 76.223.54.146

Two other host names, along with taurusbuilding.com, cyberdj.com and bpm.cc, also share IP numbers with in2motion.com.

Name Servers

DNS for in2motion.com is handled by three authoritative name servers: ns1.afternic.com, ns2.afternic.com and verification-vesbet7nkettdw2mc9cgox.ns101.verify.hn.

in2motion.com has at least partial name server overlap with other domains, such as datarecoverynearme.com, ccks.org, www.shelters-of-texas.com and two others.

It is common to see these name servers used together with name servers verification-9deuajwbjerwhjhfxwztav.ns101.verify.hn and verification-ag3xtxqjhqhiyarqdrht2l.ns101.verify.hn.

Three hostnames — ns1.afternic.com, ns2.afternic.com and verification-vesbet7nkettdw2mc9cgox.ns101.verify.hn — each have two IP addresses: ns1.afternic.com has 97.74.98.69 and 2603:5:2126::45, ns2.afternic.com has 173.201.66.69 and 2603:5:2226::45, and verification-vesbet7nkettdw2mc9cgox.ns101.verify.hn has 13.248.169.48 and 76.223.54.146.