DNS Gurus
Cached · just now
83/100 SECURITY SCORE

Certificate Information

Subject
CN=cloudsponge.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M03
Valid From
April 23, 2025
Valid Until
May 23, 2026 128 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
2B:1F:8C:9E:0D:F7:1E:A1:C8:01:EC:E6:17:48:0F:55:65:FD:AD:45:07:FD:C9:06:B2:10:99:DC:91:F5:C4:11
Alternative Names
2 domains

Security Configuration

TLS Protocols
TLS 1.0 TLS 1.1 TLS 1.2
Forward Secrecy
Limited (Check cipher configuration)
Warnings
  • • TLS 1.3 is not supported (recommended)
  • • TLS 1.1 is deprecated and should be disabled
  • • TLS 1.0 is deprecated and should be disabled

HTTP Security Headers

Status
Strict-Transport-Security
Present
max-age=31536000
Content-Security-Policy
Basic
default-src; font-src; img-src; +6 more
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
camera=(), gyroscope=(), microphone=(), usb=(), payment=(), geolocation=(), fullscreen=(self)
Recommendations
  • • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • • 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

2 domains
cloudsponge.com *.cloudsponge.com