Vulnerability Scan Result

Target:

http://mkm.com/ (redirect)

Scanned target: https://mkm.com/

Submitted: Nov 19, 2025 from GD

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	MKM Building Supplies \| Your local experts
Description:	The UKs leading independent builders' merchant. Explore our range of building materials, timber, landscaping, plumbing, heating, bathroom, kitchens and more. Open to trade and public. Open a trade account today for great terms and benefits.

IP Information

ip_address	104.20.32.164
country	-
network_name	Cloudflare Inc
asn	AS13335

ip_address	172.66.174.54
country	-
network_name	Cloudflare Inc
asn	AS13335

Open Ports

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 -

Web Technologies

Software / Version	Category
Twitter Ads	Advertising
Google Cloud	IaaS
Google Cloud CDN	CDN
Cookie Script	Cookie compliance
Google Analytics	Analytics
MySQL	Databases
Nuxt.js	JavaScript frameworks, Web frameworks, Static site generator
PHP	Programming languages
Preact	JavaScript libraries
Survicate	Surveys
Vue.js	JavaScript frameworks
BigCommerce	Ecommerce
Cloudflare	CDN
Google Tag Manager	Tag managers
PrestaShop	Ecommerce
HSTS	Security
SpeedCurve	RUM
Vue Storefront 2	Ecommerce frontends

Web Application Vulnerabilities

Evidence

URL
https://mkm.com/robots.txt

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
Twitter Ads	Advertising
Google Cloud	IaaS
Google Cloud CDN	CDN
Cookie Script	Cookie compliance
Google Analytics	Analytics
MySQL	Databases
Nuxt.js	JavaScript frameworks, Web frameworks, Static site generator
PHP	Programming languages
Preact	JavaScript libraries
Survicate	Surveys
Vue.js	JavaScript frameworks
BigCommerce	Ecommerce
Cloudflare	CDN
Google Tag Manager	Tag managers
PrestaShop	Ecommerce
HSTS	Security
SpeedCurve	RUM
Vue Storefront 2	Ecommerce frontends

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

URL	Evidence
https://mkm.com/	Response headers include the HTTP Content-Security-Policy security header with the following security issues:script-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files. report-uri: report-uri is deprecated in CSP3. Please use the report-to directive instead. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. frame-ancestors: This directive tells the browser whether you want to allow your site to be framed or not. By preventing a browser from framing your site you can defend against attacks like clickjacking. The recommended value is 'none' or 'self'.

https://mkm.com/

Response headers include the HTTP Content-Security-Policy security header with the following security issues:script-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files. report-uri: report-uri is deprecated in CSP3. Please use the report-to directive instead. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. frame-ancestors: This directive tells the browser whether you want to allow your site to be framed or not. By preventing a browser from framing your site you can defend against attacks like clickjacking. The recommended value is 'none' or 'self'.

Vulnerability description

We noticed that the Content-Security-Policy (CSP) header configured for the web application includes unsafe directives. The CSP header activates a protection mechanism implemented in web browsers which prevents exploitation of Cross-Site Scripting vulnerabilities (XSS) by restricting the sources from which content can be loaded or executed.

Risk description

For example, if the unsafe-inline directive is present in the CSP header, the execution of inline scripts and event handlers is allowed. This can be exploited by an attacker to execute arbitrary JavaScript code in the context of the vulnerable application.

Recommendation

Remove the unsafe values from the directives, adopt nonces or hashes for safer inclusion of inline scripts if they are needed, and explicitly define the sources from which scripts, styles, images or other resources can be loaded.

Classification

CWE	CWE-693
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Evidence
https://mkm.com/	Response headers do not include the Referrer-Policy HTTP security header as well as the `<meta/>` tag with name 'referrer' is not present in the response.

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	Method	Parameters	Evidence
https://mkm.com/	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	Email Address: web.support@mkmbs.co.uk

Vulnerability description

