Vulnerability Scan Result

Target:

https://you.com/ (redirect)

Scanned target: https://you.com/home

Submitted: Dec 04, 2025 from FM

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	You.com \| AI Search Infrastructure for Enterprise Teams
Description:	Skip the groundwork with our AI-ready API platform and ultra-specific vertical indexes, delivering advanced search capabilities to power your next product.

IP Information

ip_address	172.64.146.80
country	-
network_name	Cloudflare Inc
asn	AS13335

ip_address	104.18.41.176
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	http	cloudflare -

Web Technologies

Software / Version	Category
Cloudflare	CDN
Cloudflare Bot Management	Security
HSTS	Security

Web Application Vulnerabilities

Evidence

URL	Evidence
https://you.com/home	Response headers do not include the Referrer-Policy HTTP security header as well as the `<meta/>` tag with name 'referrer' is not present in the response.

Vulnerability description

We noticed that the target application's server responses lack the Referrer-Policy HTTP header, which controls how much referrer information the browser will send with each request originated from the current web application.

Risk description

The risk is that if a user visits a web page (e.g. "http://example.com/pricing/") and clicks on a link from that page going to e.g. "https://www.google.com", the browser will send to Google the full originating URL in the `Referer` header, assuming the Referrer-Policy header is not set. The originating URL could be considered sensitive information and it could be used for user tracking.

Recommendation

The Referrer-Policy header should be configured on the server side to avoid user tracking and inadvertent information leakage. The value `no-referrer` of this header instructs the browser to omit the Referer header entirely.

Classification

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

Evidence

Software / Version	Category
Cloudflare	CDN
Cloudflare Bot Management	Security
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

URL
https://you.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	Evidence
https://you.com/home	Response headers do not include the X-Content-Type-Options HTTP security header

Vulnerability description

We noticed that the target application's server responses lack the X-Content-Type-Options header. This header is particularly important for preventing Internet Explorer from reinterpreting the content of a web page (MIME-sniffing) and thus overriding the value of the Content-Type header.

Risk description

The risk is that lack of this header could make possible attacks such as Cross-Site Scripting or phishing in Internet Explorer browsers.

Recommendation

We recommend setting the X-Content-Type-Options header such as `X-Content-Type-Options: nosniff`.

Classification

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

Evidence

URL Evidence

URL	Evidence
https://you.com/home	Response headers include the HTTP Content-Security-Policy security header with the following security issues:`base-uri: Missing base-uri allows the injection of base tags. They can be used to set the base URL for all relative (script) URLs to an attacker controlled domain. We recommend setting it to 'none' or 'self'. script-src: script-src directive is missing. object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified.`

https://you.com/home

Response headers include the HTTP Content-Security-Policy security header with the following security issues:base-uri: Missing base-uri allows the injection of base tags. They can be used to set the base URL for all relative (script) URLs to an attacker controlled domain. We recommend setting it to 'none' or 'self'. script-src: script-src directive is missing. object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified.

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-693
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

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

Infrastructure Vulnerabilities

Evidence

Domain Queried	DNS Record Type	Description	Value
_dmarc.you.com	TXT	Text record	"v=DMARC1; p=quarantine; rua=mailto:dmarc@you.com; pct=100; adkim=r; aspf=r;"

Vulnerability description

We found that the target uses p=quarantine in the DMARC policy. When a DMARC policy is set to p=quarantine, emails that fail DMARC validation are delivered but placed in the recipient’s spam or junk folder. Although it offers some protection, this policy is less strict than p=reject, which blocks such emails entirely.

Risk description

While emails failing DMARC validation are sent to the spam folder, users may still retrieve them from there, leading to a higher risk of phishing and spoofing attacks succeeding. Moreover, less strict enforcement may allow more fraudulent emails to reach user inboxes if misclassified.

Recommendation

We recommend considering moving to a stricter policy, such as p=reject, where emails that fail DMARC validation are completely rejected rather than delivered to spam folders. This reduces the risk of users interacting with potentially malicious emails.

Evidence

Domain Queried	DNS Record Type	Description	Value
_dmarc.you.com	TXT	Text record	"v=DMARC1; p=quarantine; rua=mailto:dmarc@you.com; pct=100; adkim=r; aspf=r;"

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

Domain Queried	DNS Record Type	Description	Value
_dmarc.you.com	TXT	Text record	"v=DMARC1; p=quarantine; rua=mailto:dmarc@you.com; pct=100; adkim=r; aspf=r;"

Vulnerability description

We found that the DMARC record for the domain is not configured with ruf tag. A missing ruf (forensic reporting) tag in a DMARC record indicates that the domain owner has not enabled the collection of detailed failure reports. Forensic reports provide valuable insights into specific instances where emails fail DMARC authentication. Without the ruf tag, the domain administrator loses the ability to receive and analyze these reports, making it difficult to investigate individual email failures or identify targeted phishing or spoofing attacks that may be exploiting weaknesses in the email authentication setup.

