Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Be careful. Something doesn’t look right. Firefox spotted a potentially serious security issue with www.aol.fr. Someone pretending to be the site could try to steal things like credit card info, passwords, or emails.

  • 5
  • 0
  • Nzaghachi ikpeazụ nke siamjo
  • Open

Be careful. Something doesn’t look right.

Firefox spotted a potentially serious security issue with www.aol.fr. Someone pretending to be the site could try to steal things like credit card info, passwords, or emails. ??????? I used Aol since 1998 !!!!!!!!

Be careful. Something doesn’t look right. Firefox spotted a potentially serious security issue with www.aol.fr. Someone pretending to be the site could try to steal things like credit card info, passwords, or emails. ??????? I used Aol since 1998 !!!!!!!!
Nseta ihuenyo ndị agbakwunyere

All Replies (5)

Hi.

Often this is a domain security outdated, but just tried your link and it goes to Yahoo in French.

I note the link is http://www.aol.fr/ so no security.

So if you trust Yahoo . . . . I don't

Basically the "Advanced" details tell you what's the issue.

In this case the site was badly configured, and the certificate forgot to include this redirect as well.

From what I can tell it appears the site operators fixed this issue today (or serve different results over time based on load balancing?) as www.aol.fr (13.248.158.7) on Mon, 11 May 2026 10:55:09 UTC failed trust checks, whereas the same www.aol.fr (13.248.158.7) on Mon, 11 May 2026 11:54:07 UTC passed A+ — the change is the certificate served a) now matches, b) is issued today fresh.

My guess is they mistakenly provisioned a "yahoo.*" certificate instead of a "aol.*" one, based on before/after:

(so yes, somebody was really pretending to be something else, and the error page was spot on…)

no such problem on Edge or Chrome !!! Firefox sucks ?

Jụọ ajụjụ

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.