jamscape.com - dns.ninja
jamscape.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=1785359722 | ||||||
Same first word
jamscape.com |
Similar names
DNS History
15 records (9 active, 6 former)
○NSbuy.internettraffic.com2015-07-17 → 2016-04-29 · 4 obs
● 2016-04-29 12:50:38
○ 2016-12-01 21:40:26
○ 2026-07-29 21:27:44
●NSdns1.registrar-servers.com2026-06-30 → 2026-07-29 · 3 obs
● 2026-06-30 17:18:56
● 2026-07-29 21:27:44
●NSdns2.registrar-servers.com2026-06-30 → 2026-07-29 · 3 obs
● 2026-06-30 17:18:56
● 2026-07-29 21:27:44
○NSns1.uniregistrymarket.link2016-12-01 → 2017-06-29 · 5 obs
● 2016-12-01 21:40:26
● 2017-06-29 16:21:36
○ 2026-06-30 17:18:56
○ 2026-07-29 21:27:44
○NSns2.uniregistrymarket.link2016-12-01 → 2017-06-29 · 5 obs
● 2016-12-01 21:40:26
● 2017-06-29 16:21:36
○ 2026-06-30 17:18:56
○ 2026-07-29 21:27:44
○NSsell.internettraffic.com2015-07-17 → 2016-04-29 · 4 obs
● 2016-04-29 12:50:38
○ 2016-12-01 21:40:26
○ 2026-07-29 21:27:44
●MXalt1.aspmx.l.google.com2026-06-30 → 2026-07-29 · 2 obs
● 2026-07-29 21:27:44
●MXalt2.aspmx.l.google.com2026-06-30 → 2026-07-29 · 2 obs
● 2026-07-29 21:27:44
●MXaspmx.l.google.com2026-06-30 → 2026-07-29 · 2 obs
● 2026-07-29 21:27:44
●MXaspmx2.googlemail.com2026-06-30 → 2026-07-29 · 2 obs
● 2026-07-29 21:27:44
●MXaspmx3.googlemail.com2026-06-30 → 2026-07-29 · 2 obs
● 2026-07-29 21:27:44
○A69.172.201.1532016-04-29 → 2017-06-29 · 5 obs
● 2016-04-29 12:50:38
● 2017-06-29 16:21:36
○ 2026-06-30 17:18:56
○ 2026-07-29 21:27:44
○A69.172.201.2082015-07-17 → 2016-02-23 · 4 obs
● 2016-02-23 05:09:22
○ 2016-04-29 12:50:38
○ 2026-07-29 21:27:44
●A75.2.70.752026-06-30 → 2026-07-29 · 3 obs
● 2026-06-30 17:18:56
● 2026-07-29 21:27:44
●A99.83.190.1022026-06-30 → 2026-07-29 · 3 obs
● 2026-06-30 17:18:56
● 2026-07-29 21:27:44
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | c.gtld-servers.net, e.gtld-servers.net, g.gtld-servers.net, b.gtld-servers.net... | - |
| jamscape.com | dns1.registrar-servers.com, dns2.registrar-servers.com | 4 records |
✅ Authoritative Response
Server:156.154.133.200
NS records: dns1.registrar-servers.com, dns2.registrar-servers.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for jamscape.com (unsigned zone)
⏱️ Timing
Total: 160ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 99.83.190.102, 75.2.70.75 |
| NS | 2 | dns1.registrar-servers.com, dns2.registrar-servers.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 3 | MS=ms88054217, v=spf1 include:_spf.google.com include:s... |
| SOA | 1 | dns1.registrar-servers.com hostmaster.re |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (dns1.registrar-servers.com, dns1.registrar-servers.com, dns2.registrar-servers.com...)
Analysis
IP Addresses
jamscape.com points to the IP addresses 75.2.70.75 and 99.83.190.102
Two other host names, along with oaklanepartners.com, helpmechoose.ai and volleto.com, also share IP numbers with jamscape.com.
Name Servers
jamscape.com uses two name servers for its delegation: dns1.registrar-servers.com and dns2.registrar-servers.com.
jamscape.com shares its NS records with other domains, for example masslessphoton.com, greensborotrails.com, growthera.com and two others.
The two host names dns1.registrar-servers.com and dns2.registrar-servers.com each have a pair of IP addresses: dns1.registrar-servers.com has 156.154.132.200 and 2610:a1:1024::200, and dns2.registrar-servers.com has 156.154.133.200 and 2610:a1:1025::200.
Mail Servers
jamscape.com has five mail servers, which are aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
There is at least a partial MX overlap between jamscape.com and other domains, including ns500759.ns500758.ns500698.ns500758.ns500735.ns500735.ns500698.ns500736.ns500736.ns500735.ns500736.ns500708.ns500708.ns500576.ns500686.ns500619.trackreceptor.com, ns500698.ns500759.ns500758.ns500758.ns500758.ns500698.ns500736.ns500736.ns500698.ns500708.ns500576.ns500686.ns500576.ns500619.trackreceptor.com, ns500758.ns500758.ns500759.ns500735.ns500736.ns500698.ns500735.ns500735.ns500698.ns500735.ns500576.ns500698.ns500576.ns500576.ns500619.ns500619.trackreceptor.com and two others.
These mail servers tend to appear in combination with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.
Host names that have two IP addresses:
aspmx2.googlemail.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
aspmx3.googlemail.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1b.
aspmx.l.google.com directs traffic to 142.251.16.27 and 2607:f8b0:4004:c08::1b.
alt1.aspmx.l.google.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1b.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c0f::1a IP addresses each.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 108.177.123.26 IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 2a00:1450:400b:c02::1b IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 172.253.116.27 IP addresses each.