fullstack.sh - dns.ninja

πŸ›‘οΈDomain Reputation CheckBlocklist, phishing & malware statusβ†’

fullstack.sh

DNSSEC⚠️ Not signed
A52.20.84.62πŸ‡ΊπŸ‡Έ Amazon52.20.0.0/14 EC2 IAD prefix
NSns1.atom.com ⭐
A44.219.81.145πŸ‡ΊπŸ‡Έ Amazon44.192.0.0/11 EC2 IAD prefix
PTRec2-44-219-81-145.compute-1.amazonaws.com
NSns2.atom.com
A50.19.240.86πŸ‡ΊπŸ‡Έ Amazon50.19.128.0/17 EC2 IAD prefix
PTRec2-50-19-240-86.compute-1.amazonaws.com
SOAns1.atom.comhostmaster@fullstack.sh 2026-09-27 #1

sh

DNSSECπŸ”’ Signed (DS record present)
NSa0.nic.sh ⭐
NSa2.nic.sh
NSb0.nic.sh
NSc0.nic.sh
SOAa0.nic.shhostmaster@donuts.email serial=1793629699

Same first word

DNS History

3 records (3 active, 0 former)

NSns1.atom.comns2.atom.comA52.20.84.62
●NSns1.atom.com2026-10-05 β†’ 2026-11-02 Β· 2 obs
● 2026-10-05 15:41:26
● 2026-11-02 15:05:38
●NSns2.atom.com2026-10-05 β†’ 2026-11-02 Β· 2 obs
● 2026-10-05 15:41:26
● 2026-11-02 15:05:38
●A52.20.84.622026-10-05 β†’ 2026-11-02 Β· 2 obs
● 2026-10-05 15:41:26
● 2026-11-02 15:05:38

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
sha0.nic.sh, a2.nic.sh, b0.nic.sh, c0.nic.sh8 records
fullstack.shns1.atom.com, ns2.atom.com-

βœ… Authoritative Response

Server:50.19.240.86

NS records: ns1.atom.com, ns2.atom.com

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

Root DNSKEY fetch failed: Error: connect EADDRNOTAVAIL 198.41.0.4:53 - Local (0.0.0.0:0)

⏱️ Timing

Total: 627ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A152.20.84.62
NS2ns1.atom.com, ns2.atom.com
SOA1ns1.atom.com hostmaster.fullstack.sh

πŸ“Œ Glue Records Collected

Total: 8

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

Analysis

IP Addresses

fullstack.sh directs to one IP number, which is 52.20.84.62.

Name Servers

The NS records for fullstack.sh delegate to ns1.atom.com and ns2.atom.com.

Each of ns1.atom.com and ns2.atom.com has one IP address: ns1.atom.com uses 44.219.81.145 and ns2.atom.com uses 50.19.240.86.