jamzen.com - dns.ninja

jamzen.com

DNSSEC⚠️ Not signed
A13.56.33.8🇺🇸 Amazon13.56.0.0/16 EC2 Region prefix
PTRec2-13-56-33-8.us-west-1.compute.amazonaws.com
NSns1.brandbucket.com ⭐
A2600:1f1c:800:8b01:2ba3:bb61:44fb:b361🇺🇸 Amazon2600:1f1c:800::/38 AMAZON AWS
A54.241.53.41🇺🇸 Amazon54.241.0.0/17 EC2 SFO prefix
PTRec2-54-241-53-41.us-west-1.compute.amazonaws.com
NSns2.brandbucket.com
A2600:1f16:54:8701:4012:7e34:5c5f:95a8🇺🇸 Amazon2600:1f16::/38 AMAZON AWS
A18.221.52.246🇺🇸 Amazon18.220.0.0/14 EC2 CMH prefix
PTRec2-18-221-52-246.us-east-2.compute.amazonaws.com
TXTafternic-verification-cvgUQU8SkLxsjXcPBSk2CM
TXT27aab5373841b85aab94982ee19ab62f96481ed6
TXTv=spf1 -all
SOAns1.brandbucket.commail@jamzen.com 2024-03-05 #2

com

DNSSEC🔒 Signed (DS record present)
NSa.gtld-servers.net ⭐
NSb.gtld-servers.net
NSc.gtld-servers.net
NSd.gtld-servers.net
NSe.gtld-servers.net
NSf.gtld-servers.net
NSg.gtld-servers.net
NSh.gtld-servers.net
NSi.gtld-servers.net
NSj.gtld-servers.net
NSk.gtld-servers.net
NSl.gtld-servers.net
NSm.gtld-servers.net
SOAa.gtld-servers.netnstld@verisign-grs.com serial=1786576269

Same first word

jamzen.com

Similar names

enjazm.com
jzname.com
zenjam.com
menjaz.com

DNS History

20 records (3 active, 17 former)

