railtechnicalstrategy.com - dns.ninja

`railtechnicalstrategy.com`

DNSSEC	⚠️ Not signed
NS	`ns1-02.azure-dns.com` ⭐
		A	2603:1061:0:700::2^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-02.azure-dns.com`
		A	13.107.236.2^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-02.azure-dns.com`
NS	`ns2-02.azure-dns.net`
		A	2620:1ec:8ec:700::2^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-02.azure-dns.net`
		A	150.171.21.2^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-02.azure-dns.net`
NS	`ns3-02.azure-dns.org`
		A	2a01:111:4000:700::2^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-02.azure-dns.org`
		A	204.14.183.2^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-02.azure-dns.org`
NS	`ns4-02.azure-dns.info`
		A	2620:1ec:bda:700::2^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-02.azure-dns.info`
		A	208.84.5.2^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-02.azure-dns.info`
TXT	`v=spf1 include:_u.railtechnicalstrategy.com._spf.smart.ondmarc.com ~all`
SOA	`ns1-02.azure-dns.com`azuredns-hostmaster@microsoft.com 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=1786472854

Same first word

railtechnicalstrategy.com

DNS History

13 records (4 active, 9 former)

○NSdns0.easily.co.uk2026-04-06 → 2026-04-06 · 3 obs

○ 2017-03-18 19:44:14
● 2026-04-06 16:36:20
○ 2026-08-11 18:42:36

○NSdns1.easily.co.uk2026-04-06 → 2026-04-06 · 3 obs

○ 2017-03-18 19:44:14
● 2026-04-06 16:36:20
○ 2026-08-11 18:42:36

●NSns1-02.azure-dns.com2026-08-11 → 2026-08-11 · 2 obs

○ 2026-04-06 16:36:20
● 2026-08-11 18:42:36

●NSns2-02.azure-dns.net2026-08-11 → 2026-08-11 · 2 obs

○ 2026-04-06 16:36:20
● 2026-08-11 18:42:36

●NSns3-02.azure-dns.org2026-08-11 → 2026-08-11 · 2 obs

○ 2026-04-06 16:36:20
● 2026-08-11 18:42:36

●NSns4-02.azure-dns.info2026-08-11 → 2026-08-11 · 2 obs

○ 2026-04-06 16:36:20
● 2026-08-11 18:42:36

○NSpdns03.domaincontrol.com2015-07-19 → 2017-03-18 · 3 obs

● 2015-07-19 22:51:36
● 2017-03-18 19:44:14
○ 2026-08-11 18:42:36

○NSpdns04.domaincontrol.com2015-07-19 → 2017-03-18 · 3 obs

● 2015-07-19 22:51:36
● 2017-03-18 19:44:14
○ 2026-08-11 18:42:36

○MXmailstore1.secureserver.net2015-07-19 → 2017-03-18 · 4 obs

● 2015-07-19 22:51:36
● 2017-03-18 19:44:14
○ 2026-04-06 16:36:20
○ 2026-08-11 18:42:36

○MXsmtp.secureserver.net2015-07-19 → 2017-03-18 · 4 obs

● 2015-07-19 22:51:36
● 2017-03-18 19:44:14
○ 2026-04-06 16:36:20
○ 2026-08-11 18:42:36

○A15.197.148.332026-04-06 → 2026-06-29 · 9 obs

○ 2017-03-18 19:44:14
● 2026-04-06 16:36:20
● 2026-06-07 15:04:20
○ 2026-06-13 06:24:56
○ 2026-06-15 23:15:40
● 2026-06-21 13:11:32
○ 2026-06-25 11:28:42
● 2026-06-29 20:48:06
○ 2026-08-11 18:42:36

○A184.168.221.522015-07-19 → 2017-03-18 · 4 obs

● 2015-07-19 22:51:36
● 2017-03-18 19:44:14
○ 2026-04-06 16:36:20
○ 2026-08-11 18:42:36

○A3.33.130.1902026-04-06 → 2026-06-29 · 9 obs

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
railtechnicalstrategy.com	ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info	2 records

✅ Authoritative Response

Server:13.107.236.2

NS records: ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for railtechnicalstrategy.com (unsigned zone)

⏱️ Timing

Total: 209ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns1-02.azure-dns.com, ns2-02.azure-dns.net...`
MX	1	`. (pri: 0)`
TXT	1	`v=spf1 include:_u.railtechnicalstrategy.`
SOA	1	`ns1-02.azure-dns.com azuredns-hostmaster`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1-02.azure-dns.com, ns1-02.azure-dns.com)

Analysis

Name Servers

Four name servers handle the delegation for railtechnicalstrategy.com: ns1-02.azure-dns.com, ns4-02.azure-dns.info, ns2-02.azure-dns.net and ns3-02.azure-dns.org.

There is at least partial name server overlap between railtechnicalstrategy.com and other domains — sbp-int.com, swatchxomega.fr, limdesk.com and two more among them.

All four hostnames — ns1-02.azure-dns.com, ns4-02.azure-dns.info, ns2-02.azure-dns.net and ns3-02.azure-dns.org — resolve to two IP numbers apiece: ns1-02.azure-dns.com to 13.107.236.2 and 2603:1061:0:700::2; ns4-02.azure-dns.info to 208.84.5.2 and 2620:1ec:bda:700::2; ns2-02.azure-dns.net to 150.171.21.2 and 2620:1ec:8ec:700::2; ns3-02.azure-dns.org to 204.14.183.2 and 2a01:111:4000:700::2.