denverbroncoscommunity.com

Home | DenverBroncosCommunity

Built with

Frontend framework

Next.js

Also detected

Infrastructure

Vercel

Overview

Status

alive

Registered

2026-03-19 (6 months ago)

First seen here

2026-09-22

Security grade

F (55/100, from headers & TLS)

Privacy score

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

Hosting

Amazon.com, Inc. · AS16509 · United States

Server header

Vercel

Response time

258 ms to first byte, measured from our crawler

TLS certificate

Let's Encrypt · TLSv1.3 · expires 2026-10-20

Language

en

Mobile-ready

yes (viewport meta tag)

RSS / Atom feed

yes

Linked to from

0 other sites seen so far

What to fix

1. 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.
2. Add X-Content-Type-Options
   Header: X-Content-Type-Options: nosniff
3. Prevent clickjacking
   Header: X-Frame-Options: DENY (or a CSP frame-ancestors directive).
4. Add a Referrer-Policy
   Header: Referrer-Policy: strict-origin-when-cross-origin
5. Publish an SPF record
   A DNS TXT record listing who may send email for this domain, which prevents spoofing.
6. 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/denverbroncoscommunity.com"><img src="https://webtelemetry.dev/badge/denverbroncoscommunity.com.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.