Vulnerability Scan Result

Target:

https://pixnoy.com/ (redirect)

Scanned target: https://www.pixnoy.com/

Submitted: May 15, 2026 from BY

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Pixnoy (formerly Pixwox): Instagram viewer and downloader
Description:	Anonymously view and download Instagram photos and videos from profiles, posts and stories without login.

IP Information

ip_address	104.26.6.225
country	-
network_name	Cloudflare, Inc.
asn	AS13335

ip_address	104.26.7.225
country	-
network_name	Cloudflare, Inc.
asn	AS13335

ip_address	172.67.71.150
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	https-alt	cloudflare -

Web Technologies

Software / Version	Category
Amazon Web Services	PaaS
Funding Choices	Cookie compliance
Google Publisher Tag	Advertising
Google Font API	Font scripts
Google Analytics GA4	Analytics
HTTP/3	Miscellaneous
MySQL	Databases
Open Graph	Miscellaneous
PHP	Programming languages
DoubleClick Floodlight	Advertising
PWA	Miscellaneous
WordPress	CMS, Blogs
Cloudflare	CDN
Connexity	Marketing automation
Google Tag Manager	Tag managers
Twiago	Advertising

Web Application Vulnerabilities

Evidence

URL	Evidence
https://www.pixnoy.com/	Response headers do not include the HTTP Strict-Transport-Security header

Vulnerability description

We noticed that the target application lacks the HTTP Strict-Transport-Security header in its responses. This security header is crucial as it instructs browsers to only establish secure (HTTPS) connections with the web server and reject any HTTP connections.

Risk description

The risk is that lack of this header permits an attacker to force a victim user to initiate a clear-text HTTP connection to the server, thus opening the possibility to eavesdrop on the network traffic and extract sensitive information (e.g. session cookies).

Recommendation

The Strict-Transport-Security HTTP header should be sent with each HTTPS response. The syntax is as follows: `Strict-Transport-Security: max-age=<seconds>[; includeSubDomains]` The parameter `max-age` gives the time frame for requirement of HTTPS in seconds and should be chosen quite high, e.g. several months. A value below 7776000 is considered as too low by this scanner check. The flag `includeSubDomains` defines that the policy applies also for sub domains of the sender of the response.

Classification

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

Evidence

URL	Evidence
https://www.pixnoy.com/	Response headers include the HTTP Content-Security-Policy security header with the following security issues:`object-src: We recommend restricting object-src to 'none'. script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval().`

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

Software / Version	Category
Amazon Web Services	PaaS
Funding Choices	Cookie compliance
Google Publisher Tag	Advertising
Google Font API	Font scripts
Google Analytics GA4	Analytics
HTTP/3	Miscellaneous
MySQL	Databases
Open Graph	Miscellaneous
PHP	Programming languages
DoubleClick Floodlight	Advertising
PWA	Miscellaneous
WordPress	CMS, Blogs
Cloudflare	CDN
Connexity	Marketing automation
Google Tag Manager	Tag managers
Twiago	Advertising

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
https://www.pixnoy.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

URL
Missing: https://www.pixnoy.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.

Classification

CWE	CWE-1188
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Infrastructure Vulnerabilities

Evidence

Software / Version	Category
WordPress	CMS, Blogs
MySQL	Databases
PHP	Programming languages
Amazon Web Services	PaaS
Google Publisher Tag	Advertising
Funding Choices	Cookie compliance
Twiago	Advertising
Connexity	Marketing automation
Google Tag Manager	Tag managers
Google Analytics GA4	Analytics
Cloudflare Browser Insights	Analytics, RUM
DoubleClick Floodlight	Advertising
Cloudflare	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

Software / Version	Category
Cloudflare	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.

Operating System	Accuracy
FreeBSD 11.1-STABLE	91%

Evidence

Software / Version	Category
Cloudflare	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

Software / Version	Category
WordPress	CMS, Blogs
MySQL	Databases
PHP	Programming languages
Amazon Web Services	PaaS
Google Publisher Tag	Advertising
Funding Choices	Cookie compliance
Twiago	Advertising
Connexity	Marketing automation
Google Tag Manager	Tag managers
Google Analytics GA4	Analytics
Cloudflare Browser Insights	Analytics, RUM
DoubleClick Floodlight	Advertising
Cloudflare	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

Software / Version	Category
WordPress	CMS, Blogs
MySQL	Databases
PHP	Programming languages
Amazon Web Services	PaaS
Google Publisher Tag	Advertising
Funding Choices	Cookie compliance
Twiago	Advertising
Connexity	Marketing automation
Google Tag Manager	Tag managers
Google Analytics GA4	Analytics
Cloudflare Browser Insights	Analytics, RUM
DoubleClick Floodlight	Advertising
Cloudflare	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

Software / Version	Category
Cloudflare	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

Software / Version	Category
WordPress	CMS, Blogs
MySQL	Databases
PHP	Programming languages
Amazon Web Services	PaaS
Google Publisher Tag	Advertising
Funding Choices	Cookie compliance
Google Tag Manager	Tag managers
Google Analytics GA4	Analytics
Cloudflare Browser Insights	Analytics, RUM
Twiago	Advertising
Connexity	Marketing automation
DoubleClick Floodlight	Advertising
Cloudflare	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
www.pixnoy.com	A	IPv4 address	172.67.71.150
www.pixnoy.com	A	IPv4 address	104.26.6.225
www.pixnoy.com	A	IPv4 address	104.26.7.225
www.pixnoy.com	AAAA	IPv6 address	2606:4700:20::ac43:4796
www.pixnoy.com	AAAA	IPv6 address	2606:4700:20::681a:6e1
www.pixnoy.com	AAAA	IPv6 address	2606:4700:20::681a:7e1
www.pixnoy.com	TXT	Text record	"yandex-verification: a1fb7825e642c56d"

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.