Vulnerability Scan Result

Target:

https://galp.com/ (redirect)

Scanned target: https://www.galp.com/pt/

Submitted: Mar 23, 2026 from SM

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Galp Estrada, Casa e Empresas - Conheça a nossa Oferta \| Galp
Description:	A Galp está perto de si sempre que precisa. Conheça a oferta de combustível, gás natural e eletricidade verde na estrada, casa e empresas.

IP Information

ip_address	2.23.6.22
country	DE
network_name	Akamai International B.V.
asn	AS20940

ip_address	2.23.6.26
country	DE
network_name	Akamai International B.V.
asn	AS20940

Open Ports

80/tcp	http	AkamaiGHost -
443/tcp	https	- -

Web Technologies

Software / Version	Category
HTTP/3	Miscellaneous
DigiCert	SSL/TLS certificate authorities

Web Application Vulnerabilities

Evidence

Software / Version	Category
HTTP/3	Miscellaneous
DigiCert	SSL/TLS certificate authorities

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

Domain Queried	DNS Record Type	Description	Value
www.galp.com	A	IPv4 address	23.38.98.73
www.galp.com	A	IPv4 address	23.38.98.123
www.galp.com	CNAME	Canonical name	galp.com.edgekey.net

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
Google Maps	Maps
Microsoft ASP.NET	Web frameworks
OneTrust	Cookie compliance
jsDelivr	CDN
Google Tag Manager	Tag managers
HSTS	Security
DigiCert	SSL/TLS certificate authorities
HTTP/3	Miscellaneous
Font Awesome 4.6.3	Font scripts
AOS	JavaScript libraries
Open Graph	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.