We noticed that this web application exposes email addresses, which might be unintended. While not inherently a vulnerability, this information could be leveraged in social engineering or spam related activities.

Risk description

The risk is that exposed email addresses within the application could be accessed by unauthorized parties. This could lead to privacy violations, spam, phishing attacks, or other forms of misuse.

Recommendation

Compartmentalize the application to have 'safe' areas where trust boundaries can be unambiguously drawn. Do not allow email addresses to go outside of the trust boundary, and always be careful when interfacing with a compartment outside of the safe area.

Classification

CWE	CWE-200
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL
Missing: https://mkm.com/.well-known/security.txt

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.

Infrastructure Vulnerabilities

Evidence

Domain Queried	DNS Record Type	Description	Value
_dmarc.mkm.com	TXT	Text record	"v=DMARC1; p=reject; rua=mailto:9196b141413c4f7799111befef992b5c@dmarc-reports.cloudflare.net,mailto:1b08ee5011dd203@rep.dmarcanalyzer.com; ruf=mailto:1b08ee5011dd203@for.dmarcanalyzer.com; fo=1;"

Vulnerability description

We found that the DMARC record for the domain is not configured with sp policy, meaning that no policy is enforced for subdomains. When a DMARC record does not include a subdomain policy (sp directive), subdomains are not explicitly covered by the main domain's DMARC policy. This means that emails sent from subdomains (e.g., sub.example.com) may not be subject to the same DMARC enforcement as the main domain (example.com). As a result, attackers could potentially spoof emails from subdomains without being blocked or flagged, even if the main domain has a strict DMARC policy.

Risk description

Without a subdomain policy (sp directive) in the DMARC record, subdomains are not protected by the same DMARC enforcement as the main domain, leaving them vulnerable to spoofing attacks. This inconsistency can be exploited by attackers to send phishing emails from subdomains, undermining the organization’s overall email security.

Recommendation

To mitigate the risk, we recommend configuring the DMARC record with a subdomain policy by adding the sp=reject or sp=quarantine directive. This will extend DMARC enforcement to all subdomains, preventing spoofing attempts and maintaining consistent security across both the main domain and its subdomains.

Evidence

Domain Queried	DNS Record Type	Description	Value
mkm.com	SPF	Sender Policy Framework	"v=spf1 include:mailgun.org include:spf.protection.outlook.com include:eu._netblocks.mimecast.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

Software / Version	Category
PrestaShop	Ecommerce
Nuxt.js	JavaScript frameworks, Web frameworks, Static site generator
MySQL	Databases
PHP	Programming languages
Vue Storefront 2	Ecommerce frontends
Google Cloud	IaaS
Vue.js	JavaScript frameworks
HSTS	Security
Google Cloud CDN	CDN
Cloudflare	CDN
Twitter Ads	Advertising
Survicate	Surveys
SpeedCurve	RUM
Google Tag Manager	Tag managers
Google Analytics	Analytics
Cookie Script	Cookie compliance

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.

Operating System	Accuracy
FreeBSD 11.0-RELEASE	91%

Evidence

Software / Version	Category
BigCommerce	Ecommerce
Nuxt.js	JavaScript frameworks, Web frameworks, Static site generator
Vue Storefront 2	Ecommerce frontends
Vue.js	JavaScript frameworks
SpeedCurve	RUM
Google Tag Manager	Tag managers

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
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

