trainsync.com - dns.ninja

trainsync.com

DNSSEC⚠️ Not signed
A52.20.84.62πŸ‡ΊπŸ‡Έ Amazon52.20.0.0/14 EC2 IAD prefix
PTRec2-52-20-84-62.compute-1.amazonaws.com
NSns1.atom.com ⭐
A44.219.81.145πŸ‡ΊπŸ‡Έ Amazon44.192.0.0/11 EC2 IAD prefix
PTRec2-44-219-81-145.compute-1.amazonaws.com
NSns2.atom.com
A50.19.240.86πŸ‡ΊπŸ‡Έ Amazon50.19.128.0/17 EC2 IAD prefix
PTRec2-50-19-240-86.compute-1.amazonaws.com
SOAns1.atom.comhostmaster@trainsync.com 2024-11-19 #4

com

Same first word

Similar names

DNS History

24 records (3 active, 21 former)

200920112013201520172019202120232025NSns1.atom.comns2.atom.comns1.everydns.netns1.namebrightdns.comns2.everydns.netns2.namebrightdns.comns3.everydns.netns4.everydns.netnsg1.namebrightdns.comnsg2.namebrightdns.comMXanmail.namebrightmail.comA52.20.84.62107.23.42.5052.1.32.2552.200.243.12352.73.136.14054.152.144.24354.174.31.25454.208.74.21554.88.133.9271.80.232.164CNAMEhdredirect-lb-399551664.us-east-1.elb.amazonaws.comhdredirect-lb3-890977680.us-east-1.elb.amazonaws.comhdredirect-lb5-1afb6e2973825a56.elb.us-east-1.amazonaws.com
●NSns1.atom.com2026-03-08 β†’ 2026-06-21 Β· 3 obs
β—‹ 2020-02-15 15:53:56
● 2026-03-08 02:22:04
● 2026-06-21 01:39:30
β—‹NSns1.everydns.net2008-03-18 β†’ 2008-03-18 Β· 3 obs
● 2008-03-18 19:18:36
β—‹ 2015-08-07 18:22:58
β—‹ 2026-06-21 01:39:30
β—‹NSns1.namebrightdns.com2015-08-07 β†’ 2020-02-15 Β· 7 obs
β—‹ 2008-03-18 19:18:36
● 2015-08-07 18:22:58
β—‹ 2015-11-10 05:57:06
● 2016-02-25 18:25:34
● 2020-02-15 15:53:56
β—‹ 2026-03-08 02:22:04
β—‹ 2026-06-21 01:39:30
●NSns2.atom.com2026-03-08 β†’ 2026-06-21 Β· 3 obs
β—‹ 2020-02-15 15:53:56
● 2026-03-08 02:22:04
● 2026-06-21 01:39:30
β—‹NSns2.everydns.net2008-03-18 β†’ 2008-03-18 Β· 3 obs
● 2008-03-18 19:18:36
β—‹ 2015-08-07 18:22:58
β—‹ 2026-06-21 01:39:30
β—‹NSns2.namebrightdns.com2016-02-25 β†’ 2020-02-15 Β· 5 obs
β—‹ 2015-11-10 05:57:06
● 2016-02-25 18:25:34
● 2020-02-15 15:53:56
β—‹ 2026-03-08 02:22:04
β—‹ 2026-06-21 01:39:30
β—‹NSns3.everydns.net2008-03-18 β†’ 2008-03-18 Β· 3 obs
● 2008-03-18 19:18:36
β—‹ 2015-08-07 18:22:58
β—‹ 2026-06-21 01:39:30
β—‹NSns4.everydns.net2008-03-18 β†’ 2008-03-18 Β· 3 obs
● 2008-03-18 19:18:36
β—‹ 2015-08-07 18:22:58
β—‹ 2026-06-21 01:39:30
β—‹NSnsg1.namebrightdns.com2015-08-07 β†’ 2015-11-10 Β· 5 obs
β—‹ 2008-03-18 19:18:36
● 2015-08-07 18:22:58
● 2015-11-10 05:57:06
β—‹ 2016-02-25 18:25:34
β—‹ 2026-06-21 01:39:30
β—‹NSnsg2.namebrightdns.com2015-08-07 β†’ 2015-11-10 Β· 5 obs
β—‹ 2008-03-18 19:18:36
● 2015-08-07 18:22:58
● 2015-11-10 05:57:06
β—‹ 2016-02-25 18:25:34
β—‹ 2026-06-21 01:39:30
β—‹MXanmail.namebrightmail.com2015-08-07 β†’ 2015-08-07 Β· 4 obs
β—‹ 2008-03-18 19:18:36
● 2015-08-07 18:22:58
β—‹ 2015-11-10 05:57:06
β—‹ 2026-06-21 01:39:30
β—‹A107.23.42.502016-02-25 β†’ 2016-02-25 Β· 4 obs
β—‹ 2015-11-10 05:57:06
● 2016-02-25 18:25:34
β—‹ 2016-06-23 18:08:42
β—‹ 2026-06-21 01:39:30
β—‹A52.1.32.252017-02-08 β†’ 2017-02-08 Β· 4 obs
β—‹ 2016-06-23 18:08:42
● 2017-02-08 01:11:18
β—‹ 2020-02-15 15:53:56
β—‹ 2026-06-21 01:39:30
●A52.20.84.622026-03-08 β†’ 2026-06-21 Β· 3 obs
β—‹ 2020-02-15 15:53:56
● 2026-03-08 02:22:04
● 2026-06-21 01:39:30
β—‹A52.200.243.1232016-06-23 β†’ 2016-06-23 Β· 4 obs
β—‹ 2016-02-25 18:25:34
● 2016-06-23 18:08:42
β—‹ 2017-02-08 01:11:18
β—‹ 2026-06-21 01:39:30
β—‹A52.73.136.1402016-02-25 β†’ 2016-02-25 Β· 4 obs
β—‹ 2015-11-10 05:57:06
● 2016-02-25 18:25:34
β—‹ 2016-06-23 18:08:42
β—‹ 2026-06-21 01:39:30
β—‹A54.152.144.2432016-06-23 β†’ 2016-06-23 Β· 4 obs
β—‹ 2016-02-25 18:25:34
● 2016-06-23 18:08:42
β—‹ 2017-02-08 01:11:18
β—‹ 2026-06-21 01:39:30
β—‹A54.174.31.2542015-08-07 β†’ 2015-11-10 Β· 5 obs
β—‹ 2008-03-18 19:18:36
● 2015-08-07 18:22:58
● 2015-11-10 05:57:06
β—‹ 2016-02-25 18:25:34
β—‹ 2026-06-21 01:39:30
β—‹A54.208.74.2152015-08-07 β†’ 2015-11-10 Β· 5 obs
β—‹ 2008-03-18 19:18:36
● 2015-08-07 18:22:58
● 2015-11-10 05:57:06
β—‹ 2016-02-25 18:25:34
β—‹ 2026-06-21 01:39:30
β—‹A54.88.133.922017-02-08 β†’ 2017-02-08 Β· 4 obs
β—‹ 2016-06-23 18:08:42
● 2017-02-08 01:11:18
β—‹ 2020-02-15 15:53:56
β—‹ 2026-06-21 01:39:30
β—‹A71.80.232.1642008-03-18 β†’ 2008-03-18 Β· 3 obs
● 2008-03-18 19:18:36
β—‹ 2015-08-07 18:22:58
β—‹ 2026-06-21 01:39:30
β—‹CNAMEhdredirect-lb-399551664.us-east-1.elb.amazonaws.com2015-08-07 β†’ 2016-06-23 Β· 5 obs
β—‹ 2008-03-18 19:18:36
● 2015-08-07 18:22:58
● 2016-06-23 18:08:42
β—‹ 2017-02-08 01:11:18
β—‹ 2026-06-21 01:39:30
β—‹CNAMEhdredirect-lb3-890977680.us-east-1.elb.amazonaws.com2017-02-08 β†’ 2017-02-08 Β· 4 obs
β—‹ 2016-06-23 18:08:42
● 2017-02-08 01:11:18
β—‹ 2020-02-15 15:53:56
β—‹ 2026-06-21 01:39:30
β—‹CNAMEhdredirect-lb5-1afb6e2973825a56.elb.us-east-1.amazonaws.com2020-02-15 β†’ 2020-02-15 Β· 4 obs
β—‹ 2017-02-08 01:11:18
● 2020-02-15 15:53:56
β—‹ 2026-03-08 02:22:04
β—‹ 2026-06-21 01:39:30

πŸ” DNS Trace

Analysis

IP Addresses

trainsync.com resolves to one IP address: 52.20.84.62.

eloxa.com, www.teraba.com, heartecology.com and two other host names share IP numbers with trainsync.com.

Name Servers

trainsync.com is served by two delegated name servers, ns1.atom.com and ns2.atom.com.

trainsync.com uses the same name servers as several other domains β€” among them loftpay.com, sakefest.com, lucizan.com and two more.

The name servers of trainsync.com overlap at least partially with those of other domains β€” among them dexreview.com, torlun.com, careerform.com and two more.

These name servers commonly appear alongside the name servers ns1.afternic.com and ns2.afternic.com.

Both ns1.atom.com and ns2.atom.com have a single IP address each β€” ns1.atom.com resolves to 44.219.81.145 while ns2.atom.com resolves to 50.19.240.86.