DNS Gurus
Open Cached · just now
81/100 SECURITY SCORE

Certificate Information

Subject
CN=bigstarsoftwares.com.br
Issuer
C=US, O=Google Trust Services, CN=WR1
Valid From
November 22, 2025
Valid Until
February 20, 2026 80 days
Public Key
RSA 4096 bit Strong
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
65:0B:56:07:FE:F9:8F:5C:70:8D:3F:AA:77:98:85:70:E2:90:A6:B9:5D:11:C5:53:9D:C3:47:A6:7C:91:80:B0
Alternative Names
2 domains

Security Configuration

TLS Protocols
TLS 1.2 TLS 1.3
Forward Secrecy
Supported (Modern clients use PFS)

HTTP Security Headers

Status
Strict-Transport-Security
Missing
Not configured
Content-Security-Policy
Weak
upgrade-insecure-requests
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • • Add Strict-Transport-Security header with max-age of at least 1 year
  • • Significantly strengthen CSP directives
  • • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
  • • Add X-Content-Type-Options: nosniff
  • • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
  • • Consider adding Permissions-Policy to control browser features

CAA Records (Certificate Authority Authorization)

CAA Records
Configured (Restricts certificate issuance)
Current Issuer
Authorized (Matches CAA policy)
Authorized CAs
sectigo.com digicert.com letsencrypt.org globalsign.com pki.goog comodoca.com
Wildcard CAs
pki.goog globalsign.com comodoca.com digicert.com letsencrypt.org sectigo.com
Recommendations
  • • Consider using critical flag (flags=128) for stricter CAA enforcement
  • • You have authorized 6 CAs - consider limiting to only the CAs you actively use
  • • Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts