Vulnerability Scan Result

Target:

http://totallyimmersed.com.au/ (redirect)

Scanned target: https://totallyimmersed.com.au/

Submitted: Jun 09, 2026 from TD

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Totally Immersed Watersports - A Premium Hobie Dealer
Description:	We stock the entire range of Hobie kayak & sailboat products plus a great selection of associated water sports accessories, fishing tackle, roof rack & storage solutions, stand up paddle boards, life jackets (PFDs), water wear, apparel and polarised sunglasses. Open 5 days - Monday to Friday.

IP Information

ip_address	104.21.84.133
country	-
network_name	Cloudflare, Inc.
asn	AS13335

ip_address	172.67.193.84
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
Facebook Pixel 2.9.338	Analytics
LazySizes	JavaScript libraries, Performance
core-js 2.6.12	JavaScript libraries
Google Analytics	Analytics
HTTP/3	Miscellaneous
jQuery 3.4.1	JavaScript libraries
MailChimp	Marketing automation, Email
MySQL	Databases
Open Graph	Miscellaneous
Google Pay	Payment processors
PayPal	Payment processors
PHP	Programming languages
Shop Pay	Payment processors
Shopify	Ecommerce
DoubleClick Floodlight	Advertising
Priority Hints	Performance
WordPress	CMS, Blogs
Apple Pay	Payment processors
Cloudflare	CDN
Google Tag Manager	Tag managers
Mastercard	Payment processors
HSTS	Security
Visa	Payment processors
Cart Functionality	Ecommerce

Web Application Vulnerabilities

Evidence

URL	Cookie Name	Evidence
https://totallyimmersed.com.au/	localization, cart_currency, _shopify_y, _shopify_s	The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: localization=AU Set-Cookie: cart_currency=AUD Set-Cookie: _shopify_y=c4c3eec7-95bf-40ee-ada9-1cf6338641d5 Set-Cookie: _shopify_s=8a9ef471-9a10-4628-b7c7-60012c349fb3

Vulnerability description

We found that a cookie has been set without the HttpOnly flag, which means it can be accessed by potentially malicious JavaScript code running inside the web page. The root cause for this usually revolves around misconfigurations in the code or server settings.

Risk description

The risk is that an attacker who injects malicious JavaScript code on the page (e.g. by using an XSS attack) can access the cookie and can send it to another site. In case of a session cookie, this could lead to session hijacking.

Recommendation

Ensure that the HttpOnly flag is set for all cookies.

Classification

CWE	CWE-1004
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Cookie Name	Evidence
https://totallyimmersed.com.au/	localization, cart_currency, _shopify_y, _shopify_s	Set-Cookie: localization=AU Set-Cookie: cart_currency=AUD Set-Cookie: _shopify_y=c4c3eec7-95bf-40ee-ada9-1cf6338641d5 Set-Cookie: _shopify_s=8a9ef471-9a10-4628-b7c7-60012c349fb3

Vulnerability description

We found that a cookie has been set without the Secure flag, which means the browser will send it over an unencrypted channel (plain HTTP) if such a request is made. The root cause for this usually revolves around misconfigurations in the code or server settings.

Risk description

The risk exists that an attacker will intercept the clear-text communication between the browser and the server and he will steal the cookie of the user. If this is a session cookie, the attacker could gain unauthorized access to the victim's web session.

Recommendation

Whenever a cookie contains sensitive information or is a session token, then it should always be passed using an encrypted channel. Ensure that the secure flag is set for cookies containing such sensitive information.

Classification

CWE	CWE-614
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

CVE	CVSS	EPSS Score	EPSS Percentile	Summary
CVE-2020-11023	6.9	0.8383	0.99657	In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.
CVE-2020-11022	6.9	0.99019	0.99925	In jQuery starting with 1.12.0 and before 3.5.0, passing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.

Vulnerability description