Risk description

Without forensic reports (ruf), domain owners have limited visibility into the specifics of failed DMARC validation. This means potential malicious activity, such as email spoofing or phishing attempts, might go unnoticed until they result in more significant security breaches or reputational damage. Forensic reports allow for quick response to email abuses by providing detailed information about the failure, including the header information of the emails involved. The absence of this data hampers an organization's ability to identify and mitigate threats targeting its domain, increasing the risk of ongoing spoofing and fraud.

Recommendation

We recommend configuring the ruf tag in the DMARC record. This tag specifies where forensic reports should be sent, providing the domain owner with detailed data on DMARC validation failures. Forensic reports allow administrators to analyze why certain emails failed authentication, making it easier to fine-tune DMARC policies or address potential vulnerabilities. Ensure that the ruf email address belongs to a secure and trusted location capable of handling sensitive email data.

Operating System	Accuracy
Crestron XPanel control system	91%

Evidence

Software / Version	Category
HSTS	Security
Cloudflare	CDN

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
k3	rsa	1422	"v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsYGiMSn7fsUqSvfSX40x9R1OlRtbNiCY80lHRIlcKx3XDIR7257aUx+q9CSIARdfTL6KCuLGNFx5g9TgVr6png4ajcieSQGtOehBgxnkDN8aAA5TX0FmFrcefJU0JoxLOF09EKgXxhSSHCk/ekVb0PXSboHXoZ9+EI404F1qhcwXXIgHXTaUthHTut2P6BBZh" "IXIgvDe/w49GchR7MRJqjNb7neEBbYHbgWuBTvvHCg7Gy6m6n9krYK+ROWq3dVvXy9plAGK3ygM+HtjIiMt7arRGMOF0WgDTz7YdN9BGpt6BvXxLnjiQcgS5T9n+cIyPZgiWzDMXNlaEEdKTEKxrwIDAQAB;"
k2	rsa	1422	"v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAv2aC2KjGKLOwTweBY5A9RpjsxaBXR9r7OAU6U8/zn92ivImI75naUujWbItRI/QmL1jy5PWGqLwoUA0b90ObWaLDc+i9MtTNmGeWO009hr20fIxhGg6XBT2kjZ1DTThopSe1nAndsupmcBwlQ5Q6LJ+ZAxLcujnPIxM0ZBLmgpkv8u6RfY4eFP8OLvdAW3oSu" "B0DyLDigQX4Sj8wBO4YIdQH6AAmBeOsidsKAFNFUCpc3vCxtBDR12U+cBg724l3sBkMQ8evnz6idnqxq9QAVYh8k4kJ+RP+6cqTdy7LjIm8xY/bQNpQIpGUAuDo2DjLcCDun9DAI4Q/3z+Q0o9QuQIDAQAB;"
s1	rsa	1446	"k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAw+YVljQJ9F3hOHC2YonhWz4hxPH/eYu2tAlvyRZ+j+EGwsgMBjzT3JWxQf5CDIYL11/81DEAck0ihxSUo+O4I7b6BHSV5nydax3I4/vvcew2g57aEC/SdHSgB2jP7kde1GRi+nHU/a+WrPuHulYJBJAIVtjwgvMSYyGcYvYkhttzbGh7cds8R2e7J5PMR6pbJZXPg" "ueCLy0YdBQI1k/H/ooA+T6MfiEwsWET109zzFlv9AZsHgVk5FTU7LopRdsf1M8r05A6nIX/1nUIypLQGlaFQ4X8C+Dmocl6MPvgNsjZOSHBAgqWGRA6t6ezPqmCq1wHCzpS78L5fun3ey7eEwIDAQAB"
s2	rsa	1296	"k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDAfkw+8UIiiAZHD4v2XlE2H6IlBZmI1S93HnVnNNQuqpY0/OvrM6pMlsCy8cACYkjsmr7tx49CyB7AGVxdY5TQ5J7iRIzTJ+DyQ029d2dumAyGJz/rMrOxZqf88Y2qmvTyBgp22qnsc0RAXgsmQpOyOFa7Ir6gOuP8eGYyhsx9owIDAQAB"

Evidence

