Vulnerability Scan Result

Target:

https://rebrandidentity.com/

Scanned target: https://rebrandidentity.com/

Submitted: Oct 15, 2025 from IN

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	rebrandidentity.com - For Sale
Description:	rebrandidentity.com is available for sale. The minimum offer price is not indicative of a selling point—Make your best offer.

IP Information

ip_address	108.61.73.182
country	US
network_name	The Constant Company LLC
asn	AS20473

ip_address	149.28.227.54
country	US
network_name	The Constant Company LLC
asn	AS20473

Open Ports

22/tcp	ssh	OpenSSH 9.2p1 Debian 2+deb12u7
80/tcp	http	Caddy httpd -
443/tcp	https	- -
9100/tcp	http	- -

Web Technologies

Software / Version	Category
Trustpilot	Reviews
Caddy	Web servers
Bootstrap 5	UI frameworks
Go	Programming languages
HTTP/3	Miscellaneous
SvelteKit	UI frameworks
Node.js	Programming languages
Svelte	JavaScript frameworks
Vite	Miscellaneous
jsDelivr	CDN
HSTS	Security

Web Application Vulnerabilities

Evidence

Software / Version	Category
Trustpilot	Reviews
Caddy	Web servers
Bootstrap 5	UI frameworks
Go	Programming languages
HTTP/3	Miscellaneous
SvelteKit	UI frameworks
Node.js	Programming languages
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.

Evidence

URL	Evidence
https://rebrandidentity.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 Evidence

URL	Evidence
https://rebrandidentity.com/	Response headers include the HTTP Content-Security-Policy security header with the following security issues:`script-src: script-src directive is missing. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'. base-uri: Missing base-uri allows the injection of base tags. They can be used to set the base URL for all relative (script) URLs to an attacker controlled domain. We recommend setting it to 'none' or 'self'.`

https://rebrandidentity.com/

Response headers include the HTTP Content-Security-Policy security header with the following security issues:script-src: script-src directive is missing. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'. base-uri: Missing base-uri allows the injection of base tags. They can be used to set the base URL for all relative (script) URLs to an attacker controlled domain. We recommend setting it to '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	Method	Parameters	Evidence
https://rebrandidentity.com/	POST	Query: /offer= Body: minOffer=500 name=REBRANDIDENTITY.COM 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.

Evidence

URL	Method	Summary
https://rebrandidentity.com/	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

Infrastructure Vulnerabilities

Evidence

We managed to detect a publicly accessible SSH service. Starting Nmap ( https://nmap.org ) at 2025-10-15 05:52 EEST Nmap scan report for rebrandidentity.com (108.61.73.182) Host is up (0.081s latency). Other addresses for rebrandidentity.com (not scanned): 149.28.227.54 rDNS record for 108.61.73.182: 108.61.73.182.vultrusercontent.com

PORT STATE SERVICE VERSION 22/tcp open ssh OpenSSH 9.2p1 Debian 2+deb12u7 (protocol 2.0) | ssh-auth-methods: | Supported authentication methods: | publickey |_ password Service Info: OS: Linux; CPE: cpe:/o:linux:linux_kernel

Service detection performed. Please report any incorrect results at https://nmap.org/submit/ . Nmap done: 1 IP address (1 host up) scanned in 1.76 seconds

Vulnerability description

We found that the SSH service with username/password authentication is publicly accessible. Network administrators often use remote administration protocols to control devices like switches, routers, and other essential systems. However, allowing these services to be accessible via the Internet can increase security risks, creating potential opportunities for attacks on the organization.

Risk description

Exposing this service online with username/password authentication can enable attackers to launch authentication attacks, like guessing login credentials, and potentially gaining unauthorized access. Vulnerabilities, such as unpatched software, protocol flaws, or backdoors could also be exploited. An example is the CVE-2024-3094 (XZ Utils Backdoor) vulnerability.

Recommendation

We recommend turning off SSH with username/password authentication access over the Internet and instead using a Virtual Private Network (VPN) that mandates two-factor authentication (2FA). If the SSH service is essential for business purposes, we recommend limiting access only from designated IP addresses using a firewall. Furthermore, it is advisable to utilize SSH Public Key Authentication since it employs a key pair to verify the identity of a user or process.

Evidence

Domain Queried	DNS Record Type	Description	Value
rebrandidentity.com	A	IPv4 address	108.61.73.182
rebrandidentity.com	A	IPv4 address	149.28.227.54
rebrandidentity.com	NS	Name server	ns2.sawsells.com
rebrandidentity.com	NS	Name server	ns1.sawsells.com
rebrandidentity.com	SOA	Start of Authority	ns1.sawsells.com. hostmaster.rebrandidentity.com. 2025101502 10800 3600 604800 3600

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
Go	Programming languages
Node.js	Programming languages
Bootstrap 5	UI frameworks
SvelteKit	UI frameworks
Caddy	Web servers
Svelte	JavaScript frameworks
Trustpilot	Reviews
jsDelivr	CDN
HTTP/3	Miscellaneous
Vite	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
Go	Programming languages
Node.js	Programming languages
Bootstrap 5	UI frameworks
SvelteKit	UI frameworks
Caddy	Web servers
Svelte	JavaScript frameworks
Trustpilot	Reviews
jsDelivr	CDN
HSTS	Security
HTTP/3	Miscellaneous
Vite	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.