onelink.to

Onelink.to

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

2011-12-09 (15 years ago)

First seen here

2026-09-22

Security grade

F (50/100, from headers & TLS)

Privacy score

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

Hosting

DigitalOcean, LLC · AS14061 · Netherlands

Server header

nginx

Response time

57 ms to first byte, measured from our crawler

TLS certificate

Let's Encrypt · TLSv1.3 · expires 2026-11-05

Language

en

Mobile-ready

yes (viewport meta tag)

Linked to from

0 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, and is the main defense against XSS. Start with Content-Security-Policy-Report-Only to test.
3. Add X-Content-Type-Options
   Header: X-Content-Type-Options: nosniff
4. Add a Referrer-Policy
   Header: Referrer-Policy: strict-origin-when-cross-origin

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/onelink.to"><img src="https://webtelemetry.dev/badge/onelink.to.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.