Software / Version	Category
Next.js	JavaScript frameworks, Web frameworks, Web servers, Static site generator
Canny	Issue trackers
React	JavaScript frameworks
Osano	Cookie compliance
Cloudflare Bot Management	Security
LaunchDarkly	Feature management
HSTS	Security
Cloudflare	CDN
Webpack	Miscellaneous
lit-html 2.7.5	JavaScript libraries
Priority Hints	Performance
Lucide	Font scripts

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
you.com	A	IPv4 address	104.18.41.176
you.com	A	IPv4 address	172.64.146.80
you.com	NS	Name server	kevin.ns.cloudflare.com
you.com	NS	Name server	riya.ns.cloudflare.com
you.com	MX	Mail server	1 aspmx.l.google.com
you.com	MX	Mail server	10 alt3.aspmx.l.google.com
you.com	MX	Mail server	10 alt4.aspmx.l.google.com
you.com	MX	Mail server	5 alt1.aspmx.l.google.com
you.com	MX	Mail server	5 alt2.aspmx.l.google.com
you.com	SOA	Start of Authority	kevin.ns.cloudflare.com. dns.cloudflare.com. 2390105645 10000 2400 604800 1800
you.com	AAAA	IPv6 address	2606:4700:4401::6812:29b0
you.com	AAAA	IPv6 address	2606:4700:4408::ac40:9250
you.com	TXT	Text record	"8513851"
you.com	TXT	Text record	"PDlKdlfKr7HQoREGlNDxjkCSbJeZ"
you.com	TXT	Text record	"ZOOM_verify_u04v3YAjTxOtOJeGkKPMxg"
you.com	TXT	Text record	"anthropic-domain-verification-pjq786=3w66qu2zmTOPJz2KCgVVjsAsF"
you.com	TXT	Text record	"apple-domain-verification=gAQVl1LckgUVG1R0"
you.com	TXT	Text record	"confluent-verification=931a7299-7441-4329-b9de-f3e79b519e1e"
you.com	TXT	Text record	"cursor-domain-verification-7d6p1a=Z2WbQf5jYSenTAGAgEj1dT9vI"
you.com	TXT	Text record	"google-site-verification=6vfWcsSRYPaltK0JXWzqkPoY0PzLmnmxLD0LO48WzZc"
you.com	TXT	Text record	"google-site-verification=CRtDXRD-zfOkj7Wvo_IujrR7JM-dF1_XxzVjWxiNL1k"
you.com	TXT	Text record	"google-site-verification=NLJDpeYSfrQYfU-kfIx1oaECx3xn9yR5LQkVru5MSes"
you.com	TXT	Text record	"google-site-verification=bg4oN6_XAnEMXZ2PLsiBtJGz2_ydpphhAuIxgGgzRBE"
you.com	TXT	Text record	"launchdarkly-domain-verification=8cd8651a-1419-4231-9b09-dbd0550cc782"
you.com	TXT	Text record	"loaderio=48ce53b50995f7ae441aa14be69ac0ae"
you.com	TXT	Text record	"notion-domain-verification=heenitD9shmBmUmYHsFhHIwAqgL8NlRiayzcFw4L7r7"
you.com	TXT	Text record	"openai-domain-verification=dv-vJN0jvvR2NGjdL0CKZqhCaeb"
you.com	TXT	Text record	"stripe-verification=f7098d08261bc170d8559fe4ea918954c5e3579aa1e7f4fc7f599f06e5a0c153"
you.com	TXT	Text record	"stytch_verification_dns=flying-humidity-4672"
you.com	TXT	Text record	"zapier-domain-verification-challenge=391b45f2-2425-40d5-a208-43cd6def6a44"
you.com	SPF	Sender Policy Framework	"v=spf1 include:_spf.google.com include:amazonses.com include:45321510.spf02.hubspotemail.net include:_spf.sparkpostmail.com -all"
you.com	CAA	Certificate Authority Authorization	0 issue "amazon.com"
you.com	CAA	Certificate Authority Authorization	0 issue "amazonaws.com"
you.com	CAA	Certificate Authority Authorization	0 issue "amazontrust.com"
you.com	CAA	Certificate Authority Authorization	0 issue "awstrust.com"
you.com	CAA	Certificate Authority Authorization	0 issue "comodoca.com"
you.com	CAA	Certificate Authority Authorization	0 issue "digicert.com; cansignhttpexchanges=yes"
you.com	CAA	Certificate Authority Authorization	0 issue "letsencrypt.org"
you.com	CAA	Certificate Authority Authorization	0 issue "pki.goog; cansignhttpexchanges=yes"
you.com	CAA	Certificate Authority Authorization	0 issue "ssl.com"
you.com	CAA	Certificate Authority Authorization	0 issuewild "comodoca.com"
you.com	CAA	Certificate Authority Authorization	0 issuewild "digicert.com; cansignhttpexchanges=yes"
you.com	CAA	Certificate Authority Authorization	0 issuewild "letsencrypt.org"
you.com	CAA	Certificate Authority Authorization	0 issuewild "pki.goog; cansignhttpexchanges=yes"
you.com	CAA	Certificate Authority Authorization	0 issuewild "ssl.com"
_dmarc.you.com	TXT	Text record	"v=DMARC1; p=quarantine; rua=mailto:dmarc@you.com; pct=100; adkim=r; aspf=r;"

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

Domain Queried	DNS Record Type	Description	Value
you.com	SPF	Sender Policy Framework	"v=spf1 include:_spf.google.com include:amazonses.com include:45321510.spf02.hubspotemail.net include:_spf.sparkpostmail.com -all"