no-ip.org
FNo-IP | Smarter DNS Starts Here
Built with
- CMS
- WordPress
Also detected
- Infrastructure
- Nginx
- Third-party services
- Google Tag Manager
Overview
- Status
- alive
- Registered
- not looked up yet
- First seen here
- 2026-09-21
- Security grade
- F (55/100, from headers & TLS)
- Privacy score
- 84/100 (0 third-party script hosts, 1 tracking/marketing services)
- Hosting
- unknown
- Linked to from
- 8 other sites seen so far
What to fix
- Add Strict-Transport-Security
Header: Strict-Transport-Security: max-age=31536000; includeSubDomains - 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. - Mark cookies Secure and HttpOnly
At least one cookie is sent without these flags, exposing it to interception or scripts. - 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
Recent changes
- 2026-09-22: TLS expiry changed from "2027-02-22" to "2027-02-22"
Badge
Show this site's security grade in a README or footer:

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