Vulnerability Scan Result

Target:

http://rediads.com/ (redirect)

Scanned target: https://rediads.com/

Submitted: Jun 17, 2026 from MU

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	RediAds \| AI-Powered Publisher Monetization Platform
Description:	RediAds helps publishers and advertisers grow revenue with AI-powered monetization, Prebid, OpenRTB, identity, IVT, rich media, and curation solutions.

IP Information

ip_address	172.67.70.14
country	-
network_name	Cloudflare, Inc.
asn	AS13335

ip_address	104.26.15.59
country	-
network_name	Cloudflare, Inc.
asn	AS13335

ip_address	104.26.14.59
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	https-alt	cloudflare -

Web Technologies

Software / Version	Category
Google Font API	Font scripts
Google Analytics GA4	Analytics
HTTP/3	Miscellaneous
MySQL	Databases
Next.js 16.2.1	JavaScript frameworks, Web frameworks, Web servers, Static site generator
Next.js App Router	JavaScript frameworks, Web servers
Turbopack	Development
Open Graph	Miscellaneous
PHP	Programming languages
React	JavaScript frameworks
DoubleClick Floodlight	Advertising
Webpack	Miscellaneous
Priority Hints	Performance
WordPress	CMS, Blogs
Cloudflare	CDN
Cloudflare Bot Management	Security
Google Tag Manager	Tag managers

Web Application Vulnerabilities

Evidence

URL	Evidence
https://rediads.com/	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	Evidence
https://rediads.com/	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

URL	Evidence
https://rediads.com/	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	Evidence
https://rediads.com/	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	Method	Parameters	Evidence
https://rediads.com/login	GET	Query: callbackUrl=/dashboard 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 Cookies: __cf_bm=YJqa7PKJjHp7CI8dIAJTR1f_RBUrfVvP6CmlIE8Cams-1782773374.340324-1.0.1.1-dTyzkYCP4_jVE2rKRppKG3dbakW...	The following form sends inputs of type password plainly in the URL: ` Work email PasswordForgot password? </d... (truncated)

Vulnerability description

We found a form which is submitted using a GET method and has inputs of the type password. The end result is that passwords are submitted in URLs.

Risk description

Passwords submitted in URLs have a higher chance of being leaked. The main reason is that URLs can be leaked in browser cross-site requests via the Referer header. Additionally, URLs are usually stored in all kinds of logs. If any access or error logs of the server were publicly accessible, an attacker could also harvest password from it.

Recommendation

You should submit passwords using POST rather than GET. This way sensitive data won't be shared to other locations via URLs.

Classification

CWE	CWE-598
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

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

Software / Version	Category
Google Font API	Font scripts
Google Analytics GA4	Analytics
HTTP/3	Miscellaneous
MySQL	Databases
Next.js 16.2.1	JavaScript frameworks, Web frameworks, Web servers, Static site generator
Next.js App Router	JavaScript frameworks, Web servers
Turbopack	Development
Open Graph	Miscellaneous
PHP	Programming languages
React	JavaScript frameworks
DoubleClick Floodlight	Advertising
Webpack	Miscellaneous
Priority Hints	Performance
WordPress	CMS, Blogs
Cloudflare	CDN
Cloudflare Bot Management	Security
Google Tag Manager	Tag managers

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://rediads.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

Evidence

URL	Method	Summary
https://rediads.com/	OPTIONS	We did a HTTP OPTIONS request. The server responded with a 405 status code and the header: `Allow: GET, HEAD` Request / Response

Vulnerability description

We have noticed that the webserver responded with an Allow HTTP header when an OPTIONS HTTP request was sent. This method responds to requests by providing information about the methods available for the target resource.

Risk description

The only risk this might present nowadays is revealing debug HTTP methods that can be used on the server. This can present a danger if any of those methods can lead to sensitive information, like authentication information, secret keys.

Recommendation

