jamstackmakers.com - dns.ninja
jamstackmakers.com
com
| DNSSEC | ⚠️ Not signed | ||||||
| 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=1788380030 | ||||||
Same first word
jamstackmakers.com |
Previous names
Next names
DNS History
12 records (7 active, 5 former)
●NSbayan.ns.cloudflare.com2026-09-01 → 2026-09-02 · 3 obs
● 2026-09-01 16:10:40
● 2026-09-02 20:46:54
○NSdns1.p06.nsone.net2019-12-16 → 2019-12-16 · 3 obs
○ 2026-09-01 16:10:40
○ 2026-09-02 20:46:54
○NSdns2.p06.nsone.net2019-12-16 → 2019-12-16 · 3 obs
○ 2026-09-01 16:10:40
○ 2026-09-02 20:46:54
○NSdns3.p06.nsone.net2019-12-16 → 2019-12-16 · 3 obs
○ 2026-09-01 16:10:40
○ 2026-09-02 20:46:54
○NSdns4.p06.nsone.net2019-12-16 → 2019-12-16 · 3 obs
○ 2026-09-01 16:10:40
○ 2026-09-02 20:46:54
●NSleah.ns.cloudflare.com2026-09-01 → 2026-09-02 · 3 obs
● 2026-09-01 16:10:40
● 2026-09-02 20:46:54
●MXalt1.aspmx.l.google.com2026-09-01 → 2026-09-02 · 2 obs
● 2026-09-02 20:46:54
●MXalt2.aspmx.l.google.com2026-09-01 → 2026-09-02 · 2 obs
● 2026-09-02 20:46:54
●MXalt3.aspmx.l.google.com2026-09-01 → 2026-09-02 · 2 obs
● 2026-09-02 20:46:54
●MXalt4.aspmx.l.google.com2026-09-01 → 2026-09-02 · 2 obs
● 2026-09-02 20:46:54
●MXaspmx.l.google.com2026-09-01 → 2026-09-02 · 2 obs
● 2026-09-02 20:46:54
○A134.209.226.2112019-12-16 → 2019-12-16 · 3 obs
○ 2026-09-01 16:10:40
○ 2026-09-02 20:46:54
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net... | - |
| jamstackmakers.com | leah.ns.cloudflare.com, bayan.ns.cloudflare.com | 12 records |
✅ Authoritative Response
Server:108.162.192.129
NS records: leah.ns.cloudflare.com, bayan.ns.cloudflare.com
🔒 DNSSEC Status
❌ Bogus (DNSSEC validation failed)
Validation error at com: Error: DNS query timeout: 192.33.14.30 for DNSKEY com
⏱️ Timing
Total: 3183ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | bayan.ns.cloudflare.com, leah.ns.cloudflare.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 3 | google-site-verification=WSnp9HUX07fVckX, google-site-verification=vJwZAGHQ14FFOJH... |
| SOA | 1 | bayan.ns.cloudflare.com dns.cloudflare.c |
📌 Glue Records Collected
Total: 12
Out-of-bailiwick: 12 (leah.ns.cloudflare.com, leah.ns.cloudflare.com, leah.ns.cloudflare.com...)
Analysis
Name Servers
jamstackmakers.com has two authoritative name servers — bayan.ns.cloudflare.com and leah.ns.cloudflare.com.
jamstackmakers.com shares its NS records with other domains, for example lonellcservices.com, globallawncare.net, wlx567.com and two others.
At least some of jamstackmakers.com's name servers are shared with other domains, for example xeleg80483.workers.dev, lalabetcasinoplay.com, puncakpb.pages.dev and two more.
These name servers tend to be used in conjunction with the name servers tiffany.ns.cloudflare.com.
DNS names with 6 IP addresses:
bayan.ns.cloudflare.com points to 108.162.193.72, 172.64.33.72, 173.245.59.72 and 3 other IP addresses.
leah.ns.cloudflare.com points to 108.162.192.129, 172.64.32.129, 173.245.58.129 and 3 other IP addresses.
Mail Servers
jamstackmakers.com has five mail servers, which are aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
There is at least a partial MX overlap between jamstackmakers.com and other domains, including ywamatlanta.org, bajacasamar.com, karenparkfitness.com and two others.
These mail servers tend to appear in combination with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx3.googlemail.com and 3 others.
Four hostnames, each resolving to a pair of IP addresses: aspmx.l.google.com directs to 192.178.218.26 and 2607:f8b0:4004:c25::1b; alt1.aspmx.l.google.com directs to 192.178.234.27 and 2800:3f0:4003:c14::1b; alt3.aspmx.l.google.com directs to 192.178.223.26 and 2a00:1450:4009:c0f::1a; alt4.aspmx.l.google.com directs to 172.253.157.27 and 2a00:1450:400c:c23::1a.