securerelay.com - dns.ninja
securerelay.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@securerelay.com 2024-12-24 #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=1785804462 | ||||||
Same first word
securerelay.in |
securerelay.net |
securerelay.com |
Similar names
DNS History
17 records (3 active, 14 former)
●NSns1.atom.com2026-02-20 → 2026-08-04 · 3 obs
○ 2019-01-11 04:29:20
● 2026-02-20 13:11:12
● 2026-08-04 01:18:12
● 2026-02-20 13:11:12
● 2026-08-04 01:18:12
○NSns1.namebrightdns.com2015-07-03 → 2019-01-11 · 4 obs
● 2015-07-03 14:10:12
● 2019-01-11 04:29:20
○ 2026-02-20 13:11:12
○ 2026-08-04 01:18:12
● 2019-01-11 04:29:20
○ 2026-02-20 13:11:12
○ 2026-08-04 01:18:12
●NSns2.atom.com2026-02-20 → 2026-08-04 · 3 obs
○ 2019-01-11 04:29:20
● 2026-02-20 13:11:12
● 2026-08-04 01:18:12
● 2026-02-20 13:11:12
● 2026-08-04 01:18:12
○NSns2.namebrightdns.com2015-07-03 → 2019-01-11 · 4 obs
● 2015-07-03 14:10:12
● 2019-01-11 04:29:20
○ 2026-02-20 13:11:12
○ 2026-08-04 01:18:12
● 2019-01-11 04:29:20
○ 2026-02-20 13:11:12
○ 2026-08-04 01:18:12
○MXanmail.namebrightmail.com2015-07-03 → 2015-07-03 · 3 obs
● 2015-07-03 14:10:12
○ 2015-11-06 07:21:44
○ 2026-08-04 01:18:12
○ 2015-11-06 07:21:44
○ 2026-08-04 01:18:12
○A52.0.96.242016-02-05 → 2016-02-05 · 4 obs
○ 2015-11-06 07:21:44
● 2016-02-05 01:18:32
○ 2016-04-29 05:53:48
○ 2026-08-04 01:18:12
● 2016-02-05 01:18:32
○ 2016-04-29 05:53:48
○ 2026-08-04 01:18:12
●A52.20.84.622026-02-20 → 2026-08-04 · 3 obs
○ 2019-01-11 04:29:20
● 2026-02-20 13:11:12
● 2026-08-04 01:18:12
● 2026-02-20 13:11:12
● 2026-08-04 01:18:12
○A52.200.243.1232016-04-29 → 2016-04-29 · 4 obs
○ 2016-02-05 01:18:32
● 2016-04-29 05:53:48
○ 2017-01-10 14:26:06
○ 2026-08-04 01:18:12
● 2016-04-29 05:53:48
○ 2017-01-10 14:26:06
○ 2026-08-04 01:18:12
○A52.71.117.992016-02-05 → 2016-02-05 · 4 obs
○ 2015-11-06 07:21:44
● 2016-02-05 01:18:32
○ 2016-04-29 05:53:48
○ 2026-08-04 01:18:12
● 2016-02-05 01:18:32
○ 2016-04-29 05:53:48
○ 2026-08-04 01:18:12
○A54.152.144.2432016-04-29 → 2016-04-29 · 4 obs
○ 2016-02-05 01:18:32
● 2016-04-29 05:53:48
○ 2017-01-10 14:26:06
○ 2026-08-04 01:18:12
● 2016-04-29 05:53:48
○ 2017-01-10 14:26:06
○ 2026-08-04 01:18:12
○A54.174.31.2542015-07-03 → 2015-11-06 · 4 obs
● 2015-07-03 14:10:12
● 2015-11-06 07:21:44
○ 2016-02-05 01:18:32
○ 2026-08-04 01:18:12
● 2015-11-06 07:21:44
○ 2016-02-05 01:18:32
○ 2026-08-04 01:18:12
○A54.208.74.2152015-07-03 → 2015-11-06 · 4 obs
● 2015-07-03 14:10:12
● 2015-11-06 07:21:44
○ 2016-02-05 01:18:32
○ 2026-08-04 01:18:12
● 2015-11-06 07:21:44
○ 2016-02-05 01:18:32
○ 2026-08-04 01:18:12
○A54.82.156.192017-01-10 → 2017-01-10 · 4 obs
○ 2016-04-29 05:53:48
● 2017-01-10 14:26:06
○ 2019-01-11 04:29:20
○ 2026-08-04 01:18:12
● 2017-01-10 14:26:06
○ 2019-01-11 04:29:20
○ 2026-08-04 01:18:12
○A54.86.225.1562017-01-10 → 2017-01-10 · 4 obs
○ 2016-04-29 05:53:48
● 2017-01-10 14:26:06
○ 2019-01-11 04:29:20
○ 2026-08-04 01:18:12
● 2017-01-10 14:26:06
○ 2019-01-11 04:29:20
○ 2026-08-04 01:18:12
○CNAMEhdredirect-lb-399551664.us-east-1.elb.amazonaws.com2015-07-03 → 2016-04-29 · 4 obs
● 2015-07-03 14:10:12
● 2016-04-29 05:53:48
○ 2017-01-10 14:26:06
○ 2026-08-04 01:18:12
● 2016-04-29 05:53:48
○ 2017-01-10 14:26:06
○ 2026-08-04 01:18:12
○CNAMEhdredirect-lb3-890977680.us-east-1.elb.amazonaws.com2017-01-10 → 2017-01-10 · 4 obs
○ 2016-04-29 05:53:48
● 2017-01-10 14:26:06
○ 2019-01-11 04:29:20
○ 2026-08-04 01:18:12
● 2017-01-10 14:26:06
○ 2019-01-11 04:29:20
○ 2026-08-04 01:18:12
○CNAMEhdredirect-lb5-1afb6e2973825a56.elb.us-east-1.amazonaws.com2019-01-11 → 2019-01-11 · 4 obs
○ 2017-01-10 14:26:06
● 2019-01-11 04:29:20
○ 2026-02-20 13:11:12
○ 2026-08-04 01:18:12
● 2019-01-11 04:29:20
○ 2026-02-20 13:11:12
○ 2026-08-04 01:18:12
🔍 DNS Trace
Analysis
IP Addresses
securerelay.com points to a single IP number: 52.20.84.62.
Additional host names — tsula.com, rebartec.com, speedfiller.com and two others — share IP numbers with securerelay.com.
Name Servers
Two name servers handle the delegation for securerelay.com: ns1.atom.com and ns2.atom.com.
securerelay.com shares its name server setup with other domains, including indiapost.in, quzar.com, better.ai and two others.
securerelay.com at least partially shares name servers with other domains, including aivantech.com, seemy.net, ninopay.com and bamwealth.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.