insecure.computer - dns.ninja

`insecure.computer`

DNSSEC	⚠️ Not signed
NS	`ns-1382.awsdns-44.org` ⭐
		A	2600:9000:5305:6600::1^{🇺🇸 Amazon2600:9000:5305::/48 - CloudFront}
			PTR	`ns-1382.awsdns-44.org`
		A	205.251.197.102^{🇺🇸 Amazon205.251.197.0/24 prefix}
			PTR	`ns-1382.awsdns-44.org`
NS	`ns-1952.awsdns-52.co.uk`
		A	2600:9000:5307:a000::1^{🇺🇸 Amazon2600:9000:5307::/48 - CloudFront}
			PTR	`ns-1952.awsdns-52.co.uk`
		A	205.251.199.160^{🇺🇸 Amazon205.251.199.0/24 prefix}
			PTR	`ns-1952.awsdns-52.co.uk`
NS	`ns-651.awsdns-17.net`
		A	2600:9000:5302:8b00::1^{🇺🇸 Amazon2600:9000:5302::/48 - CloudFront}
			PTR	`ns-651.awsdns-17.net`
		A	205.251.194.139^{🇺🇸 Amazon205.251.194.0/24 prefix}
			PTR	`ns-651.awsdns-17.net`
NS	`ns-90.awsdns-11.com`
		A	2600:9000:5300:5a00::1^{🇺🇸 Amazon2600:9000:5300::/48 - CloudFront}
			PTR	`ns-90.awsdns-11.com`
		A	205.251.192.90^{🇺🇸 Amazon205.251.192.0/24 prefix}
			PTR	`ns-90.awsdns-11.com`
MX	`mx.insecure.computer` ⭐
		A	50.208.29.237^{🇺🇸 COMCAST-IBONE50.128.0.0/9 Comcast Cable Communications, Inc. 1800 Bishops Gate Blvd Mount Laurel, NJ 08054}
SOA	`ns-1382.awsdns-44.org`awsdns-hostmaster@amazon.com serial=1

`computer`

	DNSSEC	🔒 Signed (DS record present)
	NS	`v0n0.nic.computer` ⭐
	NS	`v0n1.nic.computer`
	NS	`v0n2.nic.computer`
	NS	`v0n3.nic.computer`
	NS	`v2n0.nic.computer`
	NS	`v2n1.nic.computer`
	SOA	`v0n0.nic.computer`hostmaster@donuts.email serial=1785428685

Subdomains

mx.insecure.computer

Same first word

insecure.lu

insecure.me

insecure.com.ar

insecure.cl

insecure.at

insecure.computer

insecure.co.in

insecure.in

insecure.co.nz

insecure.io

insecure.network

insecure.ch

insecure.ru

insecure.systems

insecure.pl

insecure.org.mx

insecure.co

insecure.cloud

insecure.lt

insecure.ca

insecure.org

insecure.design

insecure.com

insecure.sk

insecure.pw

insecure.guru

insecure.cn

insecure.ws

insecure.email

insecure.us

insecure.nl

insecure.net

insecure.world

Similar names

DNS History

14 records (5 active, 9 former)

●NSns-1382.awsdns-44.org2026-03-22 → 2026-07-30 · 3 obs

○ 2017-11-03 13:02:28
● 2026-03-22 10:48:02
● 2026-07-30 16:53:48

●NSns-1952.awsdns-52.co.uk2026-03-22 → 2026-07-30 · 3 obs

○ 2017-11-03 13:02:28
● 2026-03-22 10:48:02
● 2026-07-30 16:53:48

●NSns-651.awsdns-17.net2026-03-22 → 2026-07-30 · 3 obs

○ 2017-11-03 13:02:28
● 2026-03-22 10:48:02
● 2026-07-30 16:53:48

●NSns-90.awsdns-11.com2026-03-22 → 2026-07-30 · 3 obs

○ 2017-11-03 13:02:28
● 2026-03-22 10:48:02
● 2026-07-30 16:53:48

○NSns-cloud-e1.googledomains.com2016-12-10 → 2017-11-03 · 4 obs

● 2016-12-10 21:31:00
● 2017-11-03 13:02:28
○ 2026-03-22 10:48:02
○ 2026-07-30 16:53:48

