You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Have you requested removal from other sources?
No.
Please include all relevant links to your existing removals / whitelistings. https://t.co/
Additional context
Add any other context about the problem here.
❗
Dear Team,
I am reaching out to bring your attention to a false positive warning associated with links hosted on Twitter's URL shortener, https://t.co/. As you know, https://t.co/ is an integral service provided by Twitter, a globally recognized and reputable company.
It has come to my attention that links shortened through this platform are being flagged as potentially risky or associated with phishing. This assessment is clearly inaccurate and could lead to unnecessary disruption for users and businesses relying on Twitter’s services.
While automated detection systems are valuable, they are not infallible. In this instance, I believe there has been a misjudgment in the criteria used to flag https://t.co/. Twitter has robust security measures in place to prevent misuse of its services. Thus, labeling its links as risky undermines the integrity of a widely trusted platform and creates unnecessary concern for end-users.
I kindly request a review of your assessment and the removal of the risk designation for https://t.co/ from your database. Addressing this issue will help ensure that your users receive accurate and reliable warnings without impeding legitimate usage of trusted platforms.
Thank you for your time and for considering this matter. I am happy to provide additional details if required. I look forward to your prompt resolution of this issue.
Best regards,
Send a Pull Request for faster removal
Users who understand github and creating Pull Requests can assist us with faster removals by sending a PR to mitchellkrogza/phishing repository, on the falsepositive.list file
Domains or links
Please list any domains and links listed here which you believe are a false positive.
https://t.co/
More Information
How did you discover your web site or domain was listed here?
https://www.virustotal.com/
Have you requested removal from other sources?
No.
Please include all relevant links to your existing removals / whitelistings.
https://t.co/
Additional context
Add any other context about the problem here.
❗
Dear Team,
I am reaching out to bring your attention to a false positive warning associated with links hosted on Twitter's URL shortener, https://t.co/. As you know, https://t.co/ is an integral service provided by Twitter, a globally recognized and reputable company.
It has come to my attention that links shortened through this platform are being flagged as potentially risky or associated with phishing. This assessment is clearly inaccurate and could lead to unnecessary disruption for users and businesses relying on Twitter’s services.
While automated detection systems are valuable, they are not infallible. In this instance, I believe there has been a misjudgment in the criteria used to flag https://t.co/. Twitter has robust security measures in place to prevent misuse of its services. Thus, labeling its links as risky undermines the integrity of a widely trusted platform and creates unnecessary concern for end-users.
I kindly request a review of your assessment and the removal of the risk designation for https://t.co/ from your database. Addressing this issue will help ensure that your users receive accurate and reliable warnings without impeding legitimate usage of trusted platforms.
Thank you for your time and for considering this matter. I am happy to provide additional details if required. I look forward to your prompt resolution of this issue.
Best regards,
Send a Pull Request for faster removal
Users who understand github and creating Pull Requests can assist us with faster removals by sending a PR to mitchellkrogza/phishing repository, on the falsepositive.list file
The text was updated successfully, but these errors were encountered: