jellycode.pt - dns.ninja
jellycode.pt
pt
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | curiosity.dns.pt ⭐ | ||||||
| NS | a.dns.pt | ||||||
| NS | b.dns.pt | ||||||
| NS | c.dns.pt | ||||||
| NS | d.dns.pt | ||||||
| NS | e.dns.pt | ||||||
| NS | g.dns.pt | ||||||
| NS | h.dns.pt | ||||||
| NS | ns.dns.br | ||||||
| NS | ns2.nic.fr | ||||||
| SOA | curiosity.dns.ptrequest@dns.pt 2026-07-19 #24 | ||||||
Subdomains
cpanel.jellycode.pt |
servidor02.jellycode.pt |
proposals.jellycode.pt |
Same first word
Similar names
DNS History
13 records (10 active, 3 former)
○NSns1.jellycode.pt2015-07-19 → 2016-12-01 · 4 obs
● 2016-12-01 07:25:44
○ 2026-03-03 09:26:32
○ 2026-07-19 11:46:20
●NSns1.webhs.org2026-03-03 → 2026-07-19 · 3 obs
● 2026-03-03 09:26:32
● 2026-07-19 11:46:20
○NSns2.jellycode.pt2015-07-19 → 2016-12-01 · 4 obs
● 2016-12-01 07:25:44
○ 2026-03-03 09:26:32
○ 2026-07-19 11:46:20
●NSns2.webhs.org2026-03-03 → 2026-07-19 · 3 obs
● 2026-03-03 09:26:32
● 2026-07-19 11:46:20
●NSns3.webhs.org2026-03-03 → 2026-07-19 · 3 obs
● 2026-03-03 09:26:32
● 2026-07-19 11:46:20
●NSns4.webhs.org2026-03-03 → 2026-07-19 · 3 obs
● 2026-03-03 09:26:32
● 2026-07-19 11:46:20
●MXalt1.aspmx.l.google.com2015-07-19 → 2026-07-19 · 2 obs
● 2026-07-19 11:46:20
●MXalt2.aspmx.l.google.com2015-07-19 → 2026-07-19 · 2 obs
● 2026-07-19 11:46:20
●MXaspmx.l.google.com2015-07-19 → 2026-07-19 · 2 obs
● 2026-07-19 11:46:20
●MXaspmx2.googlemail.com2015-07-19 → 2026-07-19 · 2 obs
● 2026-07-19 11:46:20
●MXaspmx3.googlemail.com2015-07-19 → 2026-07-19 · 2 obs
● 2026-07-19 11:46:20
●A185.90.56.352026-03-03 → 2026-07-19 · 3 obs
● 2026-03-03 09:26:32
● 2026-07-19 11:46:20
○A94.126.171.2052015-07-19 → 2016-12-01 · 4 obs
● 2016-12-01 07:25:44
○ 2026-03-03 09:26:32
○ 2026-07-19 11:46:20
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| pt | e.dns.pt, c.dns.pt, b.dns.pt, a.dns.pt... | 15 records |
| jellycode.pt | ns1.webhs.org, ns4.webhs.org, ns3.webhs.org, ns2.webhs.org | - |
✅ Authoritative Response
Server:194.39.124.5
NS records: ns1.webhs.org, ns4.webhs.org, ns3.webhs.org, ns2.webhs.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for jellycode.pt (unsigned zone)
⏱️ Timing
Total: 1228ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 185.90.56.35 |
| NS | 4 | ns2.webhs.org, ns3.webhs.org... |
| MX | 5 | alt1.aspmx.l.google.com (pri: 20), alt2.aspmx.l.google.com (pri: 20)... |
| TXT | 1 | v=spf1 ip4:185.90.56.35 include:_spf.spa |
| SOA | 1 | ns1.webhs.org reports.webhs.support |
📌 Glue Records Collected
Total: 15
In-bailiwick: 13 (a.dns.pt, b.dns.pt, c.dns.pt...)
Out-of-bailiwick: 2 (ns2.nic.fr, ns.dns.br)
Analysis
Hierarchy
jellycode.pt is a parent domain, with cpanel.jellycode.pt, servidor02.jellycode.pt and proposals.jellycode.pt beneath it.
IP Addresses
jellycode.pt resolves to just one IP address, 185.90.56.35.
Two other host names, along with saf.pt, hosting25.serverhs.org and rogeriocruzeiro.com, also share IP numbers with jellycode.pt.
Name Servers
The NS records for jellycode.pt point to four name servers: ns1.webhs.org, ns2.webhs.org, ns3.webhs.org and ns4.webhs.org.
jellycode.pt has at least partial name server overlap with other domains, such as c2group.pt, pmc.pt, restauranteosonho.com and two others.
The hosts ns1.webhs.org, ns2.webhs.org, ns3.webhs.org and ns4.webhs.org all resolve to exactly one IP address each: 194.39.124.5, 185.90.56.55, 51.158.100.205 and 194.39.127.1 respectively.
Mail Servers
Mail for jellycode.pt is handled by five mail servers, namely aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
There is at least a partial MX overlap between jellycode.pt and other domains, including taragill.com, mymsp2.21st.se, c2capital.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, alt4.aspmx.l.google.com and 3 others.
Host names that have two IP addresses:
aspmx2.googlemail.com directs traffic to 108.177.123.27 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 172.253.63.26 and 2607:f8b0:4004:c06::1b.
alt1.aspmx.l.google.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1a.