Vulnerability Scan Result
| Title: | Environmental Health & Safety Consulting Services | MechSafety |
| Description: | Environmental health and safety consultant services tailored to your needs. Ensure compliance and safety. Contact us today! |
| ip_address | 104.21.59.238 |
| country | - |
| network_name | Cloudflare Inc |
| asn | AS13335 |
| ip_address | 172.67.185.112 |
| country | - |
| network_name | Cloudflare Inc |
| asn | AS13335 |
80/tcp | http | Cloudflare http proxy - |
443/tcp | https | cloudflare - |
2082/tcp | http | Cloudflare http proxy - |
2083/tcp | https | nginx - |
2086/tcp | http | Cloudflare http proxy - |
2087/tcp | https | nginx - |
8080/tcp | http | Cloudflare http proxy - |
8443/tcp | http | cloudflare - |
| Software / Version | Category |
|---|---|
| Clipboard.js | JavaScript libraries |
| Elementor 3.27.5 | Page builders, WordPress plugins |
| Hello Elementor 3.1.0 | WordPress themes |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| core-js 3.39.0 | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| Google Font API | Font scripts |
| HTTP/3 | Miscellaneous |
| imagesLoaded 5.0.0 | JavaScript libraries |
| jQuery 3.7.1 | JavaScript libraries |
| jQuery UI 1.13.3 | JavaScript libraries |
| MySQL | Databases |
| Open Graph | Miscellaneous |
| PHP | Programming languages |
| RankMath SEO | WordPress plugins, SEO |
| Twitter Emoji (Twemoji) | Font scripts |
| Priority Hints | Performance |
| WordPress 6.8.3 | CMS, Blogs |
| Cloudflare | CDN |
| Google Tag Manager | Tag managers |
| Lodash 1.13.7 | JavaScript libraries |
| RSS | Miscellaneous |
Web Application Vulnerabilities
Evidence
| URL | Evidence |
|---|---|
| https://mechsafety.com/ | Response headers do not include the HTTP Strict-Transport-Security header |
Vulnerability description
We noticed that the target application lacks the HTTP Strict-Transport-Security header in its responses. This security header is crucial as it instructs browsers to only establish secure (HTTPS) connections with the web server and reject any HTTP connections.
Risk description
The risk is that lack of this header permits an attacker to force a victim user to initiate a clear-text HTTP connection to the server, thus opening the possibility to eavesdrop on the network traffic and extract sensitive information (e.g. session cookies).
Recommendation
The Strict-Transport-Security HTTP header should be sent with each HTTPS response. The syntax is as follows: `Strict-Transport-Security: max-age=<seconds>[; includeSubDomains]` The parameter `max-age` gives the time frame for requirement of HTTPS in seconds and should be chosen quite high, e.g. several months. A value below 7776000 is considered as too low by this scanner check. The flag `includeSubDomains` defines that the policy applies also for sub domains of the sender of the response.
Classification
| CWE | CWE-693 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
Vulnerability description
We found the robots.txt on the target server. This file instructs web crawlers what URLs and endpoints of the web application they can visit and crawl. Website administrators often misuse this file while attempting to hide some web pages from the users.
Risk description
There is no particular security risk in having a robots.txt file. However, it's important to note that adding endpoints in it should not be considered a security measure, as this file can be directly accessed and read by anyone.
Recommendation
We recommend you to manually review the entries from robots.txt and remove the ones which lead to sensitive locations in the website (ex. administration panels, configuration files, etc).
Evidence
| Software / Version | Category |
|---|---|
| Clipboard.js | JavaScript libraries |
| Elementor 3.27.5 | Page builders, WordPress plugins |
| Hello Elementor 3.1.0 | WordPress themes |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| core-js 3.39.0 | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| Google Font API | Font scripts |
| HTTP/3 | Miscellaneous |
| imagesLoaded 5.0.0 | JavaScript libraries |
| jQuery 3.7.1 | JavaScript libraries |
| jQuery UI 1.13.3 | JavaScript libraries |
| MySQL | Databases |
| Open Graph | Miscellaneous |
| PHP | Programming languages |
| RankMath SEO | WordPress plugins, SEO |
| Twitter Emoji (Twemoji) | Font scripts |
| Priority Hints | Performance |
| WordPress 6.8.3 | CMS, Blogs |
| Cloudflare | CDN |
| Google Tag Manager | Tag managers |
| Lodash 1.13.7 | JavaScript libraries |
| RSS | Miscellaneous |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.
Evidence
| URL | Evidence |
|---|---|
| https://mechsafety.com/ | Response headers do not include the Referrer-Policy HTTP security header as well as the |
Vulnerability description
We noticed that the target application's server responses lack the Referrer-Policy HTTP header, which controls how much referrer information the browser will send with each request originated from the current web application.
Risk description
The risk is that if a user visits a web page (e.g. "http://example.com/pricing/") and clicks on a link from that page going to e.g. "https://www.google.com", the browser will send to Google the full originating URL in the `Referer` header, assuming the Referrer-Policy header is not set. The originating URL could be considered sensitive information and it could be used for user tracking.
Recommendation
The Referrer-Policy header should be configured on the server side to avoid user tracking and inadvertent information leakage. The value `no-referrer` of this header instructs the browser to omit the Referer header entirely.
Classification
| CWE | CWE-693 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://mechsafety.com/ | Response headers do not include the X-Content-Type-Options HTTP security header |
Vulnerability description
We noticed that the target application's server responses lack the X-Content-Type-Options header. This header is particularly important for preventing Internet Explorer from reinterpreting the content of a web page (MIME-sniffing) and thus overriding the value of the Content-Type header.
Risk description
The risk is that lack of this header could make possible attacks such as Cross-Site Scripting or phishing in Internet Explorer browsers.
Recommendation
We recommend setting the X-Content-Type-Options header such as `X-Content-Type-Options: nosniff`.
Classification
| CWE | CWE-693 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://mechsafety.com/ | Response does not include the HTTP Content-Security-Policy security header or meta tag |
Vulnerability description
We noticed that the target application lacks the Content-Security-Policy (CSP) header in its HTTP responses. The CSP header is a security measure that instructs web browsers to enforce specific security rules, effectively preventing the exploitation of Cross-Site Scripting (XSS) vulnerabilities.
Risk description
The risk is that if the target application is vulnerable to XSS, lack of this header makes it easily exploitable by attackers.
Recommendation
Configure the Content-Security-Header to be sent with each HTTP response in order to apply the specific policies needed by the application.
Classification
| CWE | CWE-693 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://mechsafety.com/wp-json/wp/v2 | GET | Headers: User-Agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36 | Possible API endpoint found at |
Vulnerability description
We found API endpoints while crawling the given web application.
Risk description
These endpoints may represent an attack surface for malicious actors interested in API-specific vulnerabilities.
Recommendation
Use the API Scanner to perform a more thorough vulnerability check for these endpoints, if an API specification is present.
Vulnerability description
We have noticed that the server is missing the security.txt file, which is considered a good practice for web security. It provides a standardized way for security researchers and the public to report security vulnerabilities or concerns by outlining the preferred method of contact and reporting procedures.
Risk description
There is no particular risk in not having a security.txt file for your server. However, this file is important because it offers a designated channel for reporting vulnerabilities and security issues.
Recommendation
We recommend you to implement the security.txt file according to the standard, in order to allow researchers or users report any security issues they find, improving the defensive mechanisms of your server.
Evidence
Vulnerability description
Website is accessible.
Infrastructure Vulnerabilities
Evidence
We found insecure DNS cookie usage on the following nameservers: liberty.ns.cloudflare.com, rayden.ns.cloudflare.com
Vulnerability description
We found that the server does not implement DNS Cookies or uses them insecurely. DNS Cookies help prevent DNS-based attacks, such as spoofing and amplification attacks.
Risk description
The risk exists because without DNS Cookies, the server is vulnerable to DNS spoofing and amplification attacks. Attackers can manipulate responses or use the server in distributed denial-of-service (DDoS) attacks, compromising network availability and security.
Recommendation
We recommend enabling DNS Cookies to prevent spoofed DNS responses. Ensure proper cookie validation is implemented to mitigate DNS amplification attacks. Regularly update DNS servers to support the latest DNS security features.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| mechsafety.com | SPF | Sender Policy Framework | "v=spf1 ip4:192.185.4.23 a mx include:websitewelcome.com ~all" |
Vulnerability description
We found that the Sender Policy Framework (SPF) record for the domain is configured with ~all (soft fail), which indicates that emails from unauthorized IP addresses are not explicitly denied. Instead, the recipient mail server is instructed to treat these messages with suspicion but may still accept them. This configuration may not provide enough protection against email spoofing and unauthorized email delivery, leaving the domain more vulnerable to impersonation attempts.
Risk description
The ~all directive in an SPF record allows unauthorized emails to pass through some email servers, even though they fail SPF verification. While such emails may be marked as suspicious or placed into a spam folder, not all mail servers handle soft fail conditions consistently. This creates a risk that malicious actors can spoof the domain to send phishing emails or other fraudulent communications, potentially causing damage to the organization's reputation and leading to successful social engineering attacks.
Recommendation
We recommend changing the SPF record's ~all (soft fail) directive to -all (hard fail). The -all setting tells recipient mail servers to reject emails from any IP addresses not listed in the SPF record, providing stronger protection against email spoofing. Ensure that all legitimate IP addresses and services that send emails on behalf of your domain are properly included in the SPF record before implementing this change.
Evidence
| DKIM selector | Key type | Key size | Value |
|---|---|---|---|
| default | rsa | 1422 | "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEArbyxH/hfTwqQADBIuF+3dhdZgjU8uzU0rql7X5hebOYn9DCkxujcFcd2Kuktr7UNBzsUof+x4OGgQUEEFs1U0Ua5EaPvwmL8iY37XoArqQF8jRXczx0zw7tRYCKKL1JHDY3XCz7IPi25ZMDBScgp42gqq+kvOABUZF9HIvXYNoNIRNZwDV0D7kKuGphRoXjtz" "yB/+aCKQ5oBOoeXXh/zbrngfmH/4nmACZxlB8kIArq+YNpjZVylSaKncIIbtUag49gg/cgBaGgEatkRjtewczXtbby4Rej+icqvB0dmZBdieR+LGO0LYdv5my+E/9O4fCL9ZxmcxORpktGXamBpjQIDAQAB;" |
Vulnerability description
We found that the DKIM record uses common selectors. The use of common DKIM selectors such as default, test, dkim, or mail may indicate a lack of proper customization or key management. Attackers often target domains using such selectors because they suggest that the domain is relying on default configurations, which could be less secure and easier to exploit. This can increase the risk of DKIM key exposure or misuse.
Risk description
Using a common DKIM selector makes it easier for attackers to predict and exploit email authentication weaknesses. Attackers may attempt to find corresponding DKIM keys or improperly managed records associated with common selectors. If a common selector is coupled with a weak key length or poor key management practices, it significantly increases the likelihood of email spoofing and phishing attacks.
Recommendation
We recommend using unique, customized selectors for each DKIM key to make it more difficult for attackers to predict and target the domain's DKIM records. Regularly rotate selectors and associated keys to further strengthen the security of your domain's email authentication infrastructure.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| mechsafety.com | TXT | Text record | "google-site-verification=u2V8SAlkjve0bumxUJ2QgHohh-i9SSwELxmpBM-x4gM" |
Vulnerability description
We found that the target server has no DMARC policy configured. A missing DMARC (Domain-based Message Authentication, Reporting, and Conformance) policy means that the domain is not enforcing any DMARC policies to protect against email spoofing and phishing attacks. Without DMARC, even if SPF (Sender Policy Framework) or DKIM (DomainKeys Identified Mail) are configured, there is no mechanism to tell receiving email servers how to handle messages that fail authentication. This leaves the domain vulnerable to abuse, such as email spoofing and impersonation.
Risk description
Without a DMARC policy, your domain is highly vulnerable to email spoofing, allowing attackers to impersonate your brand and send fraudulent emails that appear legitimate. This can lead to phishing attacks targeting your customers, employees, or partners, potentially resulting in stolen credentials, financial loss, or unauthorized access to sensitive systems. Additionally, repeated spoofing attempts can severely damage your brand's reputation, as recipients may lose trust in communications from your domain, associating your brand with malicious activity. The absence of DMARC also prevents you from monitoring and mitigating email-based attacks, leaving your domain exposed to ongoing abuse.
Recommendation
We recommend implementing a DMARC policy for your domain. Start by configuring a DMARC record with a policy of p=none, which will allow you to monitor email flows without impacting legitimate emails. This initial setup helps identify how emails from your domain are being processed by recipient servers. Once you’ve verified that legitimate emails are passing SPF and DKIM checks, you can gradually enforce stricter policies like p=quarantine or p=reject to protect against spoofing and phishing attacks. Additionally, include rua and ruf email addresses in the DMARC record to receive aggregate and forensic reports. These reports will provide valuable insights into authentication failures and help you detect any spoofing attempts.
Evidence
| Operating System | Accuracy |
|---|---|
| FreeBSD 11.0-STABLE | 91% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| Optimizely | A/B Testing, Personalisation |
| Google Tag Manager | Tag managers |
| Cloudflare | CDN |
| HTTP/3 | Miscellaneous |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.
Evidence
| Software / Version | Category |
|---|---|
| cPanel | Hosting panels |
| Optimizely | A/B Testing, Personalisation |
| Google Tag Manager | Tag managers |
| Cloudflare | CDN |
| HTTP/3 | Miscellaneous |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.
Evidence
| Software / Version | Category |
|---|---|
| Cloudflare | CDN |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.
Evidence
| Software / Version | Category |
|---|---|
| cPanel | Hosting panels |
| Optimizely | A/B Testing, Personalisation |
| Google Tag Manager | Tag managers |
| Cloudflare | CDN |
| HTTP/3 | Miscellaneous |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.
Evidence
| DKIM selector | Key type | Key size | Value |
|---|---|---|---|
| default | rsa | 1422 | "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEArbyxH/hfTwqQADBIuF+3dhdZgjU8uzU0rql7X5hebOYn9DCkxujcFcd2Kuktr7UNBzsUof+x4OGgQUEEFs1U0Ua5EaPvwmL8iY37XoArqQF8jRXczx0zw7tRYCKKL1JHDY3XCz7IPi25ZMDBScgp42gqq+kvOABUZF9HIvXYNoNIRNZwDV0D7kKuGphRoXjtz" "yB/+aCKQ5oBOoeXXh/zbrngfmH/4nmACZxlB8kIArq+YNpjZVylSaKncIIbtUag49gg/cgBaGgEatkRjtewczXtbby4Rej+icqvB0dmZBdieR+LGO0LYdv5my+E/9O4fCL9ZxmcxORpktGXamBpjQIDAQAB;" |
Evidence
| Software / Version | Category |
|---|---|
| Optimizely | A/B Testing, Personalisation |
| Google Tag Manager | Tag managers |
| Cloudflare | CDN |
| HTTP/3 | Miscellaneous |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.
Evidence
| Software / Version | Category |
|---|---|
| Cloudflare | CDN |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.
Evidence
| Software / Version | Category |
|---|---|
| WordPress 6.8.3 | CMS, Blogs |
| MySQL | Databases |
| PHP | Programming languages |
| RankMath SEO | WordPress plugins, SEO |
| Hello Elementor 3.1.0 | WordPress themes |
| Elementor 3.27.5 | Page builders, WordPress plugins |
| imagesLoaded 5.0.0 | JavaScript libraries |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| jQuery | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Google Analytics GA4 | Analytics |
| Cloudflare | CDN |
| HTTP/3 | Miscellaneous |
| Underscore.js 1.13.7 | JavaScript libraries |
| Clipboard.js | JavaScript libraries |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.
Evidence
| Software / Version | Category |
|---|---|
| WordPress 6.8.3 | CMS, Blogs |
| MySQL | Databases |
| PHP | Programming languages |
| RankMath SEO | WordPress plugins, SEO |
| Hello Elementor 3.1.0 | WordPress themes |
| Elementor 3.27.5 | Page builders, WordPress plugins |
| imagesLoaded 5.0.0 | JavaScript libraries |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| jQuery | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Google Analytics GA4 | Analytics |
| Cloudflare | CDN |
| HTTP/3 | Miscellaneous |
| Underscore.js 1.13.7 | JavaScript libraries |
| Clipboard.js | JavaScript libraries |
| Google Font API | Font scripts |
| RSS | Miscellaneous |
| Open Graph | Miscellaneous |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| mechsafety.com | A | IPv4 address | 172.67.185.112 |
| mechsafety.com | A | IPv4 address | 104.21.59.238 |
| mechsafety.com | NS | Name server | liberty.ns.cloudflare.com |
| mechsafety.com | NS | Name server | rayden.ns.cloudflare.com |
| mechsafety.com | MX | Mail server | 1 aspmx.l.google.com |
| mechsafety.com | MX | Mail server | 10 alt3.aspmx.l.google.com |
| mechsafety.com | MX | Mail server | 10 alt4.aspmx.l.google.com |
| mechsafety.com | MX | Mail server | 5 alt1.aspmx.l.google.com |
| mechsafety.com | MX | Mail server | 5 alt2.aspmx.l.google.com |
| mechsafety.com | SOA | Start of Authority | liberty.ns.cloudflare.com. dns.cloudflare.com. 2387717824 10000 2400 604800 1800 |
| mechsafety.com | AAAA | IPv6 address | 2606:4700:3032::6815:3bee |
| mechsafety.com | AAAA | IPv6 address | 2606:4700:3031::ac43:b970 |
| mechsafety.com | TXT | Text record | "google-site-verification=u2V8SAlkjve0bumxUJ2QgHohh-i9SSwELxmpBM-x4gM" |
| mechsafety.com | SPF | Sender Policy Framework | "v=spf1 ip4:192.185.4.23 a mx include:websitewelcome.com ~all" |
Risk description
An initial step for an attacker aiming to learn about an organization involves conducting searches on its domain names to uncover DNS records associated with the organization. This strategy aims to amass comprehensive insights into the target domain, enabling the attacker to outline the organization's external digital landscape. This gathered intelligence may subsequently serve as a foundation for launching attacks, including those based on social engineering techniques. DNS records pointing to services or servers that are no longer in use can provide an attacker with an easy entry point into the network.
Recommendation
We recommend reviewing all DNS records associated with the domain and identifying and removing unused or obsolete records.