maine.gov

Maine.gov

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

Libraries

jQuery

Infrastructure

Amazon CloudFront · Apache

Overview

Status

alive

Registered

not looked up yet

First seen here

2026-09-21

Security grade

D (65/100, from headers & TLS)

Privacy score

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

Hosting

unknown

Linked to from

9 other sites seen so far

What to fix

1. Add Strict-Transport-Security
   Header: Strict-Transport-Security: max-age=31536000; includeSubDomains
2. Add X-Content-Type-Options
   Header: X-Content-Type-Options: nosniff
3. 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

Recent changes

• 2026-09-22 — TLS expiry changed from "2027-03-22" to "2027-03-22"

Badge

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

<a href="https://webtelemetry.dev/site/maine.gov"><img src="https://webtelemetry.dev/badge/maine.gov.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.