devnimble.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`devnimble.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	`ms-domain-verification=086ba479-7997-421c-a648-9a76e8d4e365`
TXT	`v=spf1 include:spf.protection.outlook.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=1787133519

Same first word

devnimble.com

Similar names

nimbledev.com

Previous names

Next names

DNS History

9 records (4 active, 5 former)

○NSns-1194.awsdns-21.org2015-07-02 → 2017-04-19 · 4 obs

● 2015-07-02 04:15:36
● 2017-04-19 20:29:44
○ 2026-08-18 15:02:14
○ 2026-08-19 10:07:06

○NSns-2045.awsdns-63.co.uk2015-07-02 → 2017-04-19 · 4 obs

● 2015-07-02 04:15:36
● 2017-04-19 20:29:44
○ 2026-08-18 15:02:14
○ 2026-08-19 10:07:06

○NSns-356.awsdns-44.com2015-07-02 → 2017-04-19 · 4 obs

● 2015-07-02 04:15:36
● 2017-04-19 20:29:44
○ 2026-08-18 15:02:14
○ 2026-08-19 10:07:06

○NSns-635.awsdns-15.net2015-07-02 → 2017-04-19 · 4 obs

● 2015-07-02 04:15:36
● 2017-04-19 20:29:44
○ 2026-08-18 15:02:14
○ 2026-08-19 10:07:06

●NSns1-02.azure-dns.com2026-08-18 → 2026-08-19 · 3 obs

○ 2017-04-19 20:29:44
● 2026-08-18 15:02:14
● 2026-08-19 10:07:06

●NSns2-02.azure-dns.net2026-08-18 → 2026-08-19 · 3 obs

○ 2017-04-19 20:29:44
● 2026-08-18 15:02:14
● 2026-08-19 10:07:06

●NSns3-02.azure-dns.org2026-08-18 → 2026-08-19 · 3 obs

○ 2017-04-19 20:29:44
● 2026-08-18 15:02:14
● 2026-08-19 10:07:06

●NSns4-02.azure-dns.info2026-08-18 → 2026-08-19 · 3 obs

○ 2017-04-19 20:29:44
● 2026-08-18 15:02:14
● 2026-08-19 10:07:06

○A127.0.0.12015-07-02 → 2017-04-19 · 4 obs

● 2015-07-02 04:15:36
● 2017-04-19 20:29:44
○ 2026-08-18 15:02:14
○ 2026-08-19 10:07:06

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, a.gtld-servers.net...	-
devnimble.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 devnimble.com (unsigned zone)

⏱️ Timing

Total: 278ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns1-02.azure-dns.com, ns2-02.azure-dns.net...`
TXT	2	`ms-domain-verification=086ba479-7997-421, v=spf1 include:spf.protection.outlook.co`
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

The NS records for devnimble.com point to four name servers: 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 devnimble.com and other domains — frogsitefurnishings.com, danvals.se, volvia.no 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.