journalisten.no security report

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

45risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

0High

5Medium

2Low

2Info

Collected 7 hours ago5.6sfrom cache

Certificate Transparency
DNS resolution2
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs4
Registration
DNS posture3
Email authentication2
Certificate
Security headers0
Archived URLs
Analysis9

noteCertificate Transparency did not complete (HTTP 502). 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.

Without HSTS the browser will still try http:// first on a fresh visit, which is the window an on-path attacker uses.
What to do
Send `Strict-Transport-Security: max-age=31536000; includeSubDomains` once you are sure everything works over HTTPS.
asset: https://www.journalisten.no/
CSP is the main defence that limits what an injected script can do. Without it, any XSS bug is fully exploitable.
What to do
Start with a report-only policy, tighten it against the reports, then enforce.
asset: https://www.journalisten.no/
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.journalisten.no/
Receivers are asked to report spoofing but not to block it. This is the right first step, and the wrong place to stop.
What to do
Once reports look clean, move to p=quarantine, then p=reject.
asset: journalisten.no
Without clientTransferProhibited, a compromised registrar account can move the domain to another registrar in days, with no second step.
What to do
Enable the transfer lock (and registrar lock, if offered) in the registrar control panel.
asset: journalisten.no
Lets browsers guess content types, which turns some upload and text endpoints into script injection points.
What to do
Send `X-Content-Type-Options: nosniff` on every response.
asset: https://www.journalisten.no/
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.journalisten.no/
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: journalisten.no
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: journalisten.no

final https://www.journalisten.no/status 200time 1508msstack cloudflare

✓http:// redirects to https://
✗Strict-Transport-Security
✗Content-Security-Policy
✗Clickjacking protection
✗X-Content-Type-Options
✗Referrer-Policy
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✓Receives mail via 1 server
journalisten-no.mail.protection.outlook.com
✓SPFends in -all
v=spf1 include:_spf.ramsalt.com include:spf.protection.outlook.com -all
!DMARCp=none
v=DMARC1; p=none; pct=100
!MTA-STSinbound mail can be downgraded to plaintext

✓DNSSECanswers are signed and validated
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓3 nameservers
ns1.hyp.net ns2.hyp.net ns3.hyp.net

✓Registered with Domeneshop AS11.2 years old
journalisten.no
–Registration expiry
✗Transfer lock
none
✓3 nameservers at registry
ns1.hyp.net ns2.hyp.net ns3.hyp.net

Address	Ports	CVEs	Edge	Network
15.197.188.249 journalisten.no +2	80443	0	direct	—
3.33.166.206 journalisten.no +2	80443	0	direct	—

Archived URLs

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

journalisten.no security report

Moderate

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames