deliwery.com - robtex.com
deliwery.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.dyna-ns.net ⭐ | ||||||
| A | 2400:cb00:2049:1::a29f:1a5c🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 2400:cb00:2049:1::a29f:1b9e🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.26.92Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns1.dyna-ns.net | ||||||
| A | 162.159.27.158Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns1.dyna-ns.net | ||||||
| NS | ns2.dyna-ns.net | ||||||
| A | 2400:cb00:2049:1::a29f:1805🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 2400:cb00:2049:1::a29f:1905🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.24.5Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns2.dyna-ns.net | ||||||
| A | 162.159.25.5Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns2.dyna-ns.net | ||||||
| TXT | 2bc22966a9da41577d51cea7e8d09f05 | ||||||
| SOA | ns1.dyna-ns.nethostmaster@deliwery.com 2026-03-04 #1 | ||||||
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=1776279447 | ||||||
Same first word
deliwery.com |
DNS History
13 records (2 active, 11 former)
○NSns1.bodis.com2017-03-16 → 2017-03-16 · 4 obs
○ 2016-07-13 23:39:02
● 2017-03-16 04:52:18
○ 2020-01-09 20:31:30
○ 2026-04-15 18:59:08
● 2017-03-16 04:52:18
○ 2020-01-09 20:31:30
○ 2026-04-15 18:59:08
●NSns1.dyna-ns.net2026-03-26 → 2026-04-15 · 3 obs
○ 2020-01-09 20:31:30
● 2026-03-26 13:53:52
● 2026-04-15 18:59:08
● 2026-03-26 13:53:52
● 2026-04-15 18:59:08
○NSns1.sircon.no2015-05-20 → 2016-07-13 · 4 obs
● 2015-05-20 16:39:00
● 2016-07-13 23:39:02
○ 2017-03-16 04:52:18
○ 2026-04-15 18:59:08
● 2016-07-13 23:39:02
○ 2017-03-16 04:52:18
○ 2026-04-15 18:59:08
○NSns13.domaincontrol.com2020-01-09 → 2020-01-09 · 4 obs
○ 2017-03-16 04:52:18
● 2020-01-09 20:31:30
○ 2026-03-26 13:53:52
○ 2026-04-15 18:59:08
● 2020-01-09 20:31:30
○ 2026-03-26 13:53:52
○ 2026-04-15 18:59:08
○NSns14.domaincontrol.com2020-01-09 → 2020-01-09 · 4 obs
○ 2017-03-16 04:52:18
● 2020-01-09 20:31:30
○ 2026-03-26 13:53:52
○ 2026-04-15 18:59:08
● 2020-01-09 20:31:30
○ 2026-03-26 13:53:52
○ 2026-04-15 18:59:08
○NSns2.bodis.com2017-03-16 → 2017-03-16 · 4 obs
○ 2016-07-13 23:39:02
● 2017-03-16 04:52:18
○ 2020-01-09 20:31:30
○ 2026-04-15 18:59:08
● 2017-03-16 04:52:18
○ 2020-01-09 20:31:30
○ 2026-04-15 18:59:08
●NSns2.dyna-ns.net2026-03-26 → 2026-04-15 · 3 obs
○ 2020-01-09 20:31:30
● 2026-03-26 13:53:52
● 2026-04-15 18:59:08
● 2026-03-26 13:53:52
● 2026-04-15 18:59:08
○NSns2.sircon.no2015-05-20 → 2016-07-13 · 4 obs
● 2015-05-20 16:39:00
● 2016-07-13 23:39:02
○ 2017-03-16 04:52:18
○ 2026-04-15 18:59:08
● 2016-07-13 23:39:02
○ 2017-03-16 04:52:18
○ 2026-04-15 18:59:08
○MXmx76.m2bp.com2017-03-16 → 2017-03-16 · 3 obs
● 2017-03-16 04:52:18
○ 2020-01-09 20:31:30
○ 2026-04-15 18:59:08
○ 2020-01-09 20:31:30
○ 2026-04-15 18:59:08
○MXmx76.mb1p.com2017-03-16 → 2017-03-16 · 3 obs
● 2017-03-16 04:52:18
○ 2020-01-09 20:31:30
○ 2026-04-15 18:59:08
○ 2020-01-09 20:31:30
○ 2026-04-15 18:59:08
○A178.164.11.742015-05-20 → 2016-07-13 · 4 obs
● 2015-05-20 16:39:00
● 2016-07-13 23:39:02
○ 2017-03-16 04:52:18
○ 2026-04-15 18:59:08
● 2016-07-13 23:39:02
○ 2017-03-16 04:52:18
○ 2026-04-15 18:59:08
○A184.168.221.482020-01-09 → 2020-01-09 · 4 obs
○ 2017-03-16 04:52:18
● 2020-01-09 20:31:30
○ 2026-03-26 13:53:52
○ 2026-04-15 18:59:08
● 2020-01-09 20:31:30
○ 2026-03-26 13:53:52
○ 2026-04-15 18:59:08
○A199.59.242.1502017-03-16 → 2017-03-16 · 4 obs
○ 2016-07-13 23:39:02
● 2017-03-16 04:52:18
○ 2020-01-09 20:31:30
○ 2026-04-15 18:59:08
● 2017-03-16 04:52:18
○ 2020-01-09 20:31:30
○ 2026-04-15 18:59:08
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| deliwery.com | ns2.dyna-ns.net, ns1.dyna-ns.net | - |
✅ Authoritative Response
Server:162.159.27.158
NS records: ns2.dyna-ns.net, ns1.dyna-ns.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for deliwery.com (unsigned zone)
⏱️ Timing
Total: 273ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | ns2.dyna-ns.net, ns1.dyna-ns.net |
| TXT | 1 | 2bc22966a9da41577d51cea7e8d09f05 |
| SOA | 1 | ns1.dyna-ns.net hostmaster.deliwery.com |
Analysis
Name Servers
Two name servers ns1.dyna-ns.net and ns2.dyna-ns.net handle the delegation for deliwery.com.
deliwery.com shares the same name server setup as other domains, for instance dragonia-casino-888.fr, discoverhho.com, k365bet.com, whoish.com and v3v7.cc.
Host names with four IP numbers:
ns1.dyna-ns.net points to: 2400:cb00:2049:1::a29f:1a5c, 2400:cb00:2049:1::a29f:1b9e, 162.159.26.92 and 162.159.27.158.
ns2.dyna-ns.net points to: 2400:cb00:2049:1::a29f:1805, 2400:cb00:2049:1::a29f:1905, 162.159.24.5 and 162.159.25.5.