Comment on What is stopping a scammer from HTTPS certificating a "nonsense.ReputableBank.com"

• elvith@feddit.org ⁨4⁩ ⁨days⁩ ago

  Checks own servers…

  Strict-Transport-Security: max-age=63072000; includeSubDomains; preload

  Yeah, I’d like to see that…

  source

  • over_clox@lemmy.world ⁨4⁩ ⁨days⁩ ago

    web.archive.org/web/…/7667184419.html

    Anything on the archive can be accessed via simple http, regardless of whether the original site was https or not.

    source

    • elvith@feddit.org ⁨4⁩ ⁨days⁩ ago

      Yeah, but now you’re talking about communicating with web.archive.org and not nonesense.reputable-bank.com as in the original post. In this case you’re not even trying to hide the fact, that you aren’t affiliated with reputable-bank.com and were back to square one and you could also just use reputable-bank.com.some.malicious-phishing.website to host your page.

      Btw: all modern browsers will warn you when you access a non-encrypted website - some immediately, some only when you try to enter data into a login form.

      source

      • over_clox@lemmy.world ⁨4⁩ ⁨days⁩ ago

        I’m not trying to log into anything nor am I trying to get anyone’s personal information. I mostly use the archive to make it a lot easier for legacy operating systems to access and download files and software and stuff.

        You ever put Windows 3.11 or other legacy operating systems on the internet? Easier said than done, but http is basically the only way.

        source