transdig.com - dns.ninja

`transdig.com`

DNSSEC	⚠️ Not signed
A	72.250.162.150^{🇺🇸 ONE-172.250.160.0/20 ONERINGNET}
NS	`ns1-07.azure-dns.com` ⭐
		A	2603:1061:0:700::7^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-07.azure-dns.com`
		A	13.107.236.7^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-07.azure-dns.com`
NS	`ns2-07.azure-dns.net`
		A	2620:1ec:8ec:700::7^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-07.azure-dns.net`
		A	150.171.21.7^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-07.azure-dns.net`
NS	`ns3-07.azure-dns.org`
		A	2a01:111:4000:700::7^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-07.azure-dns.org`
		A	204.14.183.7^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-07.azure-dns.org`
NS	`ns4-07.azure-dns.info`
		A	2620:1ec:bda:700::7^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-07.azure-dns.info`
		A	208.84.5.7^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-07.azure-dns.info`
MX	`inbound-smtp.us-east-1.amazonaws.com` ⭐
		A	3.211.210.226^{🇺🇸 Amazon3.208.0.0/12 EC2 IAD prefix}
			PTR	`ec2-3-211-210-226.compute-1.amazonaws.com`
		A	44.206.9.87^{🇺🇸 Amazon44.192.0.0/11 EC2 IAD prefix}
			PTR	`ec2-44-206-9-87.compute-1.amazonaws.com`
		A	44.210.166.32^{🇺🇸 Amazon44.192.0.0/11 EC2 IAD prefix}
			PTR	`ec2-44-210-166-32.compute-1.amazonaws.com`
		A	54.164.173.191^{🇺🇸 Amazon54.164.0.0/15 EC2 IAD prefix}
			PTR	`ec2-54-164-173-191.compute-1.amazonaws.com`
		A	54.197.5.236^{🇺🇸 Amazon54.196.0.0/15 EC2 IAD 54.196.0.0/15}
			PTR	`ec2-54-197-5-236.compute-1.amazonaws.com`
TXT	`MS=ms68132514`
SOA	`ns1-07.azure-dns.com`root@transdig.com 2007-06-25 #20

`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=1785029567

Same first word

transdig.com

Similar names

DNS History

11 records (6 active, 5 former)

●NSns1-07.azure-dns.com2026-03-25 → 2026-07-26 · 3 obs

○ 2018-09-15 23:29:50
● 2026-03-25 16:33:42
● 2026-07-26 01:40:54

○NSns1.netgainit.com2015-06-19 → 2018-09-15 · 4 obs

● 2015-06-19 13:52:12
● 2018-09-15 23:29:50
○ 2026-03-25 16:33:42
○ 2026-07-26 01:40:54

●NSns2-07.azure-dns.net2026-03-25 → 2026-07-26 · 3 obs

○ 2018-09-15 23:29:50
● 2026-03-25 16:33:42
● 2026-07-26 01:40:54

○NSns2.netgainit.com2015-06-19 → 2018-09-15 · 4 obs

● 2015-06-19 13:52:12
● 2018-09-15 23:29:50
○ 2026-03-25 16:33:42
○ 2026-07-26 01:40:54

●NSns3-07.azure-dns.org2026-03-25 → 2026-07-26 · 3 obs

○ 2018-09-15 23:29:50
● 2026-03-25 16:33:42
● 2026-07-26 01:40:54

●NSns4-07.azure-dns.info2026-03-25 → 2026-07-26 · 3 obs

○ 2018-09-15 23:29:50
● 2026-03-25 16:33:42
● 2026-07-26 01:40:54

●MXinbound-smtp.us-east-1.amazonaws.com2026-03-25 → 2026-07-26 · 3 obs

○ 2018-09-15 23:29:50
● 2026-03-25 16:33:42
● 2026-07-26 01:40:54

○MXmail.global.frontbridge.com2015-06-19 → 2015-11-20 · 4 obs

● 2015-06-19 13:52:12
● 2015-11-20 09:03:08
○ 2016-01-10 14:49:56
○ 2026-07-26 01:40:54

○MXwebmail.netgainit.com2016-01-10 → 2018-09-15 · 5 obs

○ 2015-11-20 09:03:08
● 2016-01-10 14:49:56
● 2018-09-15 23:29:50
○ 2026-03-25 16:33:42
○ 2026-07-26 01:40:54

○A64.191.157.552015-06-19 → 2016-04-03 · 4 obs

● 2015-06-19 13:52:12
● 2016-04-03 16:21:22
○ 2018-09-15 23:29:50
○ 2026-07-26 01:40:54

●A72.250.162.1502018-09-15 → 2026-07-26 · 3 obs

○ 2016-04-03 16:21:22
● 2018-09-15 23:29:50
● 2026-07-26 01:40:54

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	c.gtld-servers.net, d.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net...	-
transdig.com	ns1-07.azure-dns.com, ns2-07.azure-dns.net, ns3-07.azure-dns.org, ns4-07.azure-dns.info	2 records

✅ Authoritative Response

Server:13.107.236.7

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for transdig.com (unsigned zone)

⏱️ Timing

Total: 231ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`72.250.162.150`
NS	4	`ns1-07.azure-dns.com, ns2-07.azure-dns.net...`
MX	1	`inbound-smtp.us-east-1.amazonaws.com (pr`
TXT	1	`MS=ms68132514`
SOA	1	`ns1-07.azure-dns.com root.transdig.com`

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

transdig.com resolves to just one IP address, 72.250.162.150.

ncdtech.com, for instance, is one of the other host names sharing IP numbers with transdig.com.

Name Servers

The NS records for transdig.com point to four name servers: ns1-07.azure-dns.com, ns4-07.azure-dns.info, ns2-07.azure-dns.net and ns3-07.azure-dns.org.

There is at least partial name server overlap between transdig.com and other domains — ia7.nz, metrics.ingest.monitor.azure.com, binganddecide.jp and two more among them.

All four hostnames — ns1-07.azure-dns.com, ns4-07.azure-dns.info, ns2-07.azure-dns.net and ns3-07.azure-dns.org — resolve to two IP numbers apiece: ns1-07.azure-dns.com to 13.107.236.7 and 2603:1061:0:700::7; ns4-07.azure-dns.info to 208.84.5.7 and 2620:1ec:bda:700::7; ns2-07.azure-dns.net to 150.171.21.7 and 2620:1ec:8ec:700::7; ns3-07.azure-dns.org to 204.14.183.7 and 2a01:111:4000:700::7.

Mail Servers

The sole mail server for transdig.com is inbound-smtp.us-east-1.amazonaws.com.

Among the domains sharing a mail server setup with transdig.com are tridentsys.net, turningtechnologies.eu, orio.io and two others.

There is at least a partial MX overlap between transdig.com and other domains, including wingsperiscope.atlassian.net, essvote.atlassian.net, wahanda.atlassian.net and two others.

These mail servers often co-occur with the mail servers inbound-smtp.us-west-2.amazonaws.com.

inbound-smtp.us-east-1.amazonaws.com directs to five IP numbers: 3.211.210.226, 44.206.9.87, 44.210.166.32 and two others.