deliveryforce.com - dns.ninja
deliveryforce.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@deliveryforce.com 2025-11-27 #9 | ||||||
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=1783757237 | ||||||
Same first word
deliveryforce.com |
deliveryforce.net |
DNS History
10 records (3 active, 7 former)
●NSns1.atom.com2026-02-27 → 2026-07-11 · 3 obs
● 2026-02-27 13:58:40
● 2026-07-11 08:25:28
○NSns1.netnames.net2015-05-29 → 2017-04-07 · 4 obs
● 2017-04-07 08:49:48
○ 2026-02-27 13:58:40
○ 2026-07-11 08:25:28
●NSns2.atom.com2026-02-27 → 2026-07-11 · 3 obs
● 2026-02-27 13:58:40
● 2026-07-11 08:25:28
○NSns2.netnames.net2015-05-29 → 2017-04-07 · 4 obs
● 2017-04-07 08:49:48
○ 2026-02-27 13:58:40
○ 2026-07-11 08:25:28
○NSns5.netnames.net2015-05-29 → 2017-04-07 · 4 obs
● 2017-04-07 08:49:48
○ 2026-02-27 13:58:40
○ 2026-07-11 08:25:28
○NSns6.netnames.net2015-05-29 → 2017-04-07 · 4 obs
● 2017-04-07 08:49:48
○ 2026-02-27 13:58:40
○ 2026-07-11 08:25:28
○MXrelay1.netnames.net2015-05-29 → 2017-04-07 · 4 obs
● 2017-04-07 08:49:48
○ 2026-02-27 13:58:40
○ 2026-07-11 08:25:28
○MXrelay2.netnames.net2015-05-29 → 2017-04-07 · 4 obs
● 2017-04-07 08:49:48
○ 2026-02-27 13:58:40
○ 2026-07-11 08:25:28
●A52.20.84.622026-02-27 → 2026-07-11 · 3 obs
● 2026-02-27 13:58:40
● 2026-07-11 08:25:28
○A74.84.204.1332015-05-29 → 2017-04-07 · 4 obs
● 2017-04-07 08:49:48
○ 2026-02-27 13:58:40
○ 2026-07-11 08:25:28
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | j.gtld-servers.net, l.gtld-servers.net, k.gtld-servers.net, h.gtld-servers.net... | - |
| deliveryforce.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 deliveryforce.com (unsigned zone)
⏱️ Timing
Total: 3051ms | 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.deliveryforce.co |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.atom.com, ns2.atom.com)
Analysis
IP Addresses
deliveryforce.com directs to one IP number, which is 52.20.84.62.
Among the host names that share IP numbers with deliveryforce.com are estateforum.com, cetlo.com, www.densitycore.com and two others.
Name Servers
deliveryforce.com is delegated to two name servers: ns1.atom.com and ns2.atom.com.
deliveryforce.com has the same name server delegation as a number of other domains, such as lovelyvine.com, hookcrypto.com, pizr.com and two more.
There is at least partial name server overlap between deliveryforce.com and other domains — pasture.in, fundvy.com, askclerk.com and two more among them.
These name servers frequently co-occur with the name servers verification-yhehuhyrvixzqbtydgzisf.ns101.verify.hn and verification-gtqfjejeoke9r3uonbsh8e.ns101.verify.hn.
ns1.atom.com → 44.219.81.145 and ns2.atom.com → 50.19.240.86: one IP number per host name.