Domain > whynohttps.com

More information on this domain is in AlienVault OTX

DNS Resolutions

Date	IP Address
2024-08-18	104.21.15.181 (ClassC)
2025-01-18	172.67.163.191 (ClassC)

HTTP/1.1 200 OKDate: Sun, 27 Aug 2023 20:26:44 GMTContent-Type: text/html; charsetutf-8Transfer-Encoding: chunkedConnection: keep-aliveCache-Control: public, max-age14400expires: Sun, 27 Aug 2023 22:5

html langen>head>  title>Why No HTTPS? The World's Largest Websites Not Redirecting Insecure Requests to HTTPS/title>  link relshortcut icon href/favicon.ico>  link relstylesheet typetext/css hrefhttps://fonts.googleapis.com/css?familyVollkorn:400,400italic,700,700italic>  meta propertyog:image contenthttps://whynohttps.com/content/not-secure.png />  meta propertyog:title contentWhy No HTTPS? The World's Largest Websites Not Redirecting Insecure Requests to HTTPS />  meta propertyog:description contentWith the web rapidly becoming secure by default, "Why No HTTPS?" is a who's who of the world's biggest websites globally and by country still not defaulting to HTTPS. />  meta propertyog:type contentwebsite />  meta propertyog:url contenthttps://whynohttps.com/ />  meta nametwitter:card contentsummary_large_image />  meta nametwitter:title contentWhy No HTTPS? The World's Largest Websites Not Redirecting Insecure Requests to HTTPS />  meta nametwitter:description contentWith the web rapidly becoming secure by default, "Why No HTTPS?" is a who's who of the world's biggest websites globally and by country still not defaulting to HTTPS. />  meta nametwitter:image contenthttps://whynohttps.com/content/not-secure.png />  meta nametwitter:url contenthttps://whynohttps.com/ />  meta nameviewport contentwidthdevice-width, initial-scale1 />  meta http-equivContent-Language contenten />  meta namegoogle contentnotranslate />  link href/Content/site.css relstylesheet/>/head>body>  div>      h1>Why No HTTPS?/h1>    p>  HTTPS is now free, easy and increasingly ubiquitous. Its also now required if you dont want  a hrefhttps://security.googleblog.com/2018/02/a-secure-web-is-here-to-stay.html>Google Chrome flagging the site as "Not secure"/a>.  Yet still, many of the worlds largest websites continue to serve content over unencrypted  connections, a hrefhttps://www.troyhunt.com/heres-why-your-static-website-needs-https/>putting users at risk even when no sensitive data is inv

View on OTX | View on ThreatMiner

Data with thanks to AlienVault OTX, VirusTotal, Malwr and others. [Sitemap]

Domain > whynohttps.com

Is this malicious?

DNS Resolutions

Port 443