Vulnerability Scan Result

Target:

https://shrt.co.il/YDW71/ (redirect)

Scanned target: https://shrt.co.il/

Submitted: Aug 17, 2025 from EG

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	SHRT \| ××£ ×¨××©×
Description:	××ª×¨ SHRT ××× × ××ª×¨ ××§××¦××¨ ××ª××××ª ××××¨ ×××××× ×××××××ª× ×××× × ×××× ××¨× ×! ×§××¦××¨ ××ª×××ª ×ª××× ×××¨× ×× ×××¨×××ª ××¨×× ×××ª×¨ ×××××ª× ××ª×¦××× ××× ×©××, × ×¡× ×× ×ª×ª×××××!

IP Information

ip_address	76.76.21.21
country	US
network_name	Amazon Inc
asn	AS16509

Open Ports

80/tcp	http	Vercel -
443/tcp	https	Vercel -

Web Technologies

Software / Version	Category
Next.js 12.2.5	JavaScript frameworks, Web frameworks, Web servers, Static site generator
NextUI	UI frameworks
Open Graph	Miscellaneous
React	JavaScript frameworks
Stitches	JavaScript frameworks, Development
styled-components 5.3.5	JavaScript frameworks, Development
Vercel	PaaS
Webpack	Miscellaneous
HSTS	Security

Web Application Vulnerabilities

Evidence

URL	Evidence
https://shrt.co.il/	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
https://shrt.co.il/	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	Evidence
https://shrt.co.il/	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

Software / Version	Category
Next.js 12.2.5	JavaScript frameworks, Web frameworks, Web servers, Static site generator
NextUI	UI frameworks
Open Graph	Miscellaneous
React	JavaScript frameworks
Stitches	JavaScript frameworks, Development
styled-components 5.3.5	JavaScript frameworks, Development
Vercel	PaaS
Webpack	Miscellaneous
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
Missing: https://shrt.co.il/.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

Software / Version	Category
Stitches	JavaScript frameworks, Development
NextUI	UI frameworks
React	JavaScript frameworks
Vercel	PaaS
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

Domain Queried	DNS Record Type	Description	Value
shrt.co.il	A	IPv4 address	76.76.21.21
shrt.co.il	NS	Name server	park2.livedns.co.il
shrt.co.il	NS	Name server	park1.livedns.co.il
shrt.co.il	SOA	Start of Authority	park1.livedns.co.il. hostmaster.shrt.co.il. 2022091100 3600 600 1209600 14400

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.