Outdated or vulnerable software components include versions of server-side software that are no longer supported or have known, publicly disclosed vulnerabilities. Using outdated software significantly increases the attack surface of a system and may allow unauthorized access, data leaks, or service disruptions. Vulnerabilities in these components are often well-documented and actively exploited by attackers. Without security patches or vendor support, any weaknesses remain unmitigated, exposing the application to risks. In some cases, even after patching, the reported version may remain unchanged, requiring manual verification.

Risk description

The risk is that an attacker could search for an appropriate exploit (or create one himself) for any of these vulnerabilities and use it to attack the system. Since the vulnerabilities were discovered using only version-based testing, the risk level for this finding will not exceed 'high' severity. Critical risks will be assigned to vulnerabilities identified through accurate active testing methods.

Recommendation

In order to eliminate the risk of these vulnerabilities, we recommend you check the installed software version and upgrade to the latest version.

Classification

CWE	CWE-1035
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

Software / Version	Category
Facebook Pixel 2.9.338	Analytics
LazySizes	JavaScript libraries, Performance
core-js 2.6.12	JavaScript libraries
Google Analytics	Analytics
HTTP/3	Miscellaneous
jQuery 3.4.1	JavaScript libraries
MailChimp	Marketing automation, Email
MySQL	Databases
Open Graph	Miscellaneous
Google Pay	Payment processors
PayPal	Payment processors
PHP	Programming languages
Shop Pay	Payment processors
Shopify	Ecommerce
DoubleClick Floodlight	Advertising
Priority Hints	Performance
WordPress	CMS, Blogs
Apple Pay	Payment processors
Cloudflare	CDN
Google Tag Manager	Tag managers
Mastercard	Payment processors
HSTS	Security
Visa	Payment processors
Cart Functionality	Ecommerce

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	Evidence
https://totallyimmersed.com.au/	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
https://totallyimmersed.com.au/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

URL	Evidence
https://totallyimmersed.com.au/	Response headers include the HTTP Content-Security-Policy security header with the following security issues:`object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'. script-src: script-src directive is missing. 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'. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified.`

https://totallyimmersed.com.au/

Response headers include the HTTP Content-Security-Policy security header with the following security issues:object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'. script-src: script-src directive is missing. 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'. 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-1021
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Method	Parameters	Evidence
https://totallyimmersed.com.au/products/	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 Cookies: _shopify_analytics=:AZ7c5VyBAAEAfGinDtBpGhPTO0R8BcFA2Aauf5N1LIY5EONwb8U3U6Iti07W8Tr0epRacy6TlnWXizsbGBy-yI31_1de6nqDd6EXnA: _shopify_essential...	Credit Card Number: 4658845188201 4681795272809

Vulnerability description

We noticed that this application does not properly prevent a person's private, personal information from being accessed by actors who either (1) are not explicitly authorized to access the information or (2) do not have the implicit consent of the person about whom the information is collected. Sensitive data targeted usually consists of emails, credit card and social security numbers.

Risk description

The risk exists that sensitive personal information within the application could be accessed by unauthorized parties. This could lead to privacy violations, identity theft, or other forms of personal or corporate harm.

Recommendation

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

Classification

CWE	CWE-201
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL
Missing: https://totallyimmersed.com.au/.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://totallyimmersed.com.au/	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: info@totallyimmersed.com.au

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

CVE	CVSS	EPSS Score	EPSS Percentile	CISA KEV	Summary
CVE-2020-11023	6.9	0.8383	0.99657	Yes	In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.
CVE-2020-11022	6.9	0.99019	0.99925	No	In jQuery starting with 1.12.0 and before 3.5.0, passing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.

Vulnerability description

Vulnerabilities found for jQuery 3.4.1

Risk description

