Website security scan results for r2mministries.com
At a glance
SSL Status: [!!] SSL Issues found. Traffic to site is not properly encrypted. Please address the issue immediately!
Location: United States (['66.96.162.142'])
Total OWASP ZAP alerts: 9
Nmap open ports found: 11
Network
Owner email: awsdns-hostmaster@amazon.comNameservers:
ns1.domain.com(66.96.142.147) - Primary NS: g-ns-956.awsdns-60.co.uk
ns2.domain.com(65.254.254.171) - Primary NS: g-ns-956.awsdns-60.co.uk
["http://r2mministries.com",200,[["Country",[{"string":"UNITED STATES","module":"US","certainty":100}]],["Title",[{"name":"page title","string":"This site is under development","certainty":100}]],["HTTPServer",[{"name":"server string","string":"Apache/2","certainty":100}]],["Frame",[{"regexp":["<iframe "],"regexp_compiled":"(?i-mx:<i?frame\\s+)","certainty":100}]],["HTML5",[{"regexp":["<!DOCTYPE HTML>"],"regexp_compiled":"(?i-mx:<!DOCTYPE html>)","certainty":100}]],["IP",[{"string":"66.96.162.142","certainty":100}]],["Apache",[{"regexp":["Apache"],"search":"headers[server]","name":"HTTP Server Header","regexp_compiled":"(?i-mx:^Apache)","certainty":100},{"version":["2"],"search":"headers[server]","name":"HTTP Server Header","regexp_compiled":"(?i-mx:^Apache\\/([\\d\\.]+))","certainty":100}]],["Script",[{"regexp":[" "],"regexp_compiled":"(?i-mx:<script(\\s|>))","certainty":100},{"string":["JavaScript"],"offset":1,"regexp_compiled":"(?-mix:<script[^>]+(language|type)\\s*=\\s*['\"]?([^'\"\\s]+)['\"]?)","certainty":100}]],["JQuery",[{"regexp":["<script src=\"//ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery"],"regexp_compiled":"(?-mix:<script [^>]*jquery)","certainty":100},{"version":["1.10.2"],"offset":0,"regexp_compiled":"(?-mix:jquery\\/([0-9\\.]+)\\/jquery(\\.min)?\\.js)","certainty":100}]]]]
Title
This site is under developmentEnvironment info
IP addresses: 66.96.162.142Location: United States
Web server: Apache/2 2
Technology
JQuery (1.10.2)
All keywords
Country (UNITED STATES)
Frame
HTML5
HTTPServer (Apache/2)
IP (66.96.162.142)
JQuery
Script
Title (This site is under development)
OWASP ZAP Vulnerability Scan for r2mministries.com
Results from May 27, 2023, 4:12 a.m.High risk vulnerabilities
Medium risk vulnerabilities
Content Security Policy (CSP) is an added layer of security that helps to detect and mitigate certain types of attacks, including Cross Site Scripting (XSS) and data injection attacks. These attacks are used for everything from data theft to site defacement or distribution of malware. CSP provides a set of standard HTTP headers that allow website owners to declare approved sources of content that browsers should be allowed to load on that page — covered types are JavaScript, CSS, HTML frames, fonts, images and embeddable objects such as Java applets, ActiveX, audio and video files.
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.
Low risk vulnerabilities
The page includes one or more script files from a third-party domain.
Ensure JavaScript source files are loaded from only trusted sources, and the sources can't be controlled by end users of the application.
The web/application server is leaking version information via the "Server" HTTP response header. Access to such information may facilitate attackers identifying other vulnerabilities your web/application server is subject to.
Ensure that your web server, application server, load balancer, etc. is configured to suppress the "Server" header or provide generic details.
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.
Informative alerts
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.
The content was retrieved from a shared cache. If the response data is sensitive, personal or user-specific, this may result in sensitive information being leaked. In some cases, this may even result in a user gaining complete control of the session of another user, depending on the configuration of the caching components in use in their environment. This is primarily an issue where caching servers such as "proxy" caches are configured on the local network. This configuration is typically found in corporate or educational environments, for instance.
Validate that the response does not contain sensitive, personal or user-specific information. If it does, consider the use of the following HTTP response headers, to limit, or prevent the content being stored and retrieved from the cache by another user:
Cache-Control: no-cache, no-store, must-revalidate, private
Pragma: no-cache
Expires: 0
This configuration directs both HTTP 1.0 and HTTP 1.1 compliant caching servers to not store the response, and to not retrieve the response (without validation) from the cache, in response to a similar request.
Open ports for r2mministries.com (Nmap scan)
Results from Sept. 11, 2021, 6:11 a.m.Port 25 (tcp)(open) - smtp
Port 80 (tcp)(open) - http
Port 110 (tcp)(open) - pop3
Port 143 (tcp)(open) - imap
Port 443 (tcp)(open) - https
Port 465 (tcp)(open) - smtps
Port 587 (tcp)(open) - submission
Port 993 (tcp)(open) - imaps
Port 995 (tcp)(open) - pop3s
Port 2222 (tcp)(open) - EtherNetIP-1
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
What next?
------------------Dig deeper
- Log in or create a free account to gain access to this report in its entirety.
- Use our dashboard to automate security testing and set up automatic monitoring for your website portfolio.
- Scan a new domain or initiate a rescan for this domain.
Join our ranks
- Use these insights to build your systems bullet-proof.
- Explore our datasets and compare your results.
- Drop us a line! Help us expand our code or cloud or just say hi!
- Support the cause - your donation helps to keep this service free and unbiased.
Idyllum Labs is on a mission
------------------Is the code hosted at r2mministries.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.
Please note
This is an automated and unbiased website vulnerability scan for the domain r2mministries.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!