Vulnerability Scan Result
| Title: | South Staffs Water | South Staffordshire Water |
| Description: | At South Staffs Water we deliver excellent water quality and secure and reliable water supplies supported by a first-rate customer experience to all customers and their communities |
| ip_address | 45.60.197.232 |
| country | US  |
| network_name | Incapsula Inc |
| asn | AS19551 |
21/tcp | ftp | - - |
25/tcp | smtp | - - |
37/tcp | time | - - |
43/tcp | whois | - - |
53/tcp | domain | - - |
80/tcp | https | - - |
81/tcp | hosts2-ns | - - |
88/tcp | kerberos-sec | - - |
110/tcp | pop3 | - - |
119/tcp | nntp | - - |
135/tcp | msrpc | - - |
139/tcp | netbios-ssn | - - |
143/tcp | imap | - - |
389/tcp | ldap | - - |
443/tcp | https | - - |
444/tcp | snpp | - - |
465/tcp | smtps | - - |
543/tcp | klogin | - - |
554/tcp | rtsp | - - |
587/tcp | submission | - - |
631/tcp | ipp | - - |
990/tcp | ftps | - - |
993/tcp | imaps | - - |
995/tcp | pop3s | - - |
1025/tcp | NFS-or-IIS | - - |
1028/tcp | other | - - |
1029/tcp | ms-lsa | - - |
1080/tcp | socks | - - |
1194/tcp | openvpn | - - |
1337/tcp | waste | - - |
1433/tcp | ms-sql-s | - - |
1701/tcp | l2f | - - |
1720/tcp | h323q931 | - - |
2000/tcp | cisco-sccp | - - |
2001/tcp | dc | - - |
2002/tcp | globe | - - |
2049/tcp | nfs | - - |
2078/tcp | tpcsrvr | - - |
2080/tcp | autodesk-nlm | - - |
2082/tcp | infowave | - - |
2083/tcp | radsec | - - |
2086/tcp | gnunet | - - |
2087/tcp | eli | - - |
2100/tcp | amiganetfs | - - |
2121/tcp | ccproxy-ftp | - - |
2222/tcp | EtherNetIP-1 | - - |
2967/tcp | symantec-av | - - |
3000/tcp | ppp | - - |
3050/tcp | gds_db | - - |
3306/tcp | mysql | - - |
3389/tcp | ms-wbt-server | - - |
3690/tcp | svn | - - |
4280/tcp | vrml-multi-use | - - |
4333/tcp | msql | - - |
4444/tcp | krb524 | - - |
4445/tcp | upnotifyp | - - |
5000/tcp | upnp | - - |
5004/tcp | avt-profile-1 | - - |
5005/tcp | avt-profile-2 | - - |
5009/tcp | airport-admin | - - |
5051/tcp | ida-agent | - - |
5060/tcp | sip | - - |
5222/tcp | xmpp-client | - - |
5223/tcp | hpvirtgrp | - - |
5631/tcp | pcanywheredata | - - |
5800/tcp | vnc-http | - - |
5900/tcp | vnc | - - |
5901/tcp | vnc-1 | - - |
5985/tcp | wsman | - - |
5986/tcp | wsmans | - - |
6000/tcp | X11 | - - |
6001/tcp | X11:1 | - - |
6379/tcp | redis | - - |
6699/tcp | napster | - - |
7000/tcp | afs3-fileserver | - - |
7001/tcp | afs3-callback | - - |
7070/tcp | realserver | - - |
8000/tcp | https | - - |
8008/tcp | https | - - |
8009/tcp | ajp13 | - - |
8080/tcp | https | - - |
8081/tcp | blackice-icecap | - - |
8200/tcp | trivnet1 | - - |
8222/tcp | other | - - |
8443/tcp | https-alt | - - |
8500/tcp | fmtp | - - |
8888/tcp | sun-answerbook | - - |
9000/tcp | cslistener | - - |
9042/tcp | other | - - |
9100/tcp | jetdirect | - - |
9800/tcp | davsrc | - - |
9999/tcp | abyss | - - |
10000/tcp | snet-sensor-mgmt | - - |
20000/tcp | dnp | - - |
| Software / Version | Category |
|---|---|
| Azure | PaaS |
| cdnjs | CDN |
| Azure Front Door | Load balancers |
| Facebook Pixel 2.9.319 | Analytics |
| Font Awesome 4.7.0 | Font scripts |
| Adobe Fonts | Font scripts |
| Bootstrap 5.3.3 | UI frameworks |
| Pikaday | JavaScript libraries |
| core-js 3.32.2 | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| jQuery 3.7.1 | JavaScript libraries |
| jQuery UI 1.13.2 | JavaScript libraries |
| Slick | JavaScript libraries |
| Modernizr 2.8.3 | JavaScript libraries |
| MySQL | Databases |
| PHP | Programming languages |
| DoubleClick Floodlight | Advertising |
| Typekit | Font scripts |
| WordPress | CMS, Blogs |
| Microsoft ASP.NET | Web frameworks |
| Cloudflare | CDN |
| CookieYes | Cookie compliance |
| Google Tag Manager | Tag managers |
| Imperva | Security, CDN |
| jsDelivr | CDN |
| Qualtrics | Surveys |
| HSTS | Security |
Web Application Vulnerabilities
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://south-staffs-water.co.uk/ | nlbi_2863621 | Set-Cookie: .south-staffs-water.co.uk |
Vulnerability description
We found that the target application sets cookies with a domain scope that is too broad. Specifically, cookies intended for use within a particular application are configured in such a way that they can be accessed by multiple subdomains of the same primary domain.
Risk description
The risk is that a cookie set for example.com may be sent along with the requests sent to dev.example.com, calendar.example.com, hostedsite.example.com. Potentially risky websites under your main domain may access those cookies and use the victim session from the main site.
Recommendation
The `Domain` attribute should be set to the origin host to limit the scope to that particular server. For example if the application resides on server app.mysite.com, then it should be set to `Domain=app.mysite.com`
Classification
| CWE | CWE-614 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://south-staffs-water.co.uk/ | incap_ses_63_2863621 | The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: incap_ses_63_2863621=efp3WQS+H27esd47mNLfAHcHBGoAAAAAEG+cZ4tvvT0a9JV14976hQ== |
Vulnerability description
We found that a cookie has been set without the HttpOnly flag, which means it can be accessed by potentially malicious JavaScript code running inside the web page. The root cause for this usually revolves around misconfigurations in the code or server settings.
Risk description
The risk is that an attacker who injects malicious JavaScript code on the page (e.g. by using an XSS attack) can access the cookie and can send it to another site. In case of a session cookie, this could lead to session hijacking.
Recommendation
Ensure that the HttpOnly flag is set for all cookies.
Classification
| CWE | CWE-1004 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://south-staffs-water.co.uk/ | 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://south-staffs-water.co.uk/ | 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-1021 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| Software / Version | Category |
|---|---|
| Azure | PaaS |
| cdnjs | CDN |
| Azure Front Door | Load balancers |
| Facebook Pixel 2.9.319 | Analytics |
| Font Awesome 4.7.0 | Font scripts |
| Adobe Fonts | Font scripts |
| Bootstrap 5.3.3 | UI frameworks |
| Pikaday | JavaScript libraries |
| core-js 3.32.2 | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| jQuery 3.7.1 | JavaScript libraries |
| jQuery UI 1.13.2 | JavaScript libraries |
| Slick | JavaScript libraries |
| Modernizr 2.8.3 | JavaScript libraries |
| MySQL | Databases |
| PHP | Programming languages |
| DoubleClick Floodlight | Advertising |
| Typekit | Font scripts |
| WordPress | CMS, Blogs |
| Microsoft ASP.NET | Web frameworks |
| Cloudflare | CDN |
| CookieYes | Cookie compliance |
| Google Tag Manager | Tag managers |
| Imperva | Security, CDN |
| jsDelivr | CDN |
| Qualtrics | Surveys |
| HSTS | Security |
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.
Classification
| CWE | CWE-200 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://south-staffs-water.co.uk/ | 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 | Method | Parameters | Evidence |
|---|---|---|---|
| https://south-staffs-water.co.uk/developer/regulations/notify-us-of-an-installation | 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 Cookies: incap_ses_63_2863621=SDF5AO1ZR2nesd47mNLfAHcHBGoAAAAAfSpT5xlaBWtd0XIl2GdtZw== incap_wrt_363=eAcEagAAAAB4GVZmGQAI6wIQ0IOxtSIYrJCQ0AYgAij1jpDQBj... | Email Address: waterregulations@south-staffs-water.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 | Method | Parameters | Evidence |
|---|---|---|---|
| https://south-staffs-water.co.uk/developer/get-connected/connection-requirements/ | 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 Cookies: incap_ses_63_2863621=SDF5AO1ZR2nesd47mNLfAHcHBGoAAAAAfSpT5xlaBWtd0XIl2GdtZw== incap_wrt_363=eAcEagAAAAB4GVZmGQAI6wIQ0IOxtSIYrJCQ0AYgAij1jpDQBj... | Operating system paths found in the HTTP response: |
| https://south-staffs-water.co.uk/developer/regulations/notify-us-of-an-installation | 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 Cookies: incap_ses_63_2863621=SDF5AO1ZR2nesd47mNLfAHcHBGoAAAAAfSpT5xlaBWtd0XIl2GdtZw== incap_wrt_363=eAcEagAAAAB4GVZmGQAI6wIQ0IOxtSIYrJCQ0AYgAij1jpDQBj... | Operating system paths found in the HTTP response: |
| https://south-staffs-water.co.uk/household/extra-help/priority-services-register | 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 Cookies: incap_ses_63_2863621=SDF5AO1ZR2nesd47mNLfAHcHBGoAAAAAfSpT5xlaBWtd0XIl2GdtZw== incap_wrt_363=egcEagAAAACDUcRHGQAI6wIQ0IOxtSIYrpCQ0AYgAij1jpDQBj... | Operating system paths found in the HTTP response: |
Vulnerability description
We found operating system paths returned in a HTTP response.
Risk description
The risk is that path disclosure may help an attacker learn more about the remote server's file system, thus increasing the effectiveness and precision of any future attacks.
Recommendation
Configure the web server to avoid leaking path information by using generic error messages that do not reveal any internal file paths. Make sure no server file is referred with its absolute path in the website code.
Classification
| CWE | CWE-200 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
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.
Classification
| CWE | CWE-1188 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Infrastructure Vulnerabilities
Evidence
We managed to detect a publicly accessible Virtual Network Computing (VNC) service. PORT STATE SERVICE VERSION 5800/tcp open vnc-http
Vulnerability description
We found that the Virtual Network Computing (VNC) service is publicly accessible. VNC, widely used for remote desktop access, enables users to remotely view and interact with a computer's desktop environment. This capability makes it a prime target for attackers.
Risk description
The risk exists that by exploiting this service, an attacker could launch an authentication attack that can lead to unauthorized access and control over network resources.
Recommendation
We recommend turning off VNC access over the public Internet and instead using a Virtual Private Network (VPN) that mandates two-factor authentication (2FA). If the VNC service is essential for business purposes, limiting access to designated IP addresses is recommended.
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | CISA KEV | Summary |
|---|---|---|---|---|---|
| CVE-2020-11023 | 6.9 | 0.439 | 0.97566 | Yes | In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0. |
| CVE-2020-11022 | 6.9 | 0.02391 | 0.85149 | No | In jQuery starting with 1.12.0 and before 3.5.0, passing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0. |
| CVE-2019-11358 | 6.1 | 0.02362 | 0.85058 | No | jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. If an unsanitized source object contained an enumerable __proto__ property, it could extend the native Object.prototype. |
Vulnerability description
Vulnerabilities found for jQuery 3.3.1
Risk description
These vulnerabilities expose the affected applications to the risk of unauthorized access to confidential data and possibly to denial of service attacks. An attacker could search for an appropriate exploit (or create one) for any of these vulnerabilities and use it to attack the system. Notes: - The vulnerabilities are identified based on the server's version.; - Only the first 5 vulnerabilities with the highest risk are shown for each port.; Since the vulnerabilities were discovered using only version-based testing, the risk level for this finding will not exceed "high" severity. Critical risks will be assigned to vulnerabilities identified through accurate active testing methods.
Recommendation
We recommend you to upgrade the affected software to the latest version in order to eliminate the risks imposed by these vulnerabilities.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| south-staffs-water.co.uk | SPF | Sender Policy Framework | "v=spf1 include:_u.south-staffs-water.co.uk._spf.dmarcld.com include:spf.protection.outlook.com ip4:168.245.25.91 include:_spf.salesforce.com include:spf.mailjet.com include:_spf.psm.knowbe4.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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.south-staffs-water.co.uk | TXT | Text record | "v=DMARC1; p=quarantine; rua=mailto:63b408bb82993@ag.dmarcly.com; ruf=mailto:63b408bb82993@fo.dmarcly.com; sp=quarantine; fo=0;" |
Vulnerability description
We found that the target uses p=quarantine in the DMARC policy. When a DMARC policy is set to p=quarantine, emails that fail DMARC validation are delivered but placed in the recipient’s spam or junk folder. Although it offers some protection, this policy is less strict than p=reject, which blocks such emails entirely.
Risk description
While emails failing DMARC validation are sent to the spam folder, users may still retrieve them from there, leading to a higher risk of phishing and spoofing attacks succeeding. Moreover, less strict enforcement may allow more fraudulent emails to reach user inboxes if misclassified.
Recommendation
We recommend considering moving to a stricter policy, such as p=reject, where emails that fail DMARC validation are completely rejected rather than delivered to spam folders. This reduces the risk of users interacting with potentially malicious emails.
Evidence
We found insecure DNS cookie usage on the following nameservers: ns37.domaincontrol.com, ns38.domaincontrol.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
| DKIM selector | Key type | Key size | Value |
|---|---|---|---|
| mailjet | rsa | 1296 | "k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCgD7Nsme87wxEtyH5DtX0lyHdCzT5fzktIczxZ99AnIs/Fdqz5KrrdqWf6M1VYBR3sjpq7GLFuCa5zmf9MzhuBwnHVqO8HhtAV7mjgHpO6pw+U1qrkPNr4kqvhQ7tOzWvo7wG2c8F8RMlfuIGa4TrCcwgNPwV6nv68rnom6asGMQIDAQAB" |
| selector1 | rsa | 1296 | "v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDB0imXzK/Z7D4NSbJtQ/SWNqi6JehirSm7sTz7VpYPRGR6A7kPRnIBQCtufpwjXAl8O/dZrg2cbZPmW8P9ENhQX09kHxCOkjxg4spYWxKVGOR8LhypZusaalLBVCMbe7xKgyyydhxvCBlHbPUYFFXNlpCU0gl4pvB4y2vu9vPv5wIDAQAB; n=1024,1505972056,1" "521610456" |
| selector2 | rsa | 1296 | "v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC7E4pZlf3HGQtH0Ju+Kpz9+Yc5A1Xjub/jM1qBFqjTb3ImThKHJEPv+5U4McjnmAi90ODjLyUD0AVf18b7zfI7E7nce77Jfgg/Scny8YdOB+kakvisC1xRTeNKrBakwFaflNC/p/plzn3v1z+9yCjfylgJKG5DEX/SdiUZkwvcbwIDAQAB; n=1024,1505972056,1" |
Evidence
| Software / Version | Category |
|---|---|
| WordPress | CMS, Blogs |
| MySQL | Databases |
| PHP | Programming languages |
| Bootstrap 5.3.3 | UI frameworks |
| Microsoft ASP.NET | Web frameworks |
| Azure Front Door | Load balancers |
| Azure | PaaS |
| Cloudflare | CDN |
| Typekit | Font scripts |
| Slick | JavaScript libraries |
| Qualtrics | Surveys |
| Pikaday | JavaScript libraries |
| Modernizr | JavaScript libraries |
| jsDelivr | CDN |
| jQuery UI 1.13.2 | JavaScript libraries |
| jQuery 3.3.1 | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Google Analytics GA4 | Analytics |
| Facebook Pixel 2.9.319 | Analytics |
| CookieYes | Cookie compliance |
| cdnjs | CDN |
| Adobe Fonts | Font scripts |
| DoubleClick Floodlight | Advertising |
| Imperva | Security, CDN |
| HSTS | Security |
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
| Operating System | Accuracy |
|---|---|
| Windows | 100% |
Vulnerability description
OS Detection
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| south-staffs-water.co.uk | A | IPv4 address | 45.60.197.232 |
| south-staffs-water.co.uk | NS | Name server | ns37.domaincontrol.com |
| south-staffs-water.co.uk | NS | Name server | ns38.domaincontrol.com |
| south-staffs-water.co.uk | MX | Mail server | 1 southstaffswater-co-uk01c1b.mail.protection.outlook.com |
| south-staffs-water.co.uk | SOA | Start of Authority | ns37.domaincontrol.com. dns.jomax.net. 2026033000 28800 7200 604800 600 |
| south-staffs-water.co.uk | TXT | Text record | "F800-87C0-42EE-DC89-C3F1-0B78-8403-DD4C" |
| south-staffs-water.co.uk | TXT | Text record | "globalsign-domain-verification=4DB4EB473B855767B05554D1820E1881" |
| south-staffs-water.co.uk | TXT | Text record | "hic5cn787cger35fbvl58gclr9" |
| south-staffs-water.co.uk | TXT | Text record | "globalsign-domain-verification=7565A7A260B60D163C26E739B9D981C3" |
| south-staffs-water.co.uk | TXT | Text record | "uq8787ll7r1o2fu40dc0l2egia" |
| south-staffs-water.co.uk | TXT | Text record | "ht09isnmqkmg89fkbc8t1se1r7" |
| south-staffs-water.co.uk | TXT | Text record | "globalsign-domain-verification=9IbmdYA9de-_vK2BO1oKgNXyrbtbOM6bKFyPXTVwGN" |
| south-staffs-water.co.uk | TXT | Text record | "google-site-verification=vz_Xmiets7OGDJmyxCNeAGORuH6XP_i-KNyxammB-3M" |
| south-staffs-water.co.uk | TXT | Text record | "tgvbsui2i9jpva07a88cp8p5o" |
| south-staffs-water.co.uk | TXT | Text record | "8c4oifktgupoqia3iq431bsm72" |
| south-staffs-water.co.uk | TXT | Text record | "pb436bk7p12d78nsqju0llu9gn" |
| south-staffs-water.co.uk | TXT | Text record | "F220-7EF8-13DB-7BCE-7F7C-5E37-0BD1-170C" |
| south-staffs-water.co.uk | TXT | Text record | "33WNC6TEH2XKUAWU6EVY7P6HYFG3RN5P" |
| south-staffs-water.co.uk | TXT | Text record | "MS=ms35862600" |
| south-staffs-water.co.uk | TXT | Text record | "globalsign-domain-verification=3DE8A7BC472B260463D77968454B2952" |
| south-staffs-water.co.uk | TXT | Text record | "l6oqascmm4nun7rp3l5r60fcne" |
| south-staffs-water.co.uk | TXT | Text record | "A75B-9112-337C-F596-8045-CFB2-C3EB-1959" |
| south-staffs-water.co.uk | TXT | Text record | "6bagoorqfgbeauem5lga2v0ttm" |
| south-staffs-water.co.uk | TXT | Text record | "thdvo5vgp20q7r96joqgmuu08t" |
| south-staffs-water.co.uk | TXT | Text record | "d3lheqddvaj19ucdol1584vtod" |
| south-staffs-water.co.uk | TXT | Text record | "globalsign-domain-verification=312AC2040CBC0038E61773F7D89C3A01" |
| south-staffs-water.co.uk | TXT | Text record | "5oe36dgtsttrh3q96br3b9kss8" |
| south-staffs-water.co.uk | TXT | Text record | "globalsign-domain-verification=705436BDBACF0C5FDE2B4862D0C2B061" |
| south-staffs-water.co.uk | TXT | Text record | "G0EwCdvU87M2uN7CqPZlULZs18JmN/0XuJElBRL5keWYfcRHt5ri/hAZr5J4vFvrIExITPHX1ViDu6Q68cNdRg==" |
| south-staffs-water.co.uk | SPF | Sender Policy Framework | "v=spf1 include:_u.south-staffs-water.co.uk._spf.dmarcld.com include:spf.protection.outlook.com ip4:168.245.25.91 include:_spf.salesforce.com include:spf.mailjet.com include:_spf.psm.knowbe4.com ~all" |
| _dmarc.south-staffs-water.co.uk | TXT | Text record | "v=DMARC1; p=quarantine; rua=mailto:63b408bb82993@ag.dmarcly.com; ruf=mailto:63b408bb82993@fo.dmarcly.com; sp=quarantine; fo=0;" |
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.