foragingguru.com - robtex.com
foragingguru.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
foragingguru.com |
DNS History
11 records (11 active, 0 former)
●NSalgin.ns.cloudflare.com2026-02-22 → 2026-03-23 · 2 obs
● 2026-03-23 14:01:28
●NSivy.ns.cloudflare.com2026-02-22 → 2026-03-23 · 2 obs
● 2026-03-23 14:01:28
●MXalt1.aspmx.l.google.com2026-02-22 → 2026-03-23 · 2 obs
● 2026-03-23 14:01:28
●MXalt2.aspmx.l.google.com2026-02-22 → 2026-03-23 · 2 obs
● 2026-03-23 14:01:28
●MXalt3.aspmx.l.google.com2026-02-22 → 2026-03-23 · 2 obs
● 2026-03-23 14:01:28
●MXalt4.aspmx.l.google.com2026-02-22 → 2026-03-23 · 2 obs
● 2026-03-23 14:01:28
●MXaspmx.l.google.com2026-02-22 → 2026-03-23 · 2 obs
● 2026-03-23 14:01:28
●A104.21.15.292026-02-22 → 2026-03-23 · 2 obs
● 2026-03-23 14:01:28
●A172.67.205.242026-02-22 → 2026-03-23 · 2 obs
● 2026-03-23 14:01:28
●A2606:4700:3035::ac43:cd182026-02-22 → 2026-03-23 · 2 obs
● 2026-03-23 14:01:28
●A2606:4700:3037::6815:f1d2026-02-22 → 2026-03-23 · 2 obs
● 2026-03-23 14:01:28
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| foragingguru.com | ivy.ns.cloudflare.com, algin.ns.cloudflare.com | 12 records |
✅ Authoritative Response
Server:108.162.193.61
NS records: ivy.ns.cloudflare.com, algin.ns.cloudflare.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for foragingguru.com (unsigned zone)
⏱️ Timing
Total: 242ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 172.67.205.24, 104.21.15.29 |
| AAAA | 2 | 2606:4700:3035::ac43:cd18, 2606:4700:3037::6815:f1d |
| NS | 2 | algin.ns.cloudflare.com, ivy.ns.cloudflare.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 2 | google-site-verification=dfbCSw0scap7ixD, v=spf1 include:_spf.google.com -all |
| HTTPS | 1 | {"priority":1,"target":".","alpn":["h3", |
| SOA | 1 | algin.ns.cloudflare.com dns.cloudflare.c |
📌 Glue Records Collected
Total: 12
Out-of-bailiwick: 12 (ivy.ns.cloudflare.com, ivy.ns.cloudflare.com, ivy.ns.cloudflare.com...)
Analysis
IP Addresses
foragingguru.com refers to four IP numbers: 2606:4700:3035::ac43:cd18, 2606:4700:3037::6815:f1d, 104.21.15.29 and 172.67.205.24.
Other host names, for instance njapd.com, baofawuzi.com, ru4arab.com, vulkanclubb.com and thseka.com share IP numbers with foragingguru.com.
Name Servers
foragingguru.com's delegation uses two name servers: algin.ns.cloudflare.com and ivy.ns.cloudflare.com.
foragingguru.com uses the same name server setup as other domains, such as celebritystyleguide.com, polishfilms.org, trackr.moe, earlyexperts.net and michaelcerne.com.
foragingguru.com at least partially shares name servers with other domains, including halloween2020.org, mypdftools.pages.dev, 12cgi.com, thelagirl.com and 87633.com.
These name servers are commonly used with arya.ns.cloudflare.com.
Host names with six IP numbers:
algin.ns.cloudflare.com points to 2606:4700:58::adf5:3b3d, 2803:f800:50::6ca2:c13d, 2a06:98c1:50::ac40:213d, 108.162.193.61, 172.64.33.61 and 173.245.59.61.
ivy.ns.cloudflare.com points to 2606:4700:50::adf5:3a78, 2803:f800:50::6ca2:c078, 2a06:98c1:50::ac40:2078, 108.162.192.120, 172.64.32.120 and 173.245.58.120.
Mail Servers
foragingguru.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com.
foragingguru.com shares at least some mail servers with other domains, for example h3.com.tw, ns500759.ns500759.ns500759.ns500698.ns500759.ns500736.ns500735.ns500708.ns500698.ns500576.ns500708.ns500708.ns500698.ns500698.ns500619.ns500619.ns500619.trackreceptor.com, ns500671.ns500671.ns500731.ns500742.ns500754.ns500704.ns500671.ns500671.ns500678.ns500705.ns500678.ns500291.ns500649.tenderladiesbz.com, ns500671.ns500742.ns500731.ns500671.ns500731.ns500671.ns500705.ns500649.ns500291.ns500666.ns500142.lusty(0x736c7574)z.com and ns500754.ns500754.ns500671.ns500704.ns500705.ns500705.ns500705.ns500688.ns500649.ns500688.ns500649.ns500649.ns500666.tenderladiesbz.com.
these mail servers are often used with aspmx3.googlemail.com, aspmx2.googlemail.com, aspmx4.googlemail.com and aspmx5.googlemail.com.
Host names with two IP numbers:
aspmx.l.google.com points to: 2607:f8b0:4004:c19::1b and 172.253.62.27.
alt1.aspmx.l.google.com points to: 2607:f8b0:4003:c30::1b and 74.125.27.26.
alt2.aspmx.l.google.com points to: 2607:f8b0:4001:c70::1a and 192.178.209.26.
alt3.aspmx.l.google.com points to: 2607:f8b0:4024:c0d::1b and 192.178.152.26.
alt4.aspmx.l.google.com points to: 2607:f8b0:4023:403::1a and 142.250.96.27.