diskusjon.no security report

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

46risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

1High

2Medium

4Low

2Info

Collected 12 hours ago24.0sfrom cache

Certificate Transparency7
DNS resolution11
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs34
Registration
DNS posture2
Email authentication1
Certificate
Security headers3
Archived URLs
Analysis9

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.

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.diskusjon.no TXT "v=DMARC1; p=none; rua=mailto:dmarc@diskusjon.no"`, review the reports, then move to p=quarantine and p=reject.
asset: diskusjon.no
The browser will also send this cookie over plain http://, where it can be captured.
What to do
Add `Secure` to the cookie.
asset: https://www.diskusjon.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: diskusjon.no
beta.diskusjon.no appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: beta.diskusjon.no
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.diskusjon.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.diskusjon.no/
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: diskusjon.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: diskusjon.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: diskusjon.no

final https://www.diskusjon.no/status 200time 1621msstack cloudflare

✓http:// redirects to https://
!Strict-Transport-Security
max-age=86400
✓Content-Security-Policy
frame-ancestors 'self' https://www.gamer.no *.ggez.no https://forum.kvinneguiden.no;
✓Clickjacking protection
via CSP frame-ancestors
✗X-Content-Type-Options
✓Referrer-Policy
strict-origin-when-cross-origin
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✓Cookie tek_dno4_IPSSessionFront
Secure · HttpOnly · SameSite=none
✗Cookie __cflb
no Secure · HttpOnly · SameSite=lax

✓Receives mail via 3 servers
route1.mx.cloudflare.net route2.mx.cloudflare.net route3.mx.cloudflare.net
✓SPFends in -all
v=spf1 a mx include:_spf.google.com include:_spf.mx.cloudflare.net ip4:185.47.42.63/32 ip6:2a02:c0:4f0:6200::/64 ip4:87.238.54.143/32 ip6:2a02:c0:1002:200:f816:3eff:fecc:3ee9/128 -all
✗DMARC
no record
!MTA-STSinbound mail can be downgraded to plaintext

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

✓Registered with Domeneshop AS3.7 years old
diskusjon.no
–Registration expiry
✗Transfer lock
none
✓2 nameservers at registry
neil.ns.cloudflare.com tegan.ns.cloudflare.com

Address	Ports	Edge	Network
172.67.197.250 www.diskusjon.no +4	80443205220532082208320862087+5	Cloudflare~	—
104.21.76.173 www.diskusjon.no +2	80443205220532082208320862087+5	Cloudflare~	—
13.35.36.127 consent.diskusjon.no +2	80443	direct	—
13.35.36.105 consent.diskusjon.no +3	80443	direct	—
13.35.36.56 consent.diskusjon.no +15	80443	direct	—
13.35.36.89 consent.diskusjon.no +2	80443	direct	—
87.238.37.70 beta.diskusjon.no	none known	direct	—
87.238.37.69 beta.diskusjon.no	none known	direct	—
87.238.37.68 beta.diskusjon.no	none known	direct	—

Archived URLs

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

diskusjon.no security report

Moderate

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames