adipepatch.com - robtex.com
adipepatch.com
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=1771291435 | ||||||
Same first word
adipepatch.com |
DNS History
11 records (11 active, 0 former)
●NSadrian.ns.cloudflare.com2026-02-21 → 2026-02-22 · 2 obs
● 2026-02-22 11:27:32
●NScasey.ns.cloudflare.com2026-02-21 → 2026-02-22 · 2 obs
● 2026-02-22 11:27:32
●MXeforward1.registrar-servers.com2026-02-21 → 2026-02-22 · 2 obs
● 2026-02-22 11:27:32
●MXeforward2.registrar-servers.com2026-02-21 → 2026-02-22 · 2 obs
● 2026-02-22 11:27:32
●MXeforward3.registrar-servers.com2026-02-21 → 2026-02-22 · 2 obs
● 2026-02-22 11:27:32
●MXeforward4.registrar-servers.com2026-02-21 → 2026-02-22 · 2 obs
● 2026-02-22 11:27:32
●MXeforward5.registrar-servers.com2026-02-21 → 2026-02-22 · 2 obs
● 2026-02-22 11:27:32
●A104.21.90.2452026-02-21 → 2026-02-22 · 2 obs
● 2026-02-22 11:27:32
●A172.67.163.852026-02-21 → 2026-02-22 · 2 obs
● 2026-02-22 11:27:32
●A2606:4700:3033::6815:5af52026-02-21 → 2026-02-22 · 2 obs
● 2026-02-22 11:27:32
●A2606:4700:3034::ac43:a3552026-02-21 → 2026-02-22 · 2 obs
● 2026-02-22 11:27:32
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| adipepatch.com | adrian.ns.cloudflare.com, casey.ns.cloudflare.com | - |
✅ Authoritative Response
Server: 108.162.192.57
NS records: adrian.ns.cloudflare.com, casey.ns.cloudflare.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for adipepatch.com (unsigned zone)
⏱️ Timing
Total: 96ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 104.21.90.245, 172.67.163.85 |
| AAAA | 2 | 2606:4700:3034::ac43:a355, 2606:4700:3033::6815:5af5 |
| NS | 2 | adrian.ns.cloudflare.com, casey.ns.cloudflare.com |
| MX | 5 | eforward1.registrar-servers.com (pri: 10, eforward2.registrar-servers.com (pri: 10... |
| TXT | 1 | v=spf1 include:spf.efwd.registrar-server |
| HTTPS | 1 | {"priority":1,"target":".","alpn":["h3", |
| SOA | 1 | adrian.ns.cloudflare.com dns.cloudflare. |
AI analysis
adipepatch.com points to four IP numbers: 2606:4700:3033::6815:5af5, 2606:4700:3034::ac43:a355, 104.21.90.245 and 172.67.163.85.
Other host names, for instance onlinehookup.org, lejing88.com, www.ljubici.com, base-lc.shipfusion.io and bessel.org share IP numbers with adipepatch.com.
Delegation for adipepatch.com rests with two name servers, adrian.ns.cloudflare.com and casey.ns.cloudflare.com.
adipepatch.com shares the same name server setup as other domains, including dhzlskj.com, giornataomeopatia.it, seolab.it, aknky.com and nnpcba.com.
adipepatch.com at least partially shares name servers with other domains, for instance atsm.mu, nyfxg.com, polstats.com, 89aw.com and firstexpo.cn.
These name servers are commonly used alongside kim.ns.cloudflare.com, tim.ns.cloudflare.com, peyton.ns.cloudflare.com and hank.ns.cloudflare.com.
Host names with six IP numbers: adrian.ns.cloudflare.com points to: 2606:4700:50::adf5:3a39, 2803:f800:50::6ca2:c039, 2a06:98c1:50::ac40:2039, 108.162.192.57, 172.64.32.57 and 173.245.58.57. casey.ns.cloudflare.com points to: 2606:4700:58::a29f:2c9e, 2803:f800:50::6ca2:c39e, 2a06:98c1:50::ac40:239e, 108.162.195.158, 162.159.44.158 and 172.64.35.158.
adipepatch.com is handled by five mail servers: eforward1.registrar-servers.com, eforward2.registrar-servers.com, eforward3.registrar-servers.com, eforward4.registrar-servers.com and eforward5.registrar-servers.com.
adipepatch.com shares mail servers with other domains at least in part, for instance sekolahmandiribatman.com, dkls.net, hilda.io, halloffamefilms.com and casinooyunlar8.com.
these mail servers are often used with eforward6.registrar-servers.com and eforward7.registrar-servers.com.
Host names with a single IP:
eforward1.registrar-servers.com points to: 162.255.118.51.
eforward2.registrar-servers.com points to: 162.255.118.52.
eforward3.registrar-servers.com points to: 162.255.118.51.
eforward4.registrar-servers.com points to: 162.255.118.52.
eforward5.registrar-servers.com points to: 162.255.118.51.
Host names pointing to 162.255.118.51: eforward1.registrar-servers.com, eforward3.registrar-servers.com and eforward5.registrar-servers.com.
Host names pointing to 162.255.118.52: eforward2.registrar-servers.com and eforward4.registrar-servers.com.
Common mappings: eforward1.registrar-servers.com, eforward3.registrar-servers.com and eforward5.registrar-servers.com point to 162.255.118.51; eforward2.registrar-servers.com and eforward4.registrar-servers.com point to 162.255.118.52.