timeout.run - robtex.com

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

timeout.run

DNSSEC⚠️ Not signed
A52.20.84.62πŸ‡ΊπŸ‡Έ Amazon52.20.0.0/14 EC2 IAD prefix
PTRec2-52-20-84-62.compute-1.amazonaws.com
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@timeout.run 2026-09-27 #3

run

DNSSECπŸ”’ Signed (DS record present)
NSv0n0.nic.run ⭐
NSv0n1.nic.run
NSv0n2.nic.run
NSv0n3.nic.run
NSv2n0.nic.run
NSv2n1.nic.run
SOAv0n0.nic.runhostmaster@donuts.email serial=1791327432

Same first word

Similar names

DNS History

3 records (3 active, 0 former)

NSns1.atom.comns2.atom.comA52.20.84.62
●NSns1.atom.com2026-09-28 β†’ 2026-10-06 Β· 2 obs
● 2026-09-28 00:22:46
● 2026-10-06 23:26:40
●NSns2.atom.com2026-09-28 β†’ 2026-10-06 Β· 2 obs
● 2026-09-28 00:22:46
● 2026-10-06 23:26:40
●A52.20.84.622026-09-28 β†’ 2026-10-06 Β· 2 obs
● 2026-09-28 00:22:46
● 2026-10-06 23:26:40

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
runv0n3.nic.run, v0n1.nic.run, v2n1.nic.run, v0n2.nic.run...12 records
timeout.runns2.atom.com, ns1.atom.com-

βœ… Authoritative Response

Server:50.19.240.86

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

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for timeout.run (unsigned zone)

⏱️ Timing

Total: 592ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A152.20.84.62
NS2ns1.atom.com, ns2.atom.com
SOA1ns1.atom.com hostmaster.timeout.run

πŸ“Œ Glue Records Collected

Total: 12

In-bailiwick: 12 (v0n3.nic.run, v0n3.nic.run, v0n1.nic.run...)

Analysis

IP Addresses

timeout.run resolves to one IP address: 52.20.84.62.

Name Servers

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

ns1.atom.com and ns2.atom.com each resolve to one IP number: ns1.atom.com points to 44.219.81.145 and ns2.atom.com points to 50.19.240.86.