fetchcore-developers.com - dns.ninja
fetchcore-developers.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=1794205851 | ||||||
Subdomains
static.fetchcore-developers.com |
Same first word
fetchcore-developers.com |
Previous names
Next names
DNS History
10 records (9 active, 1 former)
●NSns-1356.awsdns-41.org2017-08-10 → 2026-11-09 · 2 obs
● 2026-11-09 07:11:12
●NSns-1714.awsdns-22.co.uk2017-08-10 → 2026-11-09 · 2 obs
● 2026-11-09 07:11:12
●NSns-309.awsdns-38.com2017-08-10 → 2026-11-09 · 2 obs
● 2026-11-09 07:11:12
●NSns-636.awsdns-15.net2017-08-10 → 2026-11-09 · 2 obs
● 2026-11-09 07:11:12
●MXalt1.aspmx.l.google.com2026-04-09 → 2026-11-09 · 3 obs
● 2026-04-09 01:00:44
● 2026-11-09 07:11:12
●MXalt2.aspmx.l.google.com2026-04-09 → 2026-11-09 · 3 obs
● 2026-04-09 01:00:44
● 2026-11-09 07:11:12
●MXaspmx.l.google.com2026-04-09 → 2026-11-09 · 3 obs
● 2026-04-09 01:00:44
● 2026-11-09 07:11:12
●MXaspmx2.googlemail.com2026-04-09 → 2026-11-09 · 3 obs
● 2026-04-09 01:00:44
● 2026-11-09 07:11:12
●MXaspmx3.googlemail.com2026-04-09 → 2026-11-09 · 3 obs
● 2026-04-09 01:00:44
● 2026-11-09 07:11:12
○MXinbound-smtp.us-east-1.amazonaws.com2017-08-10 → 2017-08-10 · 3 obs
○ 2026-04-09 01:00:44
○ 2026-11-09 07:11:12
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | m.gtld-servers.net, k.gtld-servers.net, h.gtld-servers.net, e.gtld-servers.net... | - |
| fetchcore-developers.com | ns-636.awsdns-15.net, ns-309.awsdns-38.com, ns-1714.awsdns-22.co.uk, ns-1356.awsdns-41.org | 2 records |
✅ Authoritative Response
Server:205.251.197.76
NS records: ns-636.awsdns-15.net, ns-309.awsdns-38.com, ns-1714.awsdns-22.co.uk, ns-1356.awsdns-41.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for fetchcore-developers.com (unsigned zone)
⏱️ Timing
Total: 1561ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns-1356.awsdns-41.org, ns-1714.awsdns-22.co.uk... |
| MX | 5 | aspmx.l.google.com (pri: 1), aspmx2.googlemail.com (pri: 10)... |
| TXT | 1 | google-site-verification=nKFt1ELkgNC2TEf |
| SOA | 1 | ns-1714.awsdns-22.co.uk awsdns-hostmaste |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns-309.awsdns-38.com, ns-309.awsdns-38.com)
Analysis
Hierarchy
fetchcore-developers.com is the parent zone for static.fetchcore-developers.com.
Name Servers
Four name servers handle the delegation for fetchcore-developers.com: ns-309.awsdns-38.com, ns-636.awsdns-15.net, ns-1356.awsdns-41.org and ns-1714.awsdns-22.co.uk.
fetchcore-developers.com partially shares its NS delegation with several other domains, including do604t9yl7t34.cloudfront.net, emmatest.net, maihama.net and two others.
ns-309.awsdns-38.com, ns-636.awsdns-15.net, ns-1356.awsdns-41.org and ns-1714.awsdns-22.co.uk each carry two IP addresses. ns-309.awsdns-38.com has 205.251.193.53 and 2600:9000:5301:3500::1; ns-636.awsdns-15.net has 205.251.194.124 and 2600:9000:5302:7c00::1; ns-1356.awsdns-41.org has 205.251.197.76 and 2600:9000:5305:4c00::1; ns-1714.awsdns-22.co.uk has 205.251.198.178 and 2600:9000:5306:b200::1.
Mail Servers
Mail for fetchcore-developers.com is handled by five mail servers, namely aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
At least some of the mail servers used by fetchcore-developers.com are shared with other domains: momentuminmissions.org, eutectic.com.mx, delucasystems.com and two others among them.
These mail servers are often deployed together with alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, alt4.aspmx.l.google.com and 3 other mail servers.
Host names pointing to two IP addresses:
aspmx2.googlemail.com directs traffic to 192.178.234.27 and 2800:3f0:4003:c14::1b.
aspmx3.googlemail.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1a.
aspmx.l.google.com directs traffic to 172.253.62.27 and 2607:f8b0:4004:c2f::1a.
alt1.aspmx.l.google.com directs traffic to 192.178.234.27 and 2800:3f0:4003:c14::1a.
alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1a.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 192.178.234.27 IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 2a00:1450:400b:c02::1a IP addresses each.