Vulnerability Scan Result
| Title: | impost.uk - For Sale |
| Description: | Saw.com has successfully helped thousands of buyers acquire the perfect domain name. Interested in impost.uk? Let’s get started. |
| ip_address | 45.77.110.111 |
| country | US  |
| network_name | The Constant Company, LLC |
| asn | AS20473 |
| ip_address | 64.176.195.8 |
| country | US |
| network_name | The Constant Company, LLC |
| asn | AS20473 |
| ip_address | 149.28.42.111 |
| country | US |
| network_name | The Constant Company, LLC |
| asn | AS20473 |
80/tcp | http | Caddy httpd - |
443/tcp | https | - - |
| Software / Version | Category |
|---|---|
| Trustpilot | Reviews |
| Bootstrap 5 | UI frameworks |
| HTTP/3 | Miscellaneous |
| SvelteKit | UI frameworks |
| Open Graph | Miscellaneous |
| PayPal | Payment processors |
| Svelte | JavaScript frameworks |
| Vite | Miscellaneous |
| jsDelivr | CDN |
| HSTS | Security |
Web Application Vulnerabilities
Evidence
| Software / Version | Category |
|---|---|
| Trustpilot | Reviews |
| Bootstrap 5 | UI frameworks |
| HTTP/3 | Miscellaneous |
| SvelteKit | UI frameworks |
| Open Graph | Miscellaneous |
| PayPal | Payment processors |
| Svelte | JavaScript frameworks |
| Vite | Miscellaneous |
| jsDelivr | 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.
Classification
| CWE | CWE-200 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://impost.uk/ | Response headers include the HTTP Content-Security-Policy security header with the following security issues: |
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-1021 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://impost.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 | Summary |
|---|---|---|
| https://impost.uk/ | OPTIONS | We did a HTTP OPTIONS request. The server responded with a 204 status code and the header: `Allow: GET, HEAD, OPTIONS, POST` Request / Response |
Vulnerability description
We have noticed that the webserver responded with an Allow HTTP header when an OPTIONS HTTP request was sent. This method responds to requests by providing information about the methods available for the target resource.
Risk description
The only risk this might present nowadays is revealing debug HTTP methods that can be used on the server. This can present a danger if any of those methods can lead to sensitive information, like authentication information, secret keys.
Recommendation
We recommend that you check for unused HTTP methods or even better, disable the OPTIONS method. This can be done using your webserver configuration.
Classification
| CWE | CWE-16 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://impost.uk/ | POST | Query: /offer= Body: minOffer=500 name=IMPOST.UK offer=number q=1123123 Headers: Content-Type=application/x-www-form-urlencoded 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.
Infrastructure Vulnerabilities
Evidence
We found insecure DNS cookie usage on the following nameservers: ns1.sawsells.com, ns2.sawsells.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
| Software / Version | Category |
|---|---|
| Bootstrap 5 | UI frameworks |
| Trustpilot | Reviews |
| jsDelivr | 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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| impost.uk | A | IPv4 address | 45.77.110.111 |
| impost.uk | A | IPv4 address | 64.176.195.8 |
| impost.uk | A | IPv4 address | 149.28.42.111 |
| impost.uk | NS | Name server | ns1.sawsells.com |
| impost.uk | NS | Name server | ns2.sawsells.com |
| impost.uk | MX | Mail server | 1 mail.nickstel.com |
| impost.uk | SOA | Start of Authority | ns1.sawsells.com. hostmaster.impost.uk. 2026050504 10800 3600 604800 3600 |
| impost.uk | TXT | Text record | "spf1 ip6:fd55:9e3b:0be7::/48 -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.
Evidence
| Software / Version | Category |
|---|---|
| Bootstrap 5 | UI frameworks |
| Trustpilot | Reviews |
| jsDelivr | CDN |
| HSTS | Security |
| 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
| Operating System | Accuracy |
|---|---|
| Linux 3.10 - 4.11 | 93% |
Vulnerability description
OS Detection