["http://selmanokur.com",200,[["Bootstrap",[{"regexp":["<link href=\"/css/bootstrap"],"regexp_compiled":"(?-mix:<link [^>]*bootstrap)","certainty":100}]],["Country",[{"string":"TURKEY","module":"TR","certainty":100}]],["Title",[{"name":"page title","string":"selmanokur.com Alan adının süresi sona ermiştir","certainty":100}]],["nginx",[{"search":"headers[server]","version":["1.14.1"],"regexp_compiled":"(?-mix:^nginx\\/([^\\s]+).*$)","certainty":100}]],["HTTPServer",[{"name":"server string","string":"nginx/1.14.1","certainty":100}]],["IP",[{"string":"85.159.66.62","certainty":100}]],["UncommonHeaders",[{"name":"headers","string":"x-rate-limit-limit,x-rate-limit-remaining,x-rate-limit-reset","certainty":100}]]]]
This page contains an error/warning message that may disclose sensitive information like the location of the file that produced the unhandled exception. This information can be used to launch further attacks against the web application. The alert could be a false positive if the error message is found inside a documentation page.
Review the source code of this page. Implement custom error pages. Consider implementing a mechanism to provide a unique error reference/identifier to the client (browser) while logging the details on the server side and not exposing them to the user.
The response appeared to contain common error messages returned by platforms such as ASP.NET, and Web-servers such as IIS and Apache. You can configure the list of common debug messages.
Disable debugging messages before pushing to production.
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.
Ensure that your web server, application server, load balancer, etc. is configured to suppress 'X-Powered-By' headers.
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 selmanokur.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 selmanokur.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!