Domain Queried	DNS Record Type	Description	Value
mkm.com	A	IPv4 address	104.20.32.164
mkm.com	A	IPv4 address	172.66.174.54
mkm.com	NS	Name server	eugene.ns.cloudflare.com
mkm.com	NS	Name server	priscilla.ns.cloudflare.com
mkm.com	MX	Mail server	15 eu-smtp-inbound-1.mimecast.com
mkm.com	SOA	Start of Authority	eugene.ns.cloudflare.com. dns.cloudflare.com. 2388440379 10000 2400 604800 1800
mkm.com	AAAA	IPv6 address	2606:4700:10::6814:20a4
mkm.com	AAAA	IPv6 address	2606:4700:10::ac42:ae36
mkm.com	TXT	Text record	"v=verifydomain MS=7663986"
mkm.com	TXT	Text record	"7behubikv245lae1h1jci8op1g"
mkm.com	TXT	Text record	"29da398cb458564316aca83c0e226dcd"
mkm.com	TXT	Text record	"CKO=cli_acq4y6764u4ehgdgvf5ecu7ngq"
mkm.com	TXT	Text record	"0ed1fe018a81f322c97ff94b838d067832ffdcc4f9"
mkm.com	TXT	Text record	"facebook-domain-verification=8x4st2mz093pqe3pj9ji10uxalqmg1"
mkm.com	TXT	Text record	"tacklephishing-domain-verification=6bb866fa02c4477dad362dba58ae7e54"
mkm.com	TXT	Text record	"google-site-verification=dLRCL4Efu3xVvwHcV3IaZ5rs3CRy2Kfxxb-0mk5vqR0"
mkm.com	TXT	Text record	"atlassian-domain-verification=OEj2aawKx421ZiT3Qr12otgb44aopgOMYOfq4nCLwp1Y849J2MQL2OFlChehEc/s"
mkm.com	SPF	Sender Policy Framework	"v=spf1 include:mailgun.org include:spf.protection.outlook.com include:eu._netblocks.mimecast.com ~all"
_dmarc.mkm.com	TXT	Text record	"v=DMARC1; p=reject; rua=mailto:9196b141413c4f7799111befef992b5c@dmarc-reports.cloudflare.net,mailto:1b08ee5011dd203@rep.dmarcanalyzer.com; ruf=mailto:1b08ee5011dd203@for.dmarcanalyzer.com; fo=1;"

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.

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
BigCommerce	Ecommerce
Nuxt.js	JavaScript frameworks, Web frameworks, Static site generator
Vue Storefront 2	Ecommerce frontends
Vue.js	JavaScript frameworks
SpeedCurve	RUM
Google Tag Manager	Tag managers

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
s1	rsa	1446	"k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEArEKPvXz1kBiQVEoxN9sLKMweTWxm4evAVLCBOUvliTpyMqoZtAphiTxRnAmm7y3qjO4lKPXgSSYDduN1L8NJf5XBJYQ3cLUqOA0itweJ8JQi+PAB03DPeFhV85ih3zl3I9+xAFdlr9/lgQatUTPOyR643f2FhNR1lhq0ikoRX/j+LG6F/geAQITwp2AoRiyfMNRLo" "a0MWjfPE4iPCz2FPxlz/5Cpp5+g+IbxyYuQ/4laDkDWSlabGaPeBbUqrn35K69Dh8XBwoIUltci9b7iVTqHRX0K+cDxnmMfTcSD3EQ0VK5p8Xi4h0X1doAoY2Li6lyDyO7vy0OCXGOg2/NmUwIDAQAB"
s2	rsa	1296	"k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC+XYRLMRNPCAhT2FLYDm15ryXBRXYAE0n+Jy+BbcbsDV2Iwl/DJpnb40nxPPa0XCpXDBat0bdgFYCEr2ScbKQjpDygQ1PJ2PEBYDb0+YtpNGSMJDJ02ze/Vz9pK1mM2HjhM4ji5X0krB6I8FnWaP6LUWtfNVOeBRqtWBu89WYSWwIDAQAB"

Evidence

Software / Version	Category
BigCommerce	Ecommerce
Nuxt.js	JavaScript frameworks, Web frameworks, Static site generator
Vue Storefront 2	Ecommerce frontends
Google Cloud	IaaS
Vue.js	JavaScript frameworks
SpeedCurve	RUM
Google Tag Manager	Tag managers
HSTS	Security
Google Cloud CDN	CDN
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.