These vulnerabilities expose the affected applications to the risk of unauthorized access to confidential data and possibly to denial of service attacks. An attacker could search for an appropriate exploit (or create one) for any of these vulnerabilities and use it to attack the system. Notes: - The vulnerabilities are identified based on the server's version.; - Only the first 5 vulnerabilities with the highest risk are shown for each port.; Since the vulnerabilities were discovered using only version-based testing, the risk level for this finding will not exceed "high" severity. Critical risks will be assigned to vulnerabilities identified through accurate active testing methods.

Recommendation

We recommend you to upgrade the affected software to the latest version in order to eliminate the risks imposed by these vulnerabilities.

Evidence

DKIM selector	Key type	Key size	Value
default	rsa	1422	"v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAye+LxJZlxCqoJz139ZkZUscSQ2MwoZ7yG7W4mZSCIq9T/RkMAcnhEK3Q3DAvPK2GpTCjSz0Yfb4zkgWBa9VgCgI4meCD0kvsJADTSd5DN8SU5rTXJ4Gt+knrH2B9mpZ0vsPTmmMejbl3K6oDCl2+KRWxyGl0zckEue0bc+sVm9iTxNymkqiEIj6Lo2++m5UM5" "2vH6JESubJYq80tZ1OBkR7adDWZ4diO7HSUrjT2yGQEEq86zJOzAPT9riknbFlLl6+BkoeXUc0FcShF18pWW44KjWE0l9TF4doEUiR0T0ey5/pdGmnEKcZKxeCLMQjVmd3Kwma321v78v3Q3CcWYwIDAQAB;"

Vulnerability description

We found that the DKIM record uses common selectors. The use of common DKIM selectors such as default, test, dkim, or mail may indicate a lack of proper customization or key management. Attackers often target domains using such selectors because they suggest that the domain is relying on default configurations, which could be less secure and easier to exploit. This can increase the risk of DKIM key exposure or misuse.

Risk description

Using a common DKIM selector makes it easier for attackers to predict and exploit email authentication weaknesses. Attackers may attempt to find corresponding DKIM keys or improperly managed records associated with common selectors. If a common selector is coupled with a weak key length or poor key management practices, it significantly increases the likelihood of email spoofing and phishing attacks.

Recommendation

We recommend using unique, customized selectors for each DKIM key to make it more difficult for attackers to predict and target the domain's DKIM records. Regularly rotate selectors and associated keys to further strengthen the security of your domain's email authentication infrastructure.

Evidence

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

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

Software / Version	Category
Shopify	Ecommerce
Cart Functionality	Ecommerce
WordPress	CMS, Blogs
MySQL	Databases
PHP	Programming languages
Shop Pay	Payment processors
Visa	Payment processors
PayPal	Payment processors
Mastercard	Payment processors
Google Pay	Payment processors
Apple Pay	Payment processors
MailChimp	Marketing automation, Email
jQuery 3.4.1	JavaScript libraries
Google Tag Manager	Tag managers
Google Analytics	Analytics
Facebook Pixel 2.9.338	Analytics
Priority Hints	Performance
DoubleClick Floodlight	Advertising
HSTS	Security
Cloudflare	CDN
Open Graph	Miscellaneous
HTTP/3	Miscellaneous
LazySizes	JavaScript libraries, Performance
core-js 2.6.12	JavaScript libraries

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
_dmarc.totallyimmersed.com.au	TXT	Text record	"v=DMARC1;p=reject;sp=reject;adkim=r;aspf=r;pct=100;fo=1;rf=afrf;ri=86400;ruf=mailto:z.simpson@hobiecat.com.au; rua=mailto:db0520058e5648a1a5a05c1d56c96d5b@dmarc-reports.cloudflare.net;"

Evidence

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

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

Domain Queried	DNS Record Type	Description	Value
totallyimmersed.com.au	SPF	Sender Policy Framework	"v=spf1 ip4:138.217.245.86 include:spf.protection.outlook.com -all"

Evidence

