["http://truge.com",200,[["Country",[{"string":"UNITED STATES","module":"US","certainty":100}]],["nginx",[{"search":"headers[server]","regexp":["nginx"],"regexp_compiled":"(?-mix:^nginx$)","certainty":100}]],["HTTPServer",[{"name":"server string","string":"nginx","certainty":100}]],["IP",[{"string":"52.128.23.153","certainty":100}]],["UncommonHeaders",[{"name":"headers","string":"x-dis-request-id","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}]]]]
None
None
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.
Ensure that the HttpOnly flag is set for all cookies.
None
None
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.
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 truge.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 truge.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!