DNS Gurus
Cached · just now
89/100 SECURITY SCORE

Certificate Information

Subject
C=US, ST=California, O=Apple Inc., CN=theapplestore.com.pt
Issuer
C=US, O=Apple Inc., CN=Apple Public Server RSA CA 1 - G1
Valid From
March 31, 2026
Valid Until
June 29, 2026 56 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
67:4C:AC:AF:59:D9:DD:9D:54:4B:9F:DE:1D:21:4D:B4:7F:55:A9:9C:36:19:E0:56:60:4B:EB:76:20:34:3D:73
Alternative Names
60 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
Present
max-age=31536000; includeSubdomains
Content-Security-Policy
Basic
default-src; connect-src; script-src; +4 more Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Missing
Not configured
Recommendations
  • • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • • Improve CSP by adding more specific directives and removing 'unsafe-inline'
  • • Consider adding Permissions-Policy to control browser features

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