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

Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Tìm hiểu thêm
Đang mở

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.

jbr đã trả lời
siamjo

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 !!!!!!!!
Đính kèm ảnh chụp màn hình

Tất cả các câu trả lời (6)

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 ?

If other browsers allowed you to access the site during the same timeframe this error was produced (before Yahoo/AOL fixed their booboo earlier today), it's a security bug that you should report to their authors.

Đặt một câu hỏi

Bạn phải đăng nhập vào tài khoản của bạn để trả lời bài viết. Vui lòng bắt đầu một câu hỏi mới, nếu bạn chưa có tài khoản.