playwekings.mobi

Викинги

Built with

No platform, CMS or framework detected. Detection is passive — it only sees what a site exposes in its HTML, headers and cookies — so custom or well-hidden stacks show up as nothing rather than as a guess.

Also detected

Infrastructure

Nginx

Overview

Status

alive

Registered

not looked up yet

First seen here

2026-09-22

Security grade

F (50/100, from headers & TLS)

Privacy score

90/100 (0 third-party script hosts, 0 tracking/marketing services)

Hosting

unknown

Linked to from

2 other sites seen so far

What to fix

1. Add Strict-Transport-Security
   Header: Strict-Transport-Security: max-age=31536000; includeSubDomains
2. Add a Content-Security-Policy
   Limits which scripts can run — the main defense against XSS. Start with Content-Security-Policy-Report-Only to test.
3. Add a Referrer-Policy
   Header: Referrer-Policy: strict-origin-when-cross-origin
4. Mark cookies Secure and HttpOnly
   At least one cookie is sent without these flags, exposing it to interception or scripts.
5. Publish a DMARC record
   A TXT record at _dmarc.<domain>; start with v=DMARC1; p=none; to monitor.

Security & email signals

• ✓ HTTPS
• ✗ HSTS
• ✗ Content-Security-Policy
• ✓ X-Content-Type-Options
• ✓ X-Frame-Options
• ✗ Referrer-Policy
• ✗ Permissions-Policy
• ✓ SPF record
• ✗ DMARC record
• ✗ DKIM record
• ✗ Cookies set securely
• ✓ Has real content (not an empty shell)
• ✓ Valid TLS certificate

Badge

Show this site's security grade in a README or footer:

<a href="https://webtelemetry.dev/site/playwekings.mobi"><img src="https://webtelemetry.dev/badge/playwekings.mobi.svg" alt="Security grade"></a>

Generated automatically from passive, publicly observable data. Think something here is wrong or want this profile removed? See /bot. Machine-readable: JSON.