mitchellkrogza
jotform.com (whitelist)
Pull Request: Whitelisting of .jotform.com
This pull request aims to whitelist the domain .jotform.com as part of our ongoing efforts to enhance the integrity of our phishing database.
Related Issue: Phishing.Database Issue #1091
Current Status: This PR is currently on hold as I am engaging with the administrators of jotform.com to encourage adherence to the relevant RFC standards concerning HTTP server responses.
Technical Context
In accordance with RFC 7231, which outlines the semantics and content of HTTP/1.1, it is crucial for web servers to return appropriate HTTP status codes that accurately reflect the outcome of the request. For instance, the use of standard response codes such as 200 OK, 404 Not Found, and 500 Internal Server Error is essential for proper client-server communication and for ensuring that automated systems can effectively interpret server responses.
The current HTTP response behavior of jotform.com does not fully comply with these standards, which may lead to misinterpretations by clients and could potentially compromise the security measures we are implementing.
I am advocating for the following actions from the jotform.com team:
-
Review and Update HTTP Response Codes: Ensure that all server responses align with the expected codes as defined in RFC 7231 and other relevant RFCs, such as RFC 2616 for HTTP/1.1.
-
Implement Consistent Error Handling: Establish a consistent approach to error handling that provides clear and actionable feedback to clients, thereby improving the overall user experience and security posture.
By adhering to these standards, jotform.com can enhance its interoperability with various clients and services, ultimately contributing to a more secure and reliable web environment.
I will keep this PR on hold until we can achieve a satisfactory resolution with the jotform.com team regarding their HTTP response compliance. Thank you for your understanding and support in this matter.
ATT: @cigdemtosun
@alphanet31 please report false positives here one by one https://github.com/Phishing-Database/Phishing.Database/issues
The website is still uses 200 code for everything.
Thanks a lot for your followup, I just noticed, come to think... is this in reality yet another problem by using Cloudflare as server manager and network controllers of a domain?
Why on earth should anyone, by their free will, wants to reply a http 404 with http 200?? that don't make any seance to me.
@spirillen I've tested my small website, which uses Cloudflare as reverse proxy - everything is ok. Of course, my static website, hosted on Cloudflare pages, has other codes - but I guess I can fix it too.
Details
@spirillen I've tested my small website, which uses Cloudflare.
Oh, why did you have to ruin my fondness for you? 😭 😭 😭 😭 😭 Was that intentional?
- https://kb.mypdns.org/articles/MPDNS-A-4/CloudFlare – that’s a twist in your life that you really need to sort out quickly.
- https://kb.mypdns.org/articles/MPDNS-A-2/Fundamental-human-rights
You do realise that CrimeFlare and
with a soft spot for cybersecurity
are heading in completely different directions, don’t you?
Man, privacy != security :) There are some websites, that can be hosted at Cloudflare - let it be.
Also can't access your links @spirillen :
Details
Also can't access your links
Of course not, I do not support spyware... Try a Fox ESR and you will pass with flying color...
map $http_user_agent $blocked_agent {
default 0;
# Browsers Allowed
~*Chrome 1; # Google Chrome
~*Deno 0;
~*Mastodon 0;
~*MisskeyMediaProxy 0; # Misskey Media Proxy
~*Mozilla 0;
~*Takahe 0;
~*TorBrowser 0; # Tor Browser
...
# Block command-line tools
~*curl 0; # cURL
~*wget 0; # Wget
~*lynx 0; # Lynx
}
Closing.
Domain(s) or IP(s) not found in issue message or title.
-- We appreciate your help in refining this. Please let us know if anything seems incorrect.
Closing.
Domain(s) or IP(s) not found in issue message or title.
-- We appreciate your help in refining this. Please let us know if anything seems incorrect.
What???
Closing.
Domain(s) or IP(s) not found in issue message or title.
-- We appreciate your help in refining this. Please let us know if anything seems incorrect.
@funilrys @phishing-database-bot This script do not seems to work properly... I stop checking closed issues by this script and leaves it to you, to revisit ALL closed issues by @phishing-database-bot as most of them seems to be closed on false grounds.
phishing_database/ALL-phishing-links.csv:jotform.com
phishing_database/ALL-phishing-links.csv:app.jotform.com
phishing_database/ALL-phishing-links.csv:form.jotform.com
phishing_database/ALL-phishing-links.csv:www.jotform.com
phishing_database/phishing.database/domain.csv:app.jotform.com
phishing_database/phishing.database/domain.csv:form.jotform.com
phishing_database/phishing.database/domain.csv:jotform.com
Closing.
Domain(s) or IP(s) not found in issue message or title.
-- We appreciate your help in refining this. Please let us know if anything seems incorrect.
Closing.
Domain(s) or IP(s) not found in the Phishing.Database project: tools.ietf.org, jotform.com.
-- We appreciate your help in refining this. Please let us know if anything seems incorrect.