sudo.sh - dns.ninja

sudo.sh

DNSSEC⚠️ Not signed
A50.116.44.7🇺🇸 AKAMAI-LINODE-AP50.116.32.0/20 Akamai Technologies
PTRsudo.sh
NSns0.sudo.sh
A50.116.44.7🇺🇸 AKAMAI-LINODE-AP50.116.32.0/20 Akamai Technologies
PTRsudo.sh
NSns1.sudo.sh
A50.116.44.7🇺🇸 AKAMAI-LINODE-AP50.116.32.0/20 Akamai Technologies
PTRsudo.sh
NSns2.sudo.sh ⚠️ Not in parent delegation
A50.116.44.7🇺🇸 AKAMAI-LINODE-AP50.116.32.0/20 Akamai Technologies
PTRsudo.sh
SOAns0.sudo.shroot@sudo.sh serial=61

sh

DNSSEC🔒 Signed (DS record present)
NSa0.nic.sh
NSa2.nic.sh
NSb0.nic.sh
NSc0.nic.sh
SOAa0.nic.shhostmaster@donuts.email serial=1784074344

PTR for

Previously NS for

Subdomains

Same first word

Similar names

DNS History

7 records (4 active, 3 former)

20162017201820192020202120222023202420252026NSns0.sudo.shns1.sudo.shns2.sudo.shsudo.shMXmx.sudo.shA50.116.44.7198.177.251.74
NSns0.sudo.sh2015-08-16 → 2026-07-15 · 6 obs
● 2015-08-16 17:32:52
● 2015-12-04 08:31:28
○ 2016-03-04 16:56:38
○ 2016-06-24 22:30:22
● 2017-02-05 18:18:44
● 2026-07-15 00:50:02
NSns1.sudo.sh2015-08-16 → 2026-07-15 · 2 obs
● 2015-08-16 17:32:52
● 2026-07-15 00:50:02
NSns2.sudo.sh2016-03-04 → 2026-07-15 · 6 obs
○ 2015-12-04 08:31:28
● 2016-03-04 16:56:38
● 2016-06-24 22:30:22
○ 2017-02-05 18:18:44
● 2018-09-10 06:32:50
● 2026-07-15 00:50:02
NSsudo.sh2015-08-16 → 2018-09-10 · 8 obs
● 2015-08-16 17:32:52
○ 2015-12-04 08:31:28
● 2016-03-04 16:56:38
● 2016-06-24 22:30:22
○ 2017-02-05 18:18:44
● 2018-09-10 06:32:50
○ 2026-03-02 20:38:18
○ 2026-07-15 00:50:02
MXmx.sudo.sh2015-12-04 → 2017-02-05 · 6 obs
● 2015-12-04 08:31:28
● 2016-03-04 16:56:38
○ 2016-06-24 22:30:22
● 2017-02-05 18:18:44
○ 2018-09-10 06:32:50
○ 2026-07-15 00:50:02
A198.177.251.742015-08-16 → 2018-09-10 · 4 obs
● 2015-08-16 17:32:52
● 2018-09-10 06:32:50
○ 2026-03-02 20:38:18
○ 2026-07-15 00:50:02
A50.116.44.72026-03-02 → 2026-07-15 · 3 obs
○ 2018-09-10 06:32:50
● 2026-03-02 20:38:18
● 2026-07-15 00:50:02

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
sha0.nic.sh, a2.nic.sh, b0.nic.sh, c0.nic.sh8 records
sudo.shns0.sudo.sh, ns1.sudo.sh2 records

✅ Authoritative Response

Server:50.116.44.7

NS records: ns0.sudo.sh, ns1.sudo.sh

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for sudo.sh (unsigned zone)

⏱️ Timing

Total: 285ms | Queries: -

📄 Records

TypeCountSample Data
A150.116.44.7
NS3ns0.sudo.sh, ns1.sudo.sh...
SOA1ns0.sudo.sh root.sudo.sh

📌 Glue Records Collected

Total: 10

In-bailiwick: 10 (a0.nic.sh, a2.nic.sh, b0.nic.sh...)

Analysis

Hierarchy

sudo.sh has four subdomains: ns0.sudo.sh, hexakaideca.sudo.sh, ns2.sudo.sh and ns1.sudo.sh.

IP Addresses

sudo.sh has exactly one IP address — 50.116.44.7.

Among others, ns2.sudo.sh, ns1.sudo.sh, ns0.sudo.sh and hexakaideca.sudo.sh resolve to the same IP numbers as sudo.sh.

Name Servers

The authoritative name servers for sudo.sh are ns0.sudo.sh, ns1.sudo.sh and ns2.sudo.sh — three in total.

At least some of sudo.sh's name servers are also used by other domains, among them glomar.me.

ns0.sudo.sh resolves to 50.116.44.7, and so do ns1.sudo.sh and ns2.sudo.sh — all three share that one IP address.

Three host names point to 50.116.44.7: ns0.sudo.sh, ns1.sudo.sh and ns2.sudo.sh.