// See cached web security scan results for microsoft.com.
// Run OWASP ZAP, NMAP, WhatWeb, TLS scans on microsoft.com
whatweb: "Adobe-Flash" server:"Apache" https:"no"
// Discover sites running Adobe Flash on Apache with a faulty SSL configuration
// Search for sites with open ports 20 OR 21 AND 8008
whatweb: "Bootstrap" country:"CA" tld:".com" zap:"10202"
// Look for Canadian sites built with Bootstrap in the .com domain with absent Anti-CSRF tokens
// Look for sites with (unsafe inline scripts OR styles) AND Loosely Scoped Cookies. (Accepts ZAP alert IDs)
Ensure that your web server, application server, load balancer, etc. is configured to set the Content-Security-Policy header.
The response does not include either Content-Security-Policy with 'frame-ancestors' directive or X-Frame-Options to protect against 'ClickJacking' attacks.
Modern Web browsers support the Content-Security-Policy and X-Frame-Options HTTP headers. Ensure one of them is set on all web pages returned by your site/app.
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. Alternatively consider implementing Content Security Policy's "frame-ancestors" directive.
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.
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.
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.
Remove all comments that return information that may help an attacker and fix any underlying problems they refer to.
The application appears to be a modern web application. If you need to explore it automatically then the Ajax Spider may well be more effective than the standard one.
This is an informational alert and so no changes are required.
|Sorry, no records found|
|TXT||elixir.ee||3600||v=spf1 a mx include:_spf.zone.eu include:_spf.google.com ~all|
This report was generated with the Idyllum Labs Website security tool.
Get your report www.idyllum.com
Is the code hosted at www.99dzx.com vulnerable to cybersecurity attacks? Are the used systems up to date and respecting the security standards of 2023?
We at Idyllum Labs wanted to find out! That is why we built this automated website security scanner and generated this report.
This is an automated and unbiased website vulnerability scan for the domain www.99dzx.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!