hogum
havanindurumu.com

havanindurumu.com security report

Certificate, security headers, email authentication, DNS, registration, and exposed hosts — from public sources.

37risk

Moderate

Some surface to tighten, nothing urgent.

0Critical
1High
1Medium
2Low
0Info
Collected 1.9sfrom cache
  1. Certificate Transparency
  2. DNS resolution1
  3. Network ownership0
  4. CDN / WAF detection0
  5. Exposed ports & CVEs11
  6. Registration
  7. DNS posture1
  8. Email authentication2
  9. Certificate
  10. Security headers5
  11. Archived URLs
  12. Analysis4
  • noteCertificate Transparency did not complete (HTTP 404). Results below are partial.
  • noteCertificate inspection is unavailable in this runtime.
  • noteNetwork ownership lookup is unavailable in this runtime; ASN and org are omitted.
  • noteCDN/WAF detection is unavailable in this runtime.
final https://havanindurumu.com/status 403time 955msstack cloudflare
  • http:// redirects to https://
  • Strict-Transport-Security
    max-age=63072000; includeSubDomains; preload
  • Content-Security-Policy
  • Clickjacking protection
    SAMEORIGIN
  • X-Content-Type-Options
    nosniff
  • Referrer-Policy
    strict-origin-when-cross-origin
  • Permissions-Policy
    geolocation=(), camera=(), microphone=(), payment=()
  • security.txt publishedoptional — tells researchers where to report bugs
  • Receives mail via 1 server
  • SPFends in -all
    v=spf1 a mx a:havanindurumu.com ip4:37.27.53.158 ip6:2a01:4f9:3081:3c14::2 -all
  • DMARCp=reject
    v=DMARC1; p=reject; adkim=r; aspf=r; pct=100; rua=mailto:dmarc@havanindurumu.com; ruf=mailto:dmarc@havanindurumu.com; fo=1
  • MTA-STSinbound mail must use TLS
  • !DNSSECanswers can be forged
  • CAA
    0 issuewild "letsencrypt.org"
  • IPv6 (AAAA)
  • 1 nameserver
AddressPortsCVEsEdgeNetwork
37.27.53.158
255380110143443465587+3
0direct
Archived URLs

Endpoints the Wayback Machine has kept — config files, backups, scripts. Slow to fetch, so it is here on request.