HTTPS, SSL & Security Report for www.apr.gov.rs

This report summarizes how well www.apr.gov.rs is configured for secure web delivery. It covers HTTPS availability, HTTP→HTTPS redirects, TLS/SSL certificate validity, security headers, HTTP/2 and HTTP/3 support, and mixed content. Use it to quickly spot configuration gaps and improve your site's security and trust.

Not secureScore0/100Last checked: 30 Apr 2026 at 13:47 UTCRefresh report
HTTPS

Disabled

HTTP → HTTPS

No

TLS

F · 1.2, 1.3

Security headers

Check error

HTTPS endpoint is not accessible

Detailed checks

HTTPS availability

The site could not be reached over HTTPS or returned an error.

Why it matters: HTTPS encrypts traffic and protects user data.

HTTP to HTTPS redirect

No redirect from HTTP to HTTPS was detected.

How to fix: Configure your server (Nginx, Apache, or host) to 301/302 redirect http:// to https://.

TLS & CertificateF

ValidNo

Why it matters: A valid, non-expired certificate ensures encryption is trusted by browsers.

To improve your grade

  • Fix the SSL certificate to improve the grade.
Grade breakdown1 thing to improve for a higher grade →
0/100 pts
HTTPS Connection
+0/25
HTTP to HTTPS Redirect
+0/20
Valid SSL Certificate
+0/20
Certificate Not Expiring Soon
+0/10
Fast Response Time
+0/10
Short Redirect Chain
+0/5
HSTS Enabled
+0/5
Security Headers
+0/5

Requires 4 of 6 headers and Content-Security-Policy (CSP).

To improve your grade

  • Fix the SSL certificate to improve the grade.

DNS Security

CAA: Not set · DNSSEC: Not signedExpand
CAANot set
DNSSEC
Not signed

No CAA records. Any CA can issue certificates. Consider adding CAA to restrict issuance.

Redirect chain422ms total

When you visit the site over HTTP, the server may send you through one or more redirects until you land on the final HTTPS URL. Shorter chains are faster and better for SEO.

  1. 1.http://www.apr.gov.rs422ms

Domain owner? If you want this report removed or made private, contact us.