journeyera.com security report

Certificate, security headers, email authentication, DNS, registration, and exposed hosts — from public sources.

67risk

Elevated

Several issues worth triaging this week.

0Critical

3High

3Medium

3Low

2Info

Collected 21 hours ago137.1sfrom cache

Certificate Transparency
DNS resolution2
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs26
Registration
DNS posture2
Email authentication1
Certificate
Security headers3
Archived URLs
Analysis11

noteCertificate Transparency did not complete (20). Results below are partial.
noteCertificate inspection is unavailable in this runtime.
noteNetwork ownership lookup is unavailable in this runtime; ASN and org are omitted.
noteCDN/WAF detection is unavailable in this runtime.
note2 hosts were identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

Shodan matched these CVEs against the service banners it saw on 104.21.44.175 (journeyera.com), which advertise php 8.3.33. These are version-fingerprint matches, not confirmed exploits: a distribution may have back-ported the fix while leaving the banner unchanged. Severity reflects the volume of known issues associated with this host, not a CVSS score. CVE-2013-2220 CVE-2007-3205
What to do
Confirm the running versions on 104.21.44.175 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2013-2220 ↗CVE-2007-3205 ↗
asset: 104.21.44.175
Shodan matched these CVEs against the service banners it saw on 172.67.202.93 (journeyera.com), which advertise php 8.3.33. These are version-fingerprint matches, not confirmed exploits: a distribution may have back-ported the fix while leaving the banner unchanged. Severity reflects the volume of known issues associated with this host, not a CVSS score. CVE-2013-2220 CVE-2007-3205
What to do
Confirm the running versions on 172.67.202.93 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2013-2220 ↗CVE-2007-3205 ↗
asset: 172.67.202.93
SPF and DKIM alone do not protect the From: address a person sees. Without DMARC, a spoofed message can pass SPF for some other domain and still display yours.
What to do
Publish `_dmarc.journeyera.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@journeyera.com"`, review the reports, then move to p=quarantine and p=reject.
asset: journeyera.com
104.21.44.175 (journeyera.com) reports php 8.3.33. Publishing precise versions lets anyone match the host against a CVE feed without probing it, which is how targets get shortlisted for mass exploitation after a new advisory lands.
What to do
Suppress version tokens in server banners (for example `ServerTokens Prod` in Apache) and keep the packages current.
asset: 104.21.44.175
172.67.202.93 (journeyera.com) reports php 8.3.33. Publishing precise versions lets anyone match the host against a CVE feed without probing it, which is how targets get shortlisted for mass exploitation after a new advisory lands.
What to do
Suppress version tokens in server banners (for example `ServerTokens Prod` in Apache) and keep the packages current.
asset: 172.67.202.93
No X-Frame-Options or CSP frame-ancestors directive, so another site can load this page invisibly inside its own and trick users into clicking.
What to do
Send `X-Frame-Options: DENY` or `Content-Security-Policy: frame-ancestors ’none’`.
asset: https://www.journeyera.com/
Browsers and the preload list expect at least six months; shorter values give little protection between visits.
What to do
Raise max-age to 31536000 (one year).
asset: https://www.journeyera.com/
Full URLs — including any tokens or IDs in them — are sent to every third party the page links to.
What to do
Send `Referrer-Policy: strict-origin-when-cross-origin`.
asset: https://www.journeyera.com/
Answers for this domain are not signed, so a resolver cannot tell a forged response from a real one.
What to do
Enable DNSSEC at your DNS host and publish the DS record at the registrar.
asset: journeyera.com
Mail to this domain can be downgraded to plaintext by an on-path attacker, because senders have no way to know TLS is required.
What to do
Publish an MTA-STS policy (a TXT record plus a small HTTPS-hosted file).
asset: journeyera.com
Any public certificate authority may issue certificates for this domain. CAA lets you name the ones allowed to.
What to do
Add a CAA record naming your CA, e.g. `0 issue "letsencrypt.org"`.
asset: journeyera.com

final https://www.journeyera.com/status 200time 833msstack cloudflare

✓http:// redirects to https://
!Strict-Transport-Security
max-age=15552000; preload
✓Content-Security-Policy
block-all-mixed-content, block-all-mixed-content;
✗Clickjacking protection
✓X-Content-Type-Options
nosniff
✗Referrer-Policy
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✓Cookie __cf_bm
Secure · HttpOnly · SameSite=none

✓Receives mail via 3 servers
mx.zoho.com mx2.zoho.com mx3.zoho.com
!SPFends in ~all
v=spf1 include:zoho.com ~all
✗DMARC
no record
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
✓IPv6 (AAAA)
✓2 nameservers
quinton.ns.cloudflare.com surina.ns.cloudflare.com

✓Registered with PDR Ltd. d/b/a PublicDomainRegistry.com10.8 years old
journeyera.com
✓Registration expiry808 days
2028-11-23
✓Transfer lock
client transfer prohibited
✓2 nameservers at registry
quinton.ns.cloudflare.com surina.ns.cloudflare.com

Address	Ports	CVEs	Edge	Network
104.21.44.175 journeyera.com +2	80443205220532082208320862087+5	2	Cloudflare~	—
172.67.202.93 journeyera.com +1	80443205220532082208320862087+5	2	Cloudflare~	—

Archived URLs

Endpoints the Wayback Machine has kept — config files, backups, scripts. Slow to fetch, so it is here on request.

journeyera.com security report

Elevated

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames