inrequest.com - dns.ninja

inrequest.com

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@inrequest.com 2026-07-03 #2

com

Same first word

Similar names

DNS History

11 records (3 active, 8 former)

20162017201820192020202120222023202420252026NSns1.atom.comns2.atom.comns.buydomains.comns1.sedoparking.comns2.sedoparking.comMXlocalhostA52.20.84.62141.8.225.124207.148.248.14350.63.202.10464.190.63.222
NSns.buydomains.com2015-06-14 → 2017-06-19 · 4 obs
● 2015-06-14 00:10:26
● 2017-06-19 22:38:42
○ 2026-04-24 04:52:44
○ 2026-08-07 15:05:32
NSns1.atom.com2026-07-04 → 2026-08-07 · 4 obs
○ 2026-04-24 04:52:44
○ 2026-05-08 01:57:48
● 2026-07-04 01:48:34
● 2026-08-07 15:05:32
NSns1.sedoparking.com2026-04-24 → 2026-05-08 · 5 obs
○ 2017-06-19 22:38:42
● 2026-04-24 04:52:44
● 2026-05-08 01:57:48
○ 2026-07-04 01:48:34
○ 2026-08-07 15:05:32
NSns2.atom.com2026-07-04 → 2026-08-07 · 4 obs
○ 2026-04-24 04:52:44
○ 2026-05-08 01:57:48
● 2026-07-04 01:48:34
● 2026-08-07 15:05:32
NSns2.sedoparking.com2026-04-24 → 2026-05-08 · 5 obs
○ 2017-06-19 22:38:42
● 2026-04-24 04:52:44
● 2026-05-08 01:57:48
○ 2026-07-04 01:48:34
○ 2026-08-07 15:05:32
MXlocalhost2026-04-24 → 2026-05-08 · 4 obs
● 2026-04-24 04:52:44
● 2026-05-08 01:57:48
○ 2026-07-04 01:48:34
○ 2026-08-07 15:05:32
A141.8.225.1242016-01-24 → 2016-09-20 · 5 obs
○ 2015-11-09 09:41:56
● 2016-01-24 07:36:34
● 2016-09-20 06:07:52
○ 2017-06-19 22:38:42
○ 2026-08-07 15:05:32
A207.148.248.1432017-06-19 → 2017-06-19 · 4 obs
○ 2016-09-20 06:07:52
● 2017-06-19 22:38:42
○ 2026-04-24 04:52:44
○ 2026-08-07 15:05:32
A50.63.202.1042015-06-14 → 2015-11-09 · 4 obs
● 2015-06-14 00:10:26
● 2015-11-09 09:41:56
○ 2016-01-24 07:36:34
○ 2026-08-07 15:05:32
A52.20.84.622026-07-04 → 2026-08-07 · 4 obs
○ 2026-04-24 04:52:44
○ 2026-05-08 01:57:48
● 2026-07-04 01:48:34
● 2026-08-07 15:05:32
A64.190.63.2222026-04-24 → 2026-05-08 · 5 obs
○ 2017-06-19 22:38:42
● 2026-04-24 04:52:44
● 2026-05-08 01:57:48
○ 2026-07-04 01:48:34
○ 2026-08-07 15:05:32

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
comd.gtld-servers.net, e.gtld-servers.net, l.gtld-servers.net, k.gtld-servers.net...-
inrequest.comns1.atom.com, ns2.atom.com2 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 inrequest.com (unsigned zone)

⏱️ Timing

Total: 3067ms | Queries: -

📄 Records

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

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

inrequest.com points to a single IP number: 52.20.84.62.

Additional host names — webshock.com, conecta4.com, udemand.com and two others — share IP numbers with inrequest.com.

Name Servers

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

inrequest.com shares its name server setup with other domains, including rationkit.com, crestpillar.com, gbk.com and two others.

inrequest.com has overlapping name servers with several other domains — among them megabadger.com, altlife.org, qasaid.com and domainah.com.

These name servers commonly appear alongside the name servers verification-yhehuhyrvixzqbtydgzisf.ns101.verify.hn and verification-ef5yfht9kc3ym89rsntxua.ns101.verify.hn.

Both ns1.atom.com and ns2.atom.com have a single IP address each — ns1.atom.com resolves to 44.219.81.145 while ns2.atom.com resolves to 50.19.240.86.