privacyarray.com - robtex.com

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

privacyarray.com

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
TXTf0095018235b8109a2bf9f65674a1784b6971ed6
SOAns1.atom.comhostmaster@privacyarray.com 2025-10-27 #1

com

Same first word

DNS History

3 records (3 active, 0 former)

NSns1.atom.comns2.atom.comA52.20.84.62
●NSns1.atom.com2026-09-06 β†’ 2026-10-22 Β· 2 obs
● 2026-09-06 14:43:36
● 2026-10-22 16:36:40
●NSns2.atom.com2026-09-06 β†’ 2026-10-22 Β· 2 obs
● 2026-09-06 14:43:36
● 2026-10-22 16:36:40
●A52.20.84.622026-09-06 β†’ 2026-10-22 Β· 2 obs
● 2026-09-06 14:43:36
● 2026-10-22 16:36:40

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
privacyarray.comns1.atom.com, ns2.atom.com2 records

βœ… 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: 267ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A152.20.84.62
NS2ns2.atom.com, ns1.atom.com
TXT1f0095018235b8109a2bf9f65674a1784b6971ed6
SOA1ns1.atom.com hostmaster.privacyarray.com

πŸ“Œ Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.atom.com, ns2.atom.com)

Analysis

IP Addresses

privacyarray.com resolves to just one IP address, 52.20.84.62.

Name Servers

Two name servers handle the delegation for privacyarray.com: ns1.atom.com and ns2.atom.com.

ns1.atom.com β†’ 44.219.81.145 and ns2.atom.com β†’ 50.19.240.86: one IP number per host name.