○NSns-cloud-e2.googledomains.com2016-12-10 → 2017-11-03 · 4 obs

● 2016-12-10 21:31:00
● 2017-11-03 13:02:28
○ 2026-03-22 10:48:02
○ 2026-07-30 16:53:48

○NSns-cloud-e3.googledomains.com2016-12-10 → 2017-11-03 · 4 obs

● 2016-12-10 21:31:00
● 2017-11-03 13:02:28
○ 2026-03-22 10:48:02
○ 2026-07-30 16:53:48

○NSns-cloud-e4.googledomains.com2016-12-10 → 2017-11-03 · 4 obs

● 2016-12-10 21:31:00
● 2017-11-03 13:02:28
○ 2026-03-22 10:48:02
○ 2026-07-30 16:53:48

○MXalt1.aspmx.l.google.com2017-11-03 → 2017-11-03 · 3 obs

● 2017-11-03 13:02:28
○ 2026-03-22 10:48:02
○ 2026-07-30 16:53:48

○MXalt2.aspmx.l.google.com2017-11-03 → 2017-11-03 · 3 obs

● 2017-11-03 13:02:28
○ 2026-03-22 10:48:02
○ 2026-07-30 16:53:48

○MXalt3.aspmx.l.google.com2017-11-03 → 2017-11-03 · 3 obs

● 2017-11-03 13:02:28
○ 2026-03-22 10:48:02
○ 2026-07-30 16:53:48

○MXalt4.aspmx.l.google.com2017-11-03 → 2017-11-03 · 3 obs

● 2017-11-03 13:02:28
○ 2026-03-22 10:48:02
○ 2026-07-30 16:53:48

○MXaspmx.l.google.com2017-11-03 → 2017-11-03 · 3 obs

● 2017-11-03 13:02:28
○ 2026-03-22 10:48:02
○ 2026-07-30 16:53:48

●MXmx.insecure.computer2026-03-22 → 2026-07-30 · 3 obs

○ 2017-11-03 13:02:28
● 2026-03-22 10:48:02
● 2026-07-30 16:53:48

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
computer	v0n0.nic.computer, v0n1.nic.computer, v0n2.nic.computer, v0n3.nic.computer...	12 records
insecure.computer	ns-651.awsdns-17.net, ns-1382.awsdns-44.org, ns-1952.awsdns-52.co.uk, ns-90.awsdns-11.com	-

✅ Authoritative Response

Server:205.251.192.90

NS records: ns-651.awsdns-17.net, ns-1382.awsdns-44.org, ns-1952.awsdns-52.co.uk, ns-90.awsdns-11.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for insecure.computer (unsigned zone)

⏱️ Timing

Total: 476ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns-1382.awsdns-44.org, ns-1952.awsdns-52.co.uk...`
MX	1	`mx.insecure.computer (pri: 10)`
SOA	1	`ns-1382.awsdns-44.org awsdns-hostmaster.`

📌 Glue Records Collected

Total: 12

In-bailiwick: 12 (v0n0.nic.computer, v0n1.nic.computer, v0n2.nic.computer...)

Analysis

Hierarchy

The domain mx.insecure.computer falls under the parent insecure.computer.

Name Servers

insecure.computer has four authoritative name servers: ns-90.awsdns-11.com, ns-651.awsdns-17.net, ns-1382.awsdns-44.org and ns-1952.awsdns-52.co.uk.

At least some of insecure.computer's name servers are shared with other domains, for example ds903aikm3c5j.cloudfront.net, fedequim.es, stage.karauctionservices.com and two more.

Four hostnames, each resolving to a pair of IP addresses: ns-90.awsdns-11.com directs to 205.251.192.90 and 2600:9000:5300:5a00::1; ns-651.awsdns-17.net directs to 205.251.194.139 and 2600:9000:5302:8b00::1; ns-1382.awsdns-44.org directs to 205.251.197.102 and 2600:9000:5305:6600::1; ns-1952.awsdns-52.co.uk directs to 205.251.199.160 and 2600:9000:5307:a000::1.

Mail Servers

insecure.computer has one mail server: mx.insecure.computer.

There is one IP number for mx.insecure.computer: 50.208.29.237.