neptun.in.ua

Readiness by lane

Green: neptun.in.ua. Thin bar: GPS Navigation & Maps peer median.

Priority fixes for neptun.in.ua

Ordered by impact and by how common each practice is among peers.

1. Priority 1 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 1 external script without async or defer.

   Why it matters: A plain <script src> in the head stops the browser from showing anything until that file has downloaded and run.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   On Next.js: Use the next/script component with an appropriate loading strategy.

   63% of GPS Navigation & Maps peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

   Guide: Control Third-Party Scripts Before They Control Your Page

2. Priority 2 · Harden

   DMARC policy enforces quarantine or reject

   Observed: No DMARC record was found at _dmarc.neptun.in.ua.

   What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.

   38% of GPS Navigation & Maps peers do this.

   Guide: A Practical Website Health Check for Owners

3. Priority 3 · Harden

   CAA records limit who can issue certificates

   Observed: No CAA record was found for neptun.in.ua, so any public certificate authority may issue for it.

   What to do: Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.

   On Cloudflare: Cloudflare documents which CAs its managed certificates need; include them in your CAA records.

   18% of GPS Navigation & Maps peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Harden

   security.txt published

   Observed: No valid /.well-known/security.txt with a Contact field was returned.

   What to do: Publish /.well-known/security.txt with at least Contact and Expires fields, as RFC 9116 requires, and review it before it expires.

   On Cloudflare: Cloudflare Security Center can serve a security.txt file for the zone.

   8.5% of GPS Navigation & Maps peers do this.

   Guide: A Practical Website Health Check for Owners

What neptun.in.ua already does well

Practices fewer than half of GPS Navigation & Maps peers use.

• Referrer-Policy setReferrer-Policy present.21% of peers
• Content Security Policy presentContent-Security-Policy present.28% of peers
• HTTP/3 advertisedHTTP/3 advertised.35% of peers

What we saw

Homepage checked

https://neptun.in.ua/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 90-day validity, expiring 2026-12-09

CDN or edge

Cloudflare

Platform or framework

Next.js

DNS operators

Cloudflare

HSTS

max-age 730 days, includeSubDomains, preload

Homepage HTML

131 KB, br

Images on homepage

6 (png 3, webp 3)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

Stack and providers

Seen in the homepage response, certificate and DNS. Provider pages compare how their customers configure the same checks.

All 31 checks

Select a gap for the method and fix. How each check works

Compare with other GPS Navigation & Maps sites

• garmin.com77
• gdebenz.ru79
• komoot.com77
• openstreetmap.org81
• waze.com89

GPS Navigation & Maps readiness benchmark