We recommend that you check for unused HTTP methods or even better, disable the OPTIONS method. This can be done using your webserver configuration.

Classification

CWE	CWE-16
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL Evidence

URL	Evidence
https://rediads.com/login	<input id="login-email" type="email" autocomplete="email" placeholder="you@company.com" class="w-full rounded-xl border border-border bg-card-elevated px-4 py-3 text-sm text-foreground placeholder:text-text-caption outline-none transition-all duration-200 focus:border-[#FF7A1A]/55 focus:ring-2 focus:ring-[#FF7A1A]/25" name="email" value=""> <input id="login-password" type="password" autocomplete="current-password" class="w-full rounded-xl border border-border bg-card-elevated pl-4 pr-12 py-3 text-sm text-foreground outline-none transition-all duration-200 focus:border-[#FF7A1A]/55 focus:ring-2 focus:ring-[#FF7A1A]/25" name="password" value=""> <button type="submit" class="w-full rounded-xl py-3.5 text-sm font-bold font-headline text-white transition-all duration-200 hover:brightness-110 active:scale-[0.99] disabled:opacity-50 disabled:pointer-events-none shadow-[0_8px_24px_-4px_rgba(255,122,26,0.45)]" style="background-color:#FF7A1A">Sign in</button>

https://rediads.com/login

Vulnerability description

We have discovered that the target application presents a login interface that could be a potential target for attacks. While login interfaces are standard for user authentication, they can become vulnerabilities if not properly secured.

Risk description

The risk is that an attacker could use this interface to mount brute force attacks against known passwords and usernames combinations leaked throughout the web.

Recommendation

Ensure each interface is not bypassable using common knowledge of the application or leaked credentials using occasional password audits.

Classification

CWE	CWE-287
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Method	Parameters	Evidence
https://rediads.com/	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: support@rediads.com

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
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.

Operating System	Accuracy
FreeBSD 11.0-RELEASE	91%

Evidence

Software / Version	Category
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

Software / Version	Category
WordPress	CMS, Blogs
Next.js 16.2.1	JavaScript frameworks, Web frameworks, Web servers, Static site generator
Turbopack	Development
MySQL	Databases
PHP	Programming languages
React	JavaScript frameworks
Next.js App Router	JavaScript frameworks, Web servers
Cloudflare Bot Management	Security
Google Tag Manager	Tag managers
Google Analytics GA4	Analytics
Priority Hints	Performance
Google Font API	Font scripts
DoubleClick Floodlight	Advertising
Cloudflare	CDN
Webpack	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.

Evidence

Domain Queried	DNS Record Type	Description	Value
rediads.com	A	IPv4 address	104.26.15.59
rediads.com	A	IPv4 address	172.67.70.14
rediads.com	A	IPv4 address	104.26.14.59
rediads.com	NS	Name server	kim.ns.cloudflare.com
rediads.com	NS	Name server	phil.ns.cloudflare.com
rediads.com	MX	Mail server	1 aspmx.l.google.com
rediads.com	MX	Mail server	10 alt3.aspmx.l.google.com
rediads.com	MX	Mail server	10 alt4.aspmx.l.google.com
rediads.com	MX	Mail server	5 alt1.aspmx.l.google.com
rediads.com	MX	Mail server	5 alt2.aspmx.l.google.com
rediads.com	SOA	Start of Authority	kim.ns.cloudflare.com. dns.cloudflare.com. 2405100612 10000 2400 604800 1800
rediads.com	AAAA	IPv6 address	2606:4700:20::681a:e3b
rediads.com	AAAA	IPv6 address	2606:4700:20::681a:f3b
rediads.com	AAAA	IPv6 address	2606:4700:20::ac43:460e
rediads.com	TXT	Text record	"google-site-verification=pUI00BQmPL8imB_nXCIGRHGYP3d1M1K6gw1yI2H4nhE"
rediads.com	TXT	Text record	"sjyp2mmkdk"

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
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.