runalert.com - dns.ninja
runalert.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 52.20.84.62🇺🇸 Amazon52.20.0.0/14 EC2 IAD prefix | ||||||
| PTR | ec2-52-20-84-62.compute-1.amazonaws.com | ||||||
| NS | ns1.atom.com ⭐ | ||||||
| A | 44.219.81.145🇺🇸 Amazon44.192.0.0/11 EC2 IAD prefix | ||||||
| PTR | ec2-44-219-81-145.compute-1.amazonaws.com | ||||||
| NS | ns2.atom.com | ||||||
| A | 50.19.240.86🇺🇸 Amazon50.19.128.0/17 EC2 IAD prefix | ||||||
| PTR | ec2-50-19-240-86.compute-1.amazonaws.com | ||||||
| SOA | ns1.atom.comhostmaster@runalert.com 2025-02-07 #4 | ||||||
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1786579899 | ||||||
Same first word
runalert.com |
Similar names
DNS History
21 records (3 active, 18 former)
●NSns1.atom.com2026-02-16 → 2026-08-13 · 3 obs
○ 2020-04-03 12:58:06
● 2026-02-16 01:22:44
● 2026-08-13 00:18:08
● 2026-02-16 01:22:44
● 2026-08-13 00:18:08
○NSns1.namebrightdns.com2015-08-03 → 2017-04-09 · 7 obs
● 2015-08-03 07:02:20
○ 2015-12-11 12:50:36
● 2016-03-14 16:47:42
○ 2016-07-13 07:19:18
● 2017-04-09 22:36:46
○ 2020-04-03 12:58:06
○ 2026-08-13 00:18:08
○ 2015-12-11 12:50:36
● 2016-03-14 16:47:42
○ 2016-07-13 07:19:18
● 2017-04-09 22:36:46
○ 2020-04-03 12:58:06
○ 2026-08-13 00:18:08
●NSns2.atom.com2026-02-16 → 2026-08-13 · 3 obs
○ 2020-04-03 12:58:06
● 2026-02-16 01:22:44
● 2026-08-13 00:18:08
● 2026-02-16 01:22:44
● 2026-08-13 00:18:08
○NSns2.namebrightdns.com2015-08-03 → 2017-04-09 · 7 obs
● 2015-08-03 07:02:20
○ 2015-12-11 12:50:36
● 2016-03-14 16:47:42
○ 2016-07-13 07:19:18
● 2017-04-09 22:36:46
○ 2020-04-03 12:58:06
○ 2026-08-13 00:18:08
○ 2015-12-11 12:50:36
● 2016-03-14 16:47:42
○ 2016-07-13 07:19:18
● 2017-04-09 22:36:46
○ 2020-04-03 12:58:06
○ 2026-08-13 00:18:08
○NSnsg1.namebrightdns.com2015-12-11 → 2020-04-03 · 8 obs
○ 2015-08-03 07:02:20
● 2015-12-11 12:50:36
○ 2016-03-14 16:47:42
● 2016-07-13 07:19:18
○ 2017-04-09 22:36:46
● 2020-04-03 12:58:06
○ 2026-02-16 01:22:44
○ 2026-08-13 00:18:08
● 2015-12-11 12:50:36
○ 2016-03-14 16:47:42
● 2016-07-13 07:19:18
○ 2017-04-09 22:36:46
● 2020-04-03 12:58:06
○ 2026-02-16 01:22:44
○ 2026-08-13 00:18:08
○NSnsg2.namebrightdns.com2015-12-11 → 2020-04-03 · 8 obs
○ 2015-08-03 07:02:20
● 2015-12-11 12:50:36
○ 2016-03-14 16:47:42
● 2016-07-13 07:19:18
○ 2017-04-09 22:36:46
● 2020-04-03 12:58:06
○ 2026-02-16 01:22:44
○ 2026-08-13 00:18:08
● 2015-12-11 12:50:36
○ 2016-03-14 16:47:42
● 2016-07-13 07:19:18
○ 2017-04-09 22:36:46
● 2020-04-03 12:58:06
○ 2026-02-16 01:22:44
○ 2026-08-13 00:18:08
○MXanmail.namebrightmail.com2015-08-03 → 2015-08-03 · 3 obs
● 2015-08-03 07:02:20
○ 2015-12-11 12:50:36
○ 2026-08-13 00:18:08
○ 2015-12-11 12:50:36
○ 2026-08-13 00:18:08
○A107.23.160.2182015-12-11 → 2015-12-11 · 4 obs
○ 2015-08-03 07:02:20
● 2015-12-11 12:50:36
○ 2016-03-14 16:47:42
○ 2026-08-13 00:18:08
● 2015-12-11 12:50:36
○ 2016-03-14 16:47:42
○ 2026-08-13 00:18:08
○A107.23.198.2402016-07-13 → 2016-07-13 · 4 obs
○ 2016-03-14 16:47:42
● 2016-07-13 07:19:18
○ 2017-04-09 22:36:46
○ 2026-08-13 00:18:08
● 2016-07-13 07:19:18
○ 2017-04-09 22:36:46
○ 2026-08-13 00:18:08
○A52.0.96.242016-03-14 → 2016-03-14 · 4 obs
○ 2015-12-11 12:50:36
● 2016-03-14 16:47:42
○ 2016-07-13 07:19:18
○ 2026-08-13 00:18:08
● 2016-03-14 16:47:42
○ 2016-07-13 07:19:18
○ 2026-08-13 00:18:08
○A52.2.15.202015-08-03 → 2015-08-03 · 3 obs
● 2015-08-03 07:02:20
○ 2026-02-16 01:22:44
○ 2026-08-13 00:18:08
○ 2026-02-16 01:22:44
○ 2026-08-13 00:18:08
●A52.20.84.622026-02-16 → 2026-08-13 · 3 obs
○ 2020-04-03 12:58:06
● 2026-02-16 01:22:44
● 2026-08-13 00:18:08
● 2026-02-16 01:22:44
● 2026-08-13 00:18:08
○A52.204.129.222017-04-09 → 2017-04-09 · 4 obs
○ 2016-07-13 07:19:18
● 2017-04-09 22:36:46
○ 2020-04-03 12:58:06
○ 2026-08-13 00:18:08
● 2017-04-09 22:36:46
○ 2020-04-03 12:58:06
○ 2026-08-13 00:18:08
○A52.4.72.1372016-07-13 → 2016-07-13 · 4 obs
○ 2016-03-14 16:47:42
● 2016-07-13 07:19:18
○ 2017-04-09 22:36:46
○ 2026-08-13 00:18:08
● 2016-07-13 07:19:18
○ 2017-04-09 22:36:46
○ 2026-08-13 00:18:08
○A52.71.117.992016-03-14 → 2016-03-14 · 4 obs
○ 2015-12-11 12:50:36
● 2016-03-14 16:47:42
○ 2016-07-13 07:19:18
○ 2026-08-13 00:18:08
● 2016-03-14 16:47:42
○ 2016-07-13 07:19:18
○ 2026-08-13 00:18:08
○A54.165.76.662015-08-03 → 2015-08-03 · 3 obs
● 2015-08-03 07:02:20
○ 2026-02-16 01:22:44
○ 2026-08-13 00:18:08
○ 2026-02-16 01:22:44
○ 2026-08-13 00:18:08
○A54.209.90.812015-12-11 → 2015-12-11 · 4 obs
○ 2015-08-03 07:02:20
● 2015-12-11 12:50:36
○ 2016-03-14 16:47:42
○ 2026-08-13 00:18:08
● 2015-12-11 12:50:36
○ 2016-03-14 16:47:42
○ 2026-08-13 00:18:08
○A54.85.127.702017-04-09 → 2017-04-09 · 4 obs
○ 2016-07-13 07:19:18
● 2017-04-09 22:36:46
○ 2020-04-03 12:58:06
○ 2026-08-13 00:18:08
● 2017-04-09 22:36:46
○ 2020-04-03 12:58:06
○ 2026-08-13 00:18:08
○CNAMEhdredirect-lb-399551664.us-east-1.elb.amazonaws.com2015-08-03 → 2016-07-13 · 4 obs
● 2015-08-03 07:02:20
● 2016-07-13 07:19:18
○ 2017-04-09 22:36:46
○ 2026-08-13 00:18:08
● 2016-07-13 07:19:18
○ 2017-04-09 22:36:46
○ 2026-08-13 00:18:08
○CNAMEhdredirect-lb3-890977680.us-east-1.elb.amazonaws.com2017-04-09 → 2017-04-09 · 4 obs
○ 2016-07-13 07:19:18
● 2017-04-09 22:36:46
○ 2020-04-03 12:58:06
○ 2026-08-13 00:18:08
● 2017-04-09 22:36:46
○ 2020-04-03 12:58:06
○ 2026-08-13 00:18:08
○CNAMEhdredirect-lb5-1afb6e2973825a56.elb.us-east-1.amazonaws.com2020-04-03 → 2026-02-16 · 5 obs
○ 2017-04-09 22:36:46
● 2020-04-03 12:58:06
● 2026-02-16 01:22:44
○ 2026-03-27 14:45:28
○ 2026-08-13 00:18:08
● 2020-04-03 12:58:06
● 2026-02-16 01:22:44
○ 2026-03-27 14:45:28
○ 2026-08-13 00:18:08
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| runalert.com | ns1.atom.com, ns2.atom.com | 2 records |
✅ Authoritative Response
Server:44.219.81.145
NS records: ns1.atom.com, ns2.atom.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for runalert.com (unsigned zone)
⏱️ Timing
Total: 149ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 52.20.84.62 |
| NS | 2 | ns1.atom.com, ns2.atom.com |
| SOA | 1 | ns1.atom.com hostmaster.runalert.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.atom.com, ns2.atom.com)
Analysis
IP Addresses
runalert.com directs to one IP number, which is 52.20.84.62.
Among the host names that share IP numbers with runalert.com are leanerfit.com, 523.co, jazoa.com and two others.
Name Servers
runalert.com uses two name servers for its delegation: ns1.atom.com and ns2.atom.com.
runalert.com has the same name server delegation as a number of other domains, such as mongolianhomes.com, vyrde.com, physionorm.com and two more.
runalert.com partially shares its NS delegation with several other domains, including yalki.com, ultrainn.com, synmatch.com and two others.
ns1.atom.com resolves to 44.219.81.145. ns2.atom.com resolves to 50.19.240.86. Both host names point to a single IP number.