DKIM selector	Key type	Key size	Value
default	rsa	1422	"v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAye+LxJZlxCqoJz139ZkZUscSQ2MwoZ7yG7W4mZSCIq9T/RkMAcnhEK3Q3DAvPK2GpTCjSz0Yfb4zkgWBa9VgCgI4meCD0kvsJADTSd5DN8SU5rTXJ4Gt+knrH2B9mpZ0vsPTmmMejbl3K6oDCl2+KRWxyGl0zckEue0bc+sVm9iTxNymkqiEIj6Lo2++m5UM5" "2vH6JESubJYq80tZ1OBkR7adDWZ4diO7HSUrjT2yGQEEq86zJOzAPT9riknbFlLl6+BkoeXUc0FcShF18pWW44KjWE0l9TF4doEUiR0T0ey5/pdGmnEKcZKxeCLMQjVmd3Kwma321v78v3Q3CcWYwIDAQAB;"
k1	rsa	1296	"k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDbNrX2cY/GUKIFx2G/1I00ftdAj713WP9AQ1xir85i89sA2guU0ta4UX1Xzm06XIU6iBP41VwmPwBGRNofhBVR+e6WHUoNyIR4Bn84LVcfZE20rmDeXQblIupNWBqLXM1Q+VieI/eZu/7k9/vOkLSaQQdml4Cv8lb3PcnluMVIhQIDAQAB;"
selector1	rsa	1296	"v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDPtsL4PO6lr03zjsBvOxIIvnLkslqqFHaQC5R6c305kAND1rlyGIxRq+R1FxEpJ7OJZjHmZBr+AlOdxS0TYFVgPMwTLvzTcJ5Znk2varkIJjqjBsi8STHMZFGeUod6nWvPK3t3YBygusiF9bZH+P+HUjJljDWBiYohiSIjgL5FEQIDAQAB;"
selector2	rsa	1296	"v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDPu/FNKXdzs8QiuipzjLzuf7fCJ5eQJjrZbHg9q0ZUEVNsTagVQH5AwJ/JFvoAIq4zxqC86M8IlPZzmT6XcJ5YaA18BVCv+AO60yDjNACYBVfVj1DA2WYQU9csslSvKCu24EnXdqdiGfb7n5i/NOWIA9OcLIMtjKWNfTud2xE2pQIDAQAB;"

Evidence

Domain Queried	DNS Record Type	Description	Value
totallyimmersed.com.au	A	IPv4 address	172.67.193.84
totallyimmersed.com.au	A	IPv4 address	104.21.84.133
totallyimmersed.com.au	NS	Name server	liberty.ns.cloudflare.com
totallyimmersed.com.au	NS	Name server	norm.ns.cloudflare.com
totallyimmersed.com.au	MX	Mail server	0 totallyimmersed-com-au.mail.protection.outlook.com
totallyimmersed.com.au	SOA	Start of Authority	liberty.ns.cloudflare.com. dns.cloudflare.com. 2406712729 10000 2400 604800 1800
totallyimmersed.com.au	AAAA	IPv6 address	2606:4700:3033::ac43:c154
totallyimmersed.com.au	AAAA	IPv6 address	2606:4700:3032::6815:5485
totallyimmersed.com.au	TXT	Text record	"MS=ms12589262"
totallyimmersed.com.au	TXT	Text record	"apple-domain-verification=DaNiPxiwQB6pT1Em"
totallyimmersed.com.au	SPF	Sender Policy Framework	"v=spf1 ip4:138.217.245.86 include:spf.protection.outlook.com -all"
_dmarc.totallyimmersed.com.au	TXT	Text record	"v=DMARC1;p=reject;sp=reject;adkim=r;aspf=r;pct=100;fo=1;rf=afrf;ri=86400;ruf=mailto:z.simpson@hobiecat.com.au; rua=mailto:db0520058e5648a1a5a05c1d56c96d5b@dmarc-reports.cloudflare.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
Cloudflare	CDN
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

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