DNS Gurus
Cached · just now
93/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 6
Let's Encrypt logo Let's Encrypt Firebase logo Firebase Google API JS Client logo Google API JS Client Google Sign-In logo Google Sign-In Plausible Analytics logo Plausible Analytics Google Cloud Storage logo Google Cloud Storage

Certificate Information

Subject
CN=sharpenlyapp.com
Issuer
C=US, O=Let's Encrypt, CN=YR2
Valid From
September 06, 2026
Valid Until
December 05, 2026 88 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
A3:67:E4:B6:D5:87:C5:70:AD:CA:05:04:1D:32:95:97:C2:A9:E8:4C:EB:F1:CB:F5:C8:C8:BC:8A:F5:7F:14:8C
Alternative Names
1 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
Excellent
max-age=63072000; includeSubDomains; preload
Content-Security-Policy
Google Sign-In logo
Basic
default-src; script-src; style-src; +8 more Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
camera=(), microphone=(), geolocation=(); +1 more
Recommendations
  • • Improve CSP by adding more specific directives and removing 'unsafe-inline'

CAA Records (Certificate Authority Authorization)

CAA Records
Not Configured (Any CA can issue certificates)
CAA Issues
  • • No CAA records configured - any CA can issue certificates
Recommendations
  • • Implement CAA records to restrict which CAs can issue certificates for your domain
  • • This adds an extra layer of security against unauthorized certificate issuance
  • • Example: Add CAA record 'example.com. CAA 0 issue "letsencrypt.org"'
  • • Consider adding 'iodef' record to receive security incident reports

Subject Alternative Names

1 domain
sharpenlyapp.com