Vulnerability Scan Result

Target:

https://serviceagent.dev/ (redirect)

Scanned target: https://www.serviceagent.dev/

Submitted: Jun 18, 2026 from UY

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	ServiceAgent \| Transform your business into an AI-powered machine
Description:	Transform your business into an AI-powered machine. We find where AI saves you money and build custom systems into your workflows, live in 6 weeks. You own everything.

IP Information

ip_address	216.150.1.1
country	US
network_name	Amazon.com, Inc.
asn	AS16509

ip_address	216.150.16.1
country	US
network_name	Amazon.com, Inc.
asn	AS16509

Open Ports

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

Web Technologies

Software / Version	Category
Facebook Pixel 2.9.347	Analytics
Google Analytics GA4	Analytics
MySQL	Databases
Open Graph	Miscellaneous
PHP	Programming languages
DoubleClick Floodlight	Advertising
Vercel	PaaS
WordPress	CMS, Blogs
Google Tag Manager	Tag managers
HSTS	Security

Web Application Vulnerabilities

Evidence

Software / Version	Category
Facebook Pixel 2.9.347	Analytics
Google Analytics GA4	Analytics
MySQL	Databases
Open Graph	Miscellaneous
PHP	Programming languages
DoubleClick Floodlight	Advertising
Vercel	PaaS
WordPress	CMS, Blogs
Google Tag Manager	Tag managers
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.

Classification

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

Evidence

URL
https://www.serviceagent.dev/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	Evidence
https://www.serviceagent.dev/	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

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

Evidence

URL	Method	Parameters	Evidence
https://www.serviceagent.dev/	GET	Headers: User-Agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36	Email Address: p@serviceagent.dev

Vulnerability description

We noticed that this web application exposes email addresses, which might be unintended. While not inherently a vulnerability, this information could be leveraged in social engineering or spam related activities.

Risk description

The risk is that exposed email addresses within the application could be accessed by unauthorized parties. This could lead to privacy violations, spam, phishing attacks, or other forms of misuse.

Recommendation

Compartmentalize the application to have 'safe' areas where trust boundaries can be unambiguously drawn. Do not allow email addresses to go outside of the trust boundary, and always be careful when interfacing with a compartment outside of the safe area.

Classification

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

Infrastructure Vulnerabilities

Evidence

Software / Version	Category
WordPress	CMS, Blogs
MySQL	Databases
PHP	Programming languages
Vercel	PaaS
Google Tag Manager	Tag managers
Facebook Pixel 2.9.347	Analytics
core-js 3.32.2	JavaScript libraries
Google Analytics GA4	Analytics
DoubleClick Floodlight	Advertising
HSTS	Security
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.

Evidence

Domain Queried	DNS Record Type	Description	Value
www.serviceagent.dev	A	IPv4 address	216.150.1.193
www.serviceagent.dev	A	IPv4 address	216.150.16.193
www.serviceagent.dev	CAA	Certificate Authority Authorization	0 issue "globalsign.com"
www.serviceagent.dev	CAA	Certificate Authority Authorization	0 issue "letsencrypt.org"
www.serviceagent.dev	CAA	Certificate Authority Authorization	0 issue "pki.goog"
www.serviceagent.dev	CAA	Certificate Authority Authorization	0 issue "sectigo.com"
www.serviceagent.dev	CNAME	Canonical name	e526e6234a37ddcc.vercel-dns-016.com

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.