Legit Site (EquiFax) - Gets BLOCKED?

vpnavy
edited September 2017 in Protection


Equifax breach exposes 143 million people to identity theft so they provided a site to see if you were one of the lucky ones.  Whenever I try to go to it - BitDefender jumps in and says NO NO NO and hit to back out safely, etc.   The URL: http://www.equifaxsecurity2017.com/  Really confused - is this a mistake?


 

Comments


  • If you sign up for their protection through TrustID you waive your right to join any lawsuit against Equifax, Just as a heads up.


  • Thanks Niksal12 - I just read (mind you - I didn't because BitDefender flag's the site as bad) from another site that is getting to the URL without a problem...


    "...In response to consumer inquiries, we have made it clear that the arbitration clause and class action waiver included in the Equifax and TrustedID Premier terms of use does not apply to this cybersecurity incident.."


  • Well the URL should be https://..... but Bitdefender still blocks the top level page. Interestingly sub pages work eg google the site name and look at the Bitdefender icons.


    False positive?


  • Yea - I tried both http: and https: with the same results.   I found the URL on all the local newspapers, etc. - can't imagine it would already be hacked.  It is probably a "false positive" but until BitDefender says it is ok - I will continue to be a chicken!  :)


  • Well Bitdefender appears to be the only AV that detects it as bad.


    Results from VirusTotal: https://www.virustotal.com/#/url/310e17fee782fbf677a575cfa991796eb2e1a189f892a842524e09944be64c33/detection


    All clean, although no result listed for Kaspersky or Sophos (Sophos on my Android phone thought the URL was ok).


     


    The Tech media are giving Equifax a pretty hard time this weekend. I'm going to hold off for a bit before using this site. While it is the correct site, according to the news reports it appears some of the implementation may be lacking.


  • Hello,


     


    We apologize for the inconvenience.


    The FP was corrected.

This discussion has been closed.