["http://navasat.com",200,[["Country",[{"string":"SPAIN","module":"ES","certainty":100}]],["Title",[{"name":"page title","string":"navasat.com","certainty":100}]],["HTTPServer",[{"name":"server string","string":"Apache","certainty":100}]],["HTML5",[{"regexp":["<!DOCTYPE HTML>"],"regexp_compiled":"(?i-mx:<!DOCTYPE html>)","certainty":100}]],["IP",[{"string":"217.76.128.47","certainty":100}]],["Apache",[{"regexp":["Apache"],"search":"headers[server]","name":"HTTP Server Header","regexp_compiled":"(?i-mx:^Apache)","certainty":100}]],["UncommonHeaders",[{"name":"headers","string":"x-serverindex,upgrade","certainty":100}]],["Script",[{"regexp":[" ",">"],"regexp_compiled":"(?i-mx:<script(\\s|>))","certainty":100},{"string":["text/javascript"],"offset":1,"regexp_compiled":"(?-mix:<script[^>]+(language|type)\\s*=\\s*['\"]?([^'\"\\s]+)['\"]?)","certainty":100}]]]]
X-Frame-Options header is not included in the HTTP response to protect against 'ClickJacking' attacks.
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).
A timestamp was disclosed by the application/web server - Unix
Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.
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.
This check identifies responses where the HTTP Content-Type header declares a charset different from the charset defined by the body of the HTML or XML. When there's a charset mismatch between the HTTP header and content body Web browsers can be forced into an undesirable content-sniffing mode to determine the content's correct character set.An attacker could manipulate content on the page to be interpreted in an encoding of their choice. For example, if an attacker can control content at the beginning of the page, they could inject script using UTF-7 encoded text and manipulate some browsers into interpreting that text.
Force UTF-8 for all text content in both the HTTP header and meta tags in HTML or encoding declarations in XML.
A WSDL File has been detected.
Make your WSDL files visible only for technical issues (ex: testing purposes).
A | ||||
A | www.elixir.ee | 3600 | 217.146.69.20 | |
AAAA | ||||
Sorry, no records found | ||||
CNAME | ||||
CNAME | www.elixir.ee | 3600 | elixir.ee | |
MX | ||||
MX | www.elixir.ee | 3600 | 5 | ALT2.ASPMX.L.GOOGLE.COM. |
MX | www.elixir.ee | 3600 | 10 | ALT3.ASPMX.L.GOOGLE.COM. |
MX | www.elixir.ee | 3600 | 10 | ALT4.ASPMX.L.GOOGLE.COM. |
MX | www.elixir.ee | 3600 | 1 | ALTMX.ASPMX.L.GOOGLE.COM. |
NS Records | ||||
NS | elixir.ee | 3600 | ns2.zone.ee. (85.234.242.32) | |
NS | elixir.ee | 3600 | ns.zone.eu. (217.146.66.65) | |
NS | elixir.ee | 3600 | ns3.zonedata.net. (90.191.225.242) | |
TXT | ||||
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 navasat.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 navasat.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!