Vulnerability Scan Result

Target:

https://fifa-wc2026schedule.com.cn/

Scanned target: https://fifa-wc2026schedule.com.cn/

Submitted: Jun 09, 2026 from SC

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	2026ä¸çæ¯(World Cup)æå®å¨åæ³çä½è²ä¹°çå¹³å°æ¨è
Description:	2026ä¸çæ¯æå®å¨åæ³çä½è²ä¹°çå¹³å°æ¨èãä¸ºæ¨ä¸¥æ ¼çéåºæ¥æå®æ¹ææãå£ç¢æä½³çæ£è§ææ³¨å®ç½ãèµéå å¯ææ¯ä¿éè´¦æ·å®å¨ï¼åå«éé¸¡é»ç½ï¼è®¤åå¤§å¹³å°ï¼çäº«å¨çè¶³ççå®´ã

IP Information

ip_address	179.199.226.164
country	BR
network_name	-
asn	-

Open Ports

80/tcp	http	nginx -
443/tcp	https	nginx -

Web Technologies

Software / Version	Category
Font Awesome	Font scripts
Bootstrap	UI frameworks
HTTP/3	Miscellaneous
Bootstrap Icons .	Font scripts
Nginx	Web servers, Reverse proxies
Open Graph	Miscellaneous
Priority Hints	Performance
HSTS	Security
RSS	Miscellaneous

Web Application Vulnerabilities

Evidence

URL	Evidence
https://fifa-wc2026schedule.com.cn/	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
Font Awesome	Font scripts
Bootstrap	UI frameworks
HTTP/3	Miscellaneous
Bootstrap Icons .	Font scripts
Nginx	Web servers, Reverse proxies
Open Graph	Miscellaneous
Priority Hints	Performance
HSTS	Security
RSS	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.

Classification

CWE	CWE-200
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Evidence
https://fifa-wc2026schedule.com.cn/uploads	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
https://fifa-wc2026schedule.com.cn/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://fifa-wc2026schedule.com.cn/.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

Domain Queried	DNS Record Type	Description	Value
fifa-wc2026schedule.com.cn	A	IPv4 address	179.199.226.164
fifa-wc2026schedule.com.cn	NS	Name server	ns1.myhostadmin.net
fifa-wc2026schedule.com.cn	NS	Name server	ns2.myhostadmin.net
fifa-wc2026schedule.com.cn	SOA	Start of Authority	ns1.myhostadmin.net. dnsconct.myhostadmin.net. 2026060902 43200 300 1209600 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
Bootstrap	UI frameworks
Nginx	Web servers, Reverse proxies
Priority Hints	Performance
Font Awesome	Font scripts
Bootstrap Icons .	Font scripts
HSTS	Security
RSS	Miscellaneous
Open Graph	Miscellaneous
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.