Is fatconspiracy.com secure and safe to use? | Web Security Optimization (WSO) report by Idyllum Labs.

Website security scan results for fatconspiracy.com

Safe mode. Please [ log in ] to see the full report!

At a glance

------------------
Site scanned: fatconspiracy.com
Date of scan: July 6, 2022, 2:01 p.m.

Risk level: LOW
SSL Status: [OK] SSL Encryption enforced

Total OWASP ZAP alerts: 17
Nmap open ports found: 2

Server

------------------
IP: 199.59.243.220
Location: United States
Web server: openresty

Open ports for fatconspiracy.com (Nmap scan)

------------------
Port 80 (tcp) - http
Port 443 (tcp) - https

OWASP ZAP scan results

------------------

Informative alerts

What does this mean?

The response appears to contain suspicious comments which may help an attacker. Note: Matches made within script blocks or files are against the entire content not only comments.

Where exactly is this vulnerability found?
  1. https://fatconspiracy.com/js/parking.2.91.3.js?id=962daae0d167c4d3652b
  2. https://fatconspiracy.com/js/parking.2.91.3.js
How to solve this?

Remove all comments that return information that may help an attacker and fix any underlying problems they refer to.

Low risk vulnerabilities

What does this mean?

A cookie has been set without the SameSite attribute, which means that the cookie can be sent as a result of a 'cross-site' request. The SameSite attribute is an effective counter measure to cross-site request forgery, cross-site script inclusion, and timing attacks.

Where exactly is this vulnerability found?
  1. https://fatconspiracy.com/sitemap.xml
  2. https://fatconspiracy.com/_zc
  3. https://fatconspiracy.com/robots.txt
  4. https://fatconspiracy.com/
How to solve this?

Ensure that the SameSite attribute is set to either 'lax' or ideally 'strict' for all cookies.

What does this mean?

A cookie has been set without the secure flag, which means that the cookie can be accessed via unencrypted connections.

Where exactly is this vulnerability found?
  1. https://fatconspiracy.com/_zc
  2. https://fatconspiracy.com/robots.txt
  3. https://fatconspiracy.com/sitemap.xml
  4. https://fatconspiracy.com/
How to solve this?

Whenever a cookie contains sensitive information or is a session token, then it should always be passed using an encrypted channel. Ensure that the secure flag is set for cookies containing such sensitive information.

What does this mean?

The Anti-MIME-Sniffing header X-Content-Type-Options was not set to 'nosniff'. This allows older versions of Internet Explorer and Chrome to perform MIME-sniffing on the response body, potentially causing the response body to be interpreted and displayed as a content type other than the declared content type. Current (early 2014) and legacy versions of Firefox will use the declared content type (if one is set), rather than performing MIME-sniffing.

Where exactly is this vulnerability found?
  1. https://fatconspiracy.com/js/parking.2.91.3.js
  2. https://fatconspiracy.com/robots.txt
  3. https://fatconspiracy.com/
  4. https://fatconspiracy.com/_zc
  5. https://fatconspiracy.com/sitemap.xml
  6. https://fatconspiracy.com/js/parking.2.91.3.js?id=962daae0d167c4d3652b
How to solve this?

Ensure that the application/web server sets the Content-Type header appropriately, and that it sets the X-Content-Type-Options header to 'nosniff' for all web pages.If possible, ensure that the end user uses a standards-compliant and modern web browser that does not perform MIME-sniffing at all, or that can be directed by the web application/web server to not perform MIME-sniffing.

Medium risk vulnerabilities

What does this mean?

X-Frame-Options header is not included in the HTTP response to protect against 'ClickJacking' attacks.

Where exactly is this vulnerability found?
  1. https://fatconspiracy.com/_zc
  2. https://fatconspiracy.com/
  3. https://fatconspiracy.com/sitemap.xml
How to solve this?

Most modern Web browsers support the X-Frame-Options HTTP header. Ensure it's set on all web pages returned by your site (if you expect the page to be framed only by pages on your server (e.g. it's part of a FRAMESET) then you'll want to use SAMEORIGIN, otherwise if you never expect the page to be framed, you should use DENY. ALLOW-FROM allows specific websites to frame the web page in supported web browsers).

High risk vulnerabilities

Manual inspection results

This site has not been manually inspected yet. Please apply for an inspection here

Find this WSO report online:

Environment info

------------------

Other

Script
UncommonHeaders (x-adblock-key)
HTML5
Cookies (parking_session)
HttpOnly ([['parking_session']])
See hacks, ports, leaked data and possible attack routes for fatconspiracy.com

Idyllum Labs is on a mission

------------------

Is the code hosted at fatconspiracy.com vulnerable to cybersecurity attacks? Are the used systems up to date and respecting the security standards of 2022?

We at Idyllum Labs wanted to find out! That is why we built this automated website security scanner and generated this report.

Please note

This is an automated and unbiased website vulnerability scan for the domain fatconspiracy.com and has nothing to do with human subjectivity, thoughts, opinions, or relationships.

Our cloud-based infrastructure crawls the internet using a mixture of OWASP ZAP, Nmap, Whatweb, and other great software to detect website security issues. We display this data for educational purposes - to give security guidelines for anyone interested in building a safer web environment.

If you have comments, don't agree with the results, or want to submit a site for manual examination, don't hesitate to contact us.


Run a free OWASP ZAP scan for any website at Idyllum.com!

What next?

------------------

Dig deeper

  1. Log in or create a free account to gain access to this report in its entirety.
  2. Use our dashboard to automate security testing and set up automatic monitoring for your website portfolio.
  3. Scan a new domain or initiate a rescan for this domain.

Join our ranks

  1. Use these insights to build your systems bullet-proof.
  2. Explore our datasets and compare your results.
  3. Drop us a line! Help us expand our code or cloud or just say hi!
  4. Support the cause - your donation helps to keep this service free and unbiased.