fetchcore-cloud.com - dns.ninja
fetchcore-cloud.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=1780559944 | ||||||
Subdomains
eks.fetchcore-cloud.com |
stuller.fetchcore-cloud.com |
static.fetchcore-cloud.com |
fsp.fetchcore-cloud.com |
aws.fetchcore-cloud.com |
Same first word
fetchcore-cloud.com |
DNS History
10 records (9 active, 1 former)
●NSns-117.awsdns-14.com2016-12-16 → 2026-06-04 · 2 obs
● 2026-06-04 08:26:30
●NSns-1190.awsdns-20.org2016-12-16 → 2026-06-04 · 2 obs
● 2026-06-04 08:26:30
●NSns-2040.awsdns-63.co.uk2016-12-16 → 2026-06-04 · 2 obs
● 2026-06-04 08:26:30
●NSns-810.awsdns-37.net2016-12-16 → 2026-06-04 · 2 obs
● 2026-06-04 08:26:30
●MXalt1.aspmx.l.google.com2026-02-15 → 2026-06-04 · 3 obs
● 2026-02-15 23:58:36
● 2026-06-04 08:26:30
●MXalt2.aspmx.l.google.com2026-02-15 → 2026-06-04 · 3 obs
● 2026-02-15 23:58:36
● 2026-06-04 08:26:30
●MXaspmx.l.google.com2026-02-15 → 2026-06-04 · 3 obs
● 2026-02-15 23:58:36
● 2026-06-04 08:26:30
●MXaspmx2.googlemail.com2026-02-15 → 2026-06-04 · 3 obs
● 2026-02-15 23:58:36
● 2026-06-04 08:26:30
●MXaspmx3.googlemail.com2026-02-15 → 2026-06-04 · 3 obs
● 2026-02-15 23:58:36
● 2026-06-04 08:26:30
○MXinbound-smtp.us-west-2.amazonaws.com2016-12-16 → 2016-12-16 · 3 obs
○ 2026-02-15 23:58:36
○ 2026-06-04 08:26:30
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| fetchcore-cloud.com | ns-117.awsdns-14.com, ns-810.awsdns-37.net, ns-1190.awsdns-20.org, ns-2040.awsdns-63.co.uk | 2 records |
✅ Authoritative Response
Server:205.251.199.248
NS records: ns-117.awsdns-14.com, ns-810.awsdns-37.net, ns-1190.awsdns-20.org, ns-2040.awsdns-63.co.uk
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for fetchcore-cloud.com (unsigned zone)
⏱️ Timing
Total: 797ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns-117.awsdns-14.com, ns-1190.awsdns-20.org... |
| MX | 5 | aspmx.l.google.com (pri: 1), aspmx2.googlemail.com (pri: 10)... |
| TXT | 1 | google-site-verification=qJmckXJ0EBNyAcx |
| SOA | 1 | ns-1190.awsdns-20.org awsdns-hostmaster. |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns-117.awsdns-14.com, ns-117.awsdns-14.com)
Analysis
Hierarchy
eks.fetchcore-cloud.com, stuller.fetchcore-cloud.com, static.fetchcore-cloud.com, fsp.fetchcore-cloud.com and aws.fetchcore-cloud.com are all subdomains of fetchcore-cloud.com.
Name Servers
fetchcore-cloud.com carries NS records pointing to 4 name servers: ns-117.awsdns-14.com, ns-810.awsdns-37.net, ns-1190.awsdns-20.org and ns-2040.awsdns-63.co.uk.
The name servers of fetchcore-cloud.com overlap at least partially with those of other domains — among them toolkit.net.au, connect-press.net, bini.digital and two more.
Each of the four hosts ns-117.awsdns-14.com, ns-810.awsdns-37.net, ns-1190.awsdns-20.org and ns-2040.awsdns-63.co.uk has two IP addresses. ns-117.awsdns-14.com points to 205.251.192.117 and 2600:9000:5300:7500::1. ns-810.awsdns-37.net points to 205.251.195.42 and 2600:9000:5303:2a00::1. ns-1190.awsdns-20.org points to 205.251.196.166 and 2600:9000:5304:a600::1. ns-2040.awsdns-63.co.uk points to 205.251.199.248 and 2600:9000:5307:f800::1.
Mail Servers
fetchcore-cloud.com uses 5 mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com plus two additional ones.
fetchcore-cloud.com shares at least some of its mail servers with other domains — for example e-dp.com, ns500698.ns500758.ns500698.ns500758.ns500736.ns500735.ns500735.ns500698.ns500736.ns500735.ns500576.ns500698.ns500576.ns500576.ns500576.ns500576.trackreceptor.com, ns500698.ns500698.ns500698.ns500698.ns500698.ns500735.ns500735.ns500735.ns500735.ns500735.ns500735.ns500576.ns500698.ns500576.ns500619.ns500698.trackreceptor.com and two more.
These mail servers tend to co-occur with alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, alt4.aspmx.l.google.com and three additional mail servers.
Hosts with two IP numbers each:
aspmx2.googlemail.com maps to two IP addresses — 108.177.123.26 and 2800:3f0:4003:c0f::1a.
aspmx3.googlemail.com maps to two IP addresses — 172.253.116.27 and 2a00:1450:400b:c02::1b.
aspmx.l.google.com maps to two IP addresses — 192.178.223.26 and 2a00:1450:4009:c0f::1b.
alt1.aspmx.l.google.com maps to two IP addresses — 108.177.123.26 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com maps to two IP addresses — 172.253.116.26 and 2a00:1450:400b:c02::1b.
These two host names — aspmx2.googlemail.com and alt1.aspmx.l.google.com — each point to 2800:3f0:4003:c0f::1a IP addresses.
These two host names — aspmx2.googlemail.com and alt1.aspmx.l.google.com — each point to 108.177.123.26 IP addresses.
These two host names — aspmx3.googlemail.com and alt2.aspmx.l.google.com — each point to 2a00:1450:400b:c02::1b IP addresses.