Vulnerability Scan Result

Target:

https://cfotech.co.uk/story/huawei-joins-itu-and-iaea-s-ai-for-good-5g-challenge

Scanned target: https://cfotech.co.uk/story/huawei-joins-itu-and-iaea-s-ai-for-good-5g-challenge

Submitted: Feb 16, 2026 from TN

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Huawei joins ITU and IAEA's AI for Good 5G Challenge
Description:	The 5G energy consumption modelling challenge, curated by Huawei, aims to develop machine learning models that reduce energy consumption.

IP Information

ip_address	210.48.126.143
country	NZ
network_name	ICONZ Ltd
asn	AS4770

Open Ports

22/tcp	ssh	OpenSSH 9.6p1 Ubuntu 3ubuntu13.14
80/tcp	http	nginx -
443/tcp	https	nginx -

Web Technologies

Software / Version	Category
Open Graph	Miscellaneous
Ruby	Programming languages
Ruby on Rails	Web frameworks
Priority Hints	Performance
HSTS	Security
RSS	Miscellaneous

Web Application Vulnerabilities

Evidence

URL	Evidence
https://cfotech.co.uk/story/huawei-joins-itu-and-iaea-s-ai-for-good-5g-challenge	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
https://cfotech.co.uk/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

Software / Version	Category
Open Graph	Miscellaneous
Ruby	Programming languages
Ruby on Rails	Web frameworks
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.

Infrastructure Vulnerabilities

Evidence

Domain Queried	DNS Record Type	Description	Value
_dmarc.cfotech.co.uk	TXT	Text record	"v=DMARC1; p=reject; rua=mailto:lnpzte07ih@rua.powerdmarc.com; ruf=mailto:lnpzte07ih@ruf.powerdmarc.com; fo=0:1:d:s;"

Vulnerability description

We found that the DMARC record for the domain is not configured with sp policy, meaning that no policy is enforced for subdomains. When a DMARC record does not include a subdomain policy (sp directive), subdomains are not explicitly covered by the main domain's DMARC policy. This means that emails sent from subdomains (e.g., sub.example.com) may not be subject to the same DMARC enforcement as the main domain (example.com). As a result, attackers could potentially spoof emails from subdomains without being blocked or flagged, even if the main domain has a strict DMARC policy.

Risk description

Without a subdomain policy (sp directive) in the DMARC record, subdomains are not protected by the same DMARC enforcement as the main domain, leaving them vulnerable to spoofing attacks. This inconsistency can be exploited by attackers to send phishing emails from subdomains, undermining the organization’s overall email security.

Recommendation

To mitigate the risk, we recommend configuring the DMARC record with a subdomain policy by adding the sp=reject or sp=quarantine directive. This will extend DMARC enforcement to all subdomains, preventing spoofing attempts and maintaining consistent security across both the main domain and its subdomains.

Evidence

Software / Version	Category
Ruby	Programming languages
Ruby on Rails	Web frameworks
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.

Domain Queried	DNS Record Type	Description	Value
cfotech.co.uk	SPF	Sender Policy Framework	"v=spf1 a mx include:_spf.google.com include:sendgrid.net -all"

Operating System	Accuracy
Linux 4.15 - 5.6	93%

Evidence

Domain Queried	DNS Record Type	Description	Value
cfotech.co.uk	A	IPv4 address	210.48.126.143
cfotech.co.uk	NS	Name server	ns1.linode.com
cfotech.co.uk	NS	Name server	ns4.linode.com
cfotech.co.uk	NS	Name server	ns5.linode.com
cfotech.co.uk	NS	Name server	ns2.linode.com
cfotech.co.uk	NS	Name server	ns3.linode.com
cfotech.co.uk	MX	Mail server	10 ALT4.ASPMX.L.GOOGLE.COM
cfotech.co.uk	MX	Mail server	10 ALT3.ASPMX.L.GOOGLE.COM
cfotech.co.uk	MX	Mail server	5 ALT2.ASPMX.L.GOOGLE.COM
cfotech.co.uk	MX	Mail server	5 ALT1.ASPMX.L.GOOGLE.COM
cfotech.co.uk	MX	Mail server	1 ASPMX.L.GOOGLE.COM
cfotech.co.uk	SOA	Start of Authority	ns1.linode.com. seanm.techday.com. 2021000013 14400 14400 1209600 86400
cfotech.co.uk	TXT	Text record	"google-site-verification=RjFSQtnpl3sy1e-G5tsd-K5AYyXQqxMo1hUWcqc8Dxw"
cfotech.co.uk	SPF	Sender Policy Framework	"v=spf1 a mx include:_spf.google.com include:sendgrid.net -all"
cfotech.co.uk	CAA	Certificate Authority Authorization	0 issue "letsencrypt.org"
_dmarc.cfotech.co.uk	TXT	Text record	"v=DMARC1; p=reject; rua=mailto:lnpzte07ih@rua.powerdmarc.com; ruf=mailto:lnpzte07ih@ruf.powerdmarc.com; fo=0:1:d:s;"

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
Ruby	Programming languages
Ruby on Rails	Web frameworks
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

DKIM selector	Key type	Key size	Value
s2	rsa	1296	"k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDozoRemjoiJsmBrhFFAyKu9/D3M5RYE0wknTCmnre4NCmUDc53L7JtTKxmBNhAdaTSco2/nojpfM9qbbQdu26FINuaNdmUCthOz7oo7tK5LR8DL01yL1UqEyBs44R4156kcwidzpT+pPPjz7ZBeC5ph0EZscChPGVHzowineEGAwIDAQAB"
s1	rsa	1446	"k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAq/nCGhK3/8y9/krs/EpxKGbMCMMmlL9ftBqrNCnlDxBsmvrdUPyQRF0kpp3GC43f5e3UsCdebCAfKL4CMvGCZoKtBuCuD0TEbL8AAiR2KRAFjx9nzcdzEqGT5jeR00OgcgaIT3Q0qWLW6GAXpZrtHrGKlrsU+6zkw2oTKdlPMHlae8jfrZ7EHttKg8qOZ1QMj44K7" "vhXlaDptkT87kaTRji9zo1/e8xHMqIPGwfWl6mRJYepPoA35TNr0+LWiTEvCH7+fRHRDK+2fzEd1tBcA4sdvx3CTIVyr5flz5yf4IK9F1M9druxsnKFKm7428Vrygn90XcFRlGpD93HdIIElwIDAQAB"