Vulnerability Scan Result

Target:

http://hamilton.net/ (redirect)

Scanned target: https://hamilton.net/

Submitted: Jun 12, 2026 from SD

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Hamilton Fiber Internet
Description:	Experience the benefits of Hamilton Fiber Internet: clear calling, numerous channels, and versatile plans that fit your needs.

IP Information

ip_address	66.196.48.72
country	US
network_name	Nedelco Inc.
asn	AS13765

Open Ports

21/tcp	tcpwrapped	- -
22/tcp	tcpwrapped	- -
80/tcp	tcpwrapped	- -
443/tcp	tcpwrapped	- -

Web Technologies

Software / Version	Category
Microsoft Advertising	Advertising
Adobe Fonts	Font scripts
Bootstrap 3.3.5	UI frameworks
LazySizes	JavaScript libraries, Performance
jQuery Migrate 3.4.1	JavaScript libraries
core-js 3.48.0	JavaScript libraries
Google Analytics	Analytics
Apache HTTP Server	Web servers
Isotope	JavaScript libraries
jQuery 3.7.1	JavaScript libraries
Masonry	JavaScript libraries
MySQL	Databases
Open Graph	Miscellaneous
PHP	Programming languages
Piwik PRO Core	Analytics
Site Kit 1.181.0	Analytics, WordPress plugins
DoubleClick Floodlight	Advertising
Swiper	JavaScript libraries
Typekit	Font scripts
Priority Hints	Performance
WordPress	CMS, Blogs
Google Tag Manager	Tag managers
HubSpot	Marketing automation
HubSpot Chat	Live chat
HSTS	Security
RSS	Miscellaneous
Yoast SEO 27.8	SEO, WordPress plugins

Web Application Vulnerabilities

Evidence

CVE	CVSS	EPSS Score	EPSS Percentile	Summary
CVE-2024-6484	6.4	0.00049	0.15167	A vulnerability has been identified in Bootstrap that exposes users to Cross-Site Scripting (XSS) attacks. The issue is present in the carousel component, where the data-slide and data-slide-to attributes can be exploited through the href attribute of an <a> tag due to inadequate sanitization. This vulnerability could potentially enable attackers to execute arbitrary JavaScript within the victim's browser.
CVE-2019-8331	6.1	0.1686	0.96652	In Bootstrap before 3.4.1 and 4.3.x before 4.3.1, XSS is possible in the tooltip or popover data-template attribute.
CVE-2018-20677	6.1	0.03984	0.89158	In Bootstrap before 3.4.0, XSS is possible in the affix configuration target property.
CVE-2018-20676	6.1	0.03835	0.88733	In Bootstrap before 3.4.0, XSS is possible in the tooltip data-viewport attribute.
CVE-2018-14042	6.1	0.04009	0.89228	In Bootstrap before 4.1.2, XSS is possible in the data-container property of tooltip.

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

URL	Evidence
https://hamilton.net/	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://hamilton.net/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
Microsoft Advertising	Advertising
Adobe Fonts	Font scripts
Bootstrap 3.3.5	UI frameworks
LazySizes	JavaScript libraries, Performance
jQuery Migrate 3.4.1	JavaScript libraries
core-js 3.48.0	JavaScript libraries
Google Analytics	Analytics
Apache HTTP Server	Web servers
Isotope	JavaScript libraries
jQuery 3.7.1	JavaScript libraries
Masonry	JavaScript libraries
MySQL	Databases
Open Graph	Miscellaneous
PHP	Programming languages
Piwik PRO Core	Analytics
Site Kit 1.181.0	Analytics, WordPress plugins
DoubleClick Floodlight	Advertising
Swiper	JavaScript libraries
Typekit	Font scripts
Priority Hints	Performance
WordPress	CMS, Blogs
Google Tag Manager	Tag managers
HubSpot	Marketing automation
HubSpot Chat	Live chat
HSTS	Security
RSS	Miscellaneous
Yoast SEO 27.8	SEO, WordPress plugins

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://hamilton.net/	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://hamilton.net/	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
Missing: https://hamilton.net/.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://hamilton.net/	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@hamilton.net

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

Domain Queried	DNS Record Type	Description	Value
hamilton.net	A	IPv4 address	66.196.48.72
hamilton.net	NS	Name server	dns1.hamilton.net
hamilton.net	NS	Name server	dns2.hamilton.net
hamilton.net	MX	Mail server	10 smtp5.hamilton.net
hamilton.net	MX	Mail server	20 smtp4.hamilton.net
hamilton.net	MX	Mail server	10 smtp6.hamilton.net
hamilton.net	SOA	Start of Authority	dns1.hamilton.net. hostmaster.hamilton.net. 2026061705 43200 7200 1809600 3600
hamilton.net	AAAA	IPv6 address	2606:4900:26::aaaa:72:1
hamilton.net	TXT	Text record	"e2ma-verification=0d7bb"
hamilton.net	TXT	Text record	"google-site-verification=YObL8meXnm-WQerTlWLedOKH6EpYrgd-yrMYE-yBP0A"
hamilton.net	TXT	Text record	"ld8l8ticgrq17s8knfuti6ss8b"
hamilton.net	TXT	Text record	"qlt1d26f40iiitqstcpd4ilj7a"
hamilton.net	SPF	Sender Policy Framework	"v=spf1 ip4:66.196.48.0/25 ip4:66.196.48.188 ip4:66.196.50.128/26 ip4:139.60.0.209 include:e2ma.net include:spf.mailjet.com include:242327164.spf10.hubspotemail.net -all"
_dmarc.hamilton.net	TXT	Text record	"v=DMARC1; p=none;"

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.