20162017201820192020202120222023202420252026NSns1.brandbucket.comns2.brandbucket.comdns1.nameresolvers.comdns2.nameresolvers.comdns3.nameresolvers.comdns4.nameresolvers.comf1g1ns1.dnspod.netf1g1ns2.dnspod.netns1.namebrightdns.comns2.namebrightdns.comMXforward10.nameresolvers.comforward100.nameresolvers.comforward20.nameresolvers.comA13.56.33.8160.124.177.7216.13.106.119216.13.106.5434.206.157.6454.236.195.15CNAMEhdredirect-lb3-890977680.us-east-1.elb.amazonaws.com
○NSdns1.nameresolvers.com2015-08-06 → 2016-03-10 · 4 obs
● 2015-08-06 18:02:18
● 2016-03-10 10:57:06
○ 2016-07-07 05:45:08
○ 2026-08-12 23:17:12
○NSdns2.nameresolvers.com2015-08-06 → 2016-03-10 · 4 obs
● 2015-08-06 18:02:18
● 2016-03-10 10:57:06
○ 2016-07-07 05:45:08
○ 2026-08-12 23:17:12
○NSdns3.nameresolvers.com2015-08-06 → 2016-03-10 · 4 obs
● 2015-08-06 18:02:18
● 2016-03-10 10:57:06
○ 2016-07-07 05:45:08
○ 2026-08-12 23:17:12
○NSdns4.nameresolvers.com2015-08-06 → 2016-03-10 · 4 obs
● 2015-08-06 18:02:18
● 2016-03-10 10:57:06
○ 2016-07-07 05:45:08
○ 2026-08-12 23:17:12
○NSf1g1ns1.dnspod.net2020-03-20 → 2020-03-20 · 4 obs
○ 2017-03-19 01:37:38
● 2020-03-20 02:20:06
○ 2026-02-17 16:15:04
○ 2026-08-12 23:17:12
○NSf1g1ns2.dnspod.net2020-03-20 → 2020-03-20 · 4 obs
○ 2017-03-19 01:37:38
● 2020-03-20 02:20:06
○ 2026-02-17 16:15:04
○ 2026-08-12 23:17:12
●NSns1.brandbucket.com2026-02-17 → 2026-08-12 · 3 obs
○ 2020-03-20 02:20:06
● 2026-02-17 16:15:04
● 2026-08-12 23:17:12
○NSns1.namebrightdns.com2017-03-19 → 2017-03-19 · 4 obs
○ 2016-07-07 05:45:08
● 2017-03-19 01:37:38
○ 2020-03-20 02:20:06
○ 2026-08-12 23:17:12
●NSns2.brandbucket.com2026-02-17 → 2026-08-12 · 3 obs
○ 2020-03-20 02:20:06
● 2026-02-17 16:15:04
● 2026-08-12 23:17:12
○NSns2.namebrightdns.com2017-03-19 → 2017-03-19 · 4 obs
○ 2016-07-07 05:45:08
● 2017-03-19 01:37:38
○ 2020-03-20 02:20:06
○ 2026-08-12 23:17:12
○MXforward10.nameresolvers.com2015-08-06 → 2016-03-10 · 4 obs
● 2015-08-06 18:02:18
● 2016-03-10 10:57:06
○ 2016-07-07 05:45:08
○ 2026-08-12 23:17:12
○MXforward100.nameresolvers.com2015-08-06 → 2016-03-10 · 4 obs
● 2015-08-06 18:02:18
● 2016-03-10 10:57:06
○ 2016-07-07 05:45:08
○ 2026-08-12 23:17:12
○MXforward20.nameresolvers.com2015-08-06 → 2016-03-10 · 4 obs
● 2015-08-06 18:02:18
● 2016-03-10 10:57:06
○ 2016-07-07 05:45:08
○ 2026-08-12 23:17:12
●A13.56.33.82026-02-17 → 2026-08-12 · 3 obs
○ 2020-03-20 02:20:06
● 2026-02-17 16:15:04
● 2026-08-12 23:17:12
○A160.124.177.72020-03-20 → 2020-03-20 · 4 obs
○ 2017-03-19 01:37:38
● 2020-03-20 02:20:06
○ 2026-02-17 16:15:04
○ 2026-08-12 23:17:12
○A216.13.106.1192016-03-10 → 2016-03-10 · 4 obs
○ 2015-11-27 23:21:46
● 2016-03-10 10:57:06
○ 2016-07-07 05:45:08
○ 2026-08-12 23:17:12
○A216.13.106.542015-08-06 → 2015-11-27 · 4 obs
● 2015-08-06 18:02:18
● 2015-11-27 23:21:46
○ 2016-03-10 10:57:06
○ 2026-08-12 23:17:12
○A34.206.157.642017-03-19 → 2017-03-19 · 4 obs
○ 2016-07-07 05:45:08
● 2017-03-19 01:37:38
○ 2020-03-20 02:20:06
○ 2026-08-12 23:17:12
○A54.236.195.152017-03-19 → 2017-03-19 · 4 obs
○ 2016-07-07 05:45:08
● 2017-03-19 01:37:38
○ 2020-03-20 02:20:06
○ 2026-08-12 23:17:12
○CNAMEhdredirect-lb3-890977680.us-east-1.elb.amazonaws.com2017-03-19 → 2017-03-19 · 3 obs
● 2017-03-19 01:37:38
○ 2020-03-20 02:20:06
○ 2026-08-12 23:17:12

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
coml.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...-
jamzen.comns1.brandbucket.com, ns2.brandbucket.com2 records

✅ Authoritative Response

Server:54.241.53.41

NS records: ns1.brandbucket.com, ns2.brandbucket.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for jamzen.com (unsigned zone)

⏱️ Timing

Total: 229ms | Queries: -

📄 Records

TypeCountSample Data
A113.56.33.8
NS2ns1.brandbucket.com, ns2.brandbucket.com
TXT3v=spf1 -all, 27aab5373841b85aab94982ee19ab62f96481ed6...
SOA1ns1.brandbucket.com mail.jamzen.com

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.brandbucket.com, ns2.brandbucket.com)

Analysis

IP Addresses

jamzen.com has exactly one IP address — 13.56.33.8.

pixelcitizen.com, ninola.com, viaz.com plus two other host names have IP numbers in common with jamzen.com.

Name Servers

Two name servers handle the delegation for jamzen.com: ns1.brandbucket.com and ns2.brandbucket.com.

The name server configuration of jamzen.com is shared with other domains, for instance pomozo.com, lezune.com, kassea.com and two others.

At least some of jamzen.com's name servers are shared with other domains, for example vatomi.com and beatsugar.com.

ns1.brandbucket.com and ns2.brandbucket.com both carry two IP addresses. The A records for ns1.brandbucket.com are 54.241.53.41 and 2600:1f1c:800:8b01:2ba3:bb61:44fb:b361; the A records for ns2.brandbucket.com are 18.221.52.246 and 2600:1f16:54:8701:4012:7e34:5c5f:95a8.