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

Website security scan results for halloween-lamp.com

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

At a glance

------------------
Site scanned: halloween-lamp.com
Date of scan: April 19, 2022, 4:52 a.m.

Risk level: HIGH
SSL Status: [!!] SSL Issues found. Traffic to site is not properly encrypted. Please address the issue immediately!

Total OWASP ZAP alerts: 101
Nmap open ports found: 9

Server

------------------
IP: 163.44.185.194
Location: Japan
Web server: LiteSpeed

Open ports for halloween-lamp.com (Nmap scan)

------------------
Port 25 (tcp) - smtp
Port 80 (tcp) - http
Port 110 (tcp) - pop3
[ 6 more ]

OWASP ZAP scan results

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

Informative alerts

Low risk vulnerabilities

What does this mean?

A cookie has been set without the HttpOnly flag, which means that the cookie can be accessed by JavaScript. If a malicious script can be run on this page then the cookie will be accessible and can be transmitted to another site. If this is a session cookie then session hijacking may be possible.

Where exactly is this vulnerability found?
  1. http://halloween-lamp.com/favicon.ico
How to solve this?

Ensure that the HttpOnly flag is set for all cookies.

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. http://halloween-lamp.com/favicon.ico
How to solve this?

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

What does this mean?

The web/application server is leaking information via one or more 'X-Powered-By' HTTP response headers. Access to such information may facilitate attackers identifying other frameworks/components your web application is reliant upon and the vulnerabilities such components may be subject to.

Where exactly is this vulnerability found?
  1. http://halloween-lamp.com/cBe92u.htm
  2. http://halloween-lamp.com/vr0TLHm
  3. http://halloween-lamp.com/qrjpvVF
  4. http://halloween-lamp.com/6M7rbTY
  5. http://halloween-lamp.com/S6vbeW.htm
  6. http://halloween-lamp.com/1tSUyhY
  7. http://halloween-lamp.com/qotyvGa
  8. http://halloween-lamp.com/TmelPU.htm
  9. http://halloween-lamp.com/yBESSF.htm
  10. http://halloween-lamp.com/ES41R3f
  11. http://halloween-lamp.com/6R89NM.htm
  12. http://halloween-lamp.com/LdofhqP
  13. http://halloween-lamp.com/S8jb0A.htm
  14. http://halloween-lamp.com/AXugmq.htm
  15. http://halloween-lamp.com/dH7j9mp
  16. http://halloween-lamp.com/Sh1xLGb
  17. http://halloween-lamp.com/Srsf0Q9
  18. http://halloween-lamp.com/hZlqBo.htm
  19. http://halloween-lamp.com/93oxaR.htm
  20. http://halloween-lamp.com/7TXjS35
How to solve this?

Ensure that your web server, application server, load balancer, etc. is configured to suppress 'X-Powered-By' headers.

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. http://halloween-lamp.com/S6vbeW.htm
  2. http://halloween-lamp.com/cBe92u.htm
  3. http://halloween-lamp.com/sitemap.xml
  4. http://halloween-lamp.com/ifZzjx.htm
  5. http://halloween-lamp.com/hZlqBo.htm
  6. http://halloween-lamp.com/S8jb0A.htm
  7. http://halloween-lamp.com/6R89NM.htm
  8. http://halloween-lamp.com/93oxaR.htm
  9. http://halloween-lamp.com/xFizEl.htm
  10. http://halloween-lamp.com/igavd4.htm
  11. http://halloween-lamp.com/TmelPU.htm
  12. http://halloween-lamp.com/pODiJn.htm
  13. http://halloween-lamp.com/aikNXE.htm
  14. http://halloween-lamp.com/tGxjfH.htm
  15. http://halloween-lamp.com/8Tbuew.htm
  16. http://halloween-lamp.com/vrd4lj.htm
  17. http://halloween-lamp.com/nxmDdP.htm
  18. http://halloween-lamp.com/qpJkfZ.htm
  19. http://halloween-lamp.com/tXg7xO.htm
  20. http://halloween-lamp.com/3yck6e.htm
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

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

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

Technology

PHP (7.4.29)

Other

Open-Graph-Protocol (article)
Script
UncommonHeaders (x-powered-cms,x-robots-tag,x-turbo-charged-by)
MetaGenerator (['AntiBot.Cloud v. 5.07'])
HTML5
Cookies (ab_referer)
X-Powered-By (PHP/7.4.29)
[ 3 more ]
See hacks, ports, leaked data and possible attack routes for halloween-lamp.com

Idyllum Labs is on a mission

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

Is the code hosted at halloween-lamp.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 halloween-lamp.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.