`inrosoftware.net`

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`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c0b::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bj-in-f26.1e100.net`
		A	142.251.111.26^{🇺🇸 Google142.251.111.0/24}
			PTR	`bk-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.26^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1a^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f26.1e100.net`
		A	192.178.223.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f26.1e100.net`
		A	172.253.157.26^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f26.1e100.net`
TXT	`9shcyfct3y7f9cljgkj9vfd42yj8zfps`
TXT	`v=spf1 include:_spf.google.com ~all`
SOA	`ns1-02.azure-dns.com`azuredns-hostmaster@microsoft.com serial=1

`net`

	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=1785573987

Same first word

inrosoftware.net

inrosoftware.com

Similar names

niaforestrow.co.uk

ironsoftware.de

wooftrainers.com

ironsoftware.com

DNS History

11 records (9 active, 2 former)

●NSns1-02.azure-dns.com2026-03-27 → 2026-08-01 · 3 obs

○ 2018-01-28 04:09:40
● 2026-03-27 13:43:54
● 2026-08-01 08:52:58

○NSns1.io-servers.com2017-01-04 → 2018-01-28 · 4 obs

● 2017-01-04 12:09:08
● 2018-01-28 04:09:40
○ 2026-03-27 13:43:54
○ 2026-08-01 08:52:58

●NSns2-02.azure-dns.net2026-03-27 → 2026-08-01 · 3 obs

○ 2018-01-28 04:09:40
● 2026-03-27 13:43:54
● 2026-08-01 08:52:58

○NSns2.io-servers.com2017-01-04 → 2018-01-28 · 4 obs

● 2017-01-04 12:09:08
● 2018-01-28 04:09:40
○ 2026-03-27 13:43:54
○ 2026-08-01 08:52:58

●NSns3-02.azure-dns.org2026-03-27 → 2026-08-01 · 3 obs

○ 2018-01-28 04:09:40
● 2026-03-27 13:43:54
● 2026-08-01 08:52:58

●NSns4-02.azure-dns.info2026-03-27 → 2026-08-01 · 3 obs

○ 2018-01-28 04:09:40
● 2026-03-27 13:43:54
● 2026-08-01 08:52:58

●MXalt1.aspmx.l.google.com2017-01-04 → 2026-08-01 · 2 obs

● 2017-01-04 12:09:08
● 2026-08-01 08:52:58

●MXalt2.aspmx.l.google.com2017-01-04 → 2026-08-01 · 2 obs

● 2017-01-04 12:09:08
● 2026-08-01 08:52:58

●MXalt3.aspmx.l.google.com2017-01-04 → 2026-08-01 · 2 obs

● 2017-01-04 12:09:08
● 2026-08-01 08:52:58

●MXalt4.aspmx.l.google.com2017-01-04 → 2026-08-01 · 2 obs

● 2017-01-04 12:09:08
● 2026-08-01 08:52:58

●MXaspmx.l.google.com2017-01-04 → 2026-08-01 · 2 obs

● 2017-01-04 12:09:08
● 2026-08-01 08:52:58

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	c.gtld-servers.net, a.gtld-servers.net, d.gtld-servers.net, k.gtld-servers.net...	-
inrosoftware.net	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 inrosoftware.net (unsigned zone)

⏱️ Timing

Total: 507ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns1-02.azure-dns.com, ns2-02.azure-dns.net...`
MX	5	`aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)...`
TXT	2	`9shcyfct3y7f9cljgkj9vfd42yj8zfps, v=spf1 include:_spf.google.com ~all`
SOA	1	`ns1-02.azure-dns.com azuredns-hostmaster`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns2-02.azure-dns.net, ns2-02.azure-dns.net)

Analysis

Name Servers

inrosoftware.net has four authoritative name servers: ns1-02.azure-dns.com, ns4-02.azure-dns.info, ns2-02.azure-dns.net and ns3-02.azure-dns.org.

The name servers of inrosoftware.net overlap at least partially with those of other domains — among them rejoice.my, microkinect.com, mudgeestorageunits.com.au and two more.

Each of the four hosts ns1-02.azure-dns.com, ns4-02.azure-dns.info, ns2-02.azure-dns.net and ns3-02.azure-dns.org has two IP addresses. ns1-02.azure-dns.com points to 13.107.236.2 and 2603:1061:0:700::2. ns4-02.azure-dns.info points to 208.84.5.2 and 2620:1ec:bda:700::2. ns2-02.azure-dns.net points to 150.171.21.2 and 2620:1ec:8ec:700::2. ns3-02.azure-dns.org points to 204.14.183.2 and 2a01:111:4000:700::2.