Vulnerability Scan Result
| Title: | Network Tools: DNS,IP,Email |
| Description: | DNS and Network troubleshooting and diagnostic tools integrated into one sweet interface. |
| ip_address | 108.157.194.25 |
| country | US  |
| network_name | Amazon.com, Inc. |
| asn | AS16509 |
| ip_address | 108.157.194.11 |
| country | US |
| network_name | Amazon.com, Inc. |
| asn | AS16509 |
| ip_address | 108.157.194.103 |
| country | US |
| network_name | Amazon.com, Inc. |
| asn | AS16509 |
| ip_address | 108.157.194.48 |
| country | US |
| network_name | Amazon.com, Inc. |
| asn | AS16509 |
80/tcp | http | Amazon CloudFront httpd - |
443/tcp | https | - - |
| Software / Version | Category |
|---|---|
| AngularJS | JavaScript frameworks |
| Amazon Web Services | PaaS |
| AWS Certificate Manager | SSL/TLS certificate authorities |
| Amazon CloudFront | CDN |
| cdnjs | CDN |
| Bootstrap 3.3.7 | UI frameworks |
| Goober | JavaScript libraries |
| Google Analytics | Analytics |
| jQuery 3.7.1 | JavaScript libraries |
| Windows Server | Operating systems |
| VWO | Analytics, A/B Testing |
| PWA | Miscellaneous |
| Microsoft ASP.NET 4.0.30319 | Web frameworks |
| Cloudflare | CDN |
| Google Tag Manager | Tag managers |
| HubSpot | Marketing automation |
| HubSpot Chat | Live chat |
| IIS 10.0 | Web servers |
| JsObservable | JavaScript libraries |
| JsRender 1.0.14 | JavaScript libraries |
| JsViews | JavaScript libraries |
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.01668 | 0.81767 | 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.11866 | 0.93559 | In Bootstrap before 3.4.0, XSS is possible in the affix configuration target property. |
| CVE-2018-20676 | 6.1 | 0.06144 | 0.90606 | In Bootstrap before 3.4.0, XSS is possible in the tooltip data-viewport attribute. |
| CVE-2018-14042 | 6.1 | 0.01985 | 0.8327 | 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://mxtoolbox.com/SuperTool.aspx | Response headers do not include the Referrer-Policy HTTP security header as well as the |
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://mxtoolbox.com/SuperTool.aspx | 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-693 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://mxtoolbox.com/SuperTool.aspx | 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 | Error message error report found in: |
Vulnerability description
We noticed that the target application does not properly handle exceptional conditions, leading to error messages that reveal sensitive information.
Risk description
The risk is that an attacker may use the contents of error messages to help launch another, more focused attack. For example, an attempt to exploit a path traversal weakness (CWE-22) might yield the full pathname of the installed application.
Recommendation
It is recommended treating all exceptions of the application flow. Ensure that error messages only contain minimal details.
Classification
| CWE | CWE-209 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://mxtoolbox.com/SuperTool.aspx | 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 |
|---|---|
| https://mxtoolbox.com/SuperTool.aspx | 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
| Software / Version | Category |
|---|---|
| AngularJS | JavaScript frameworks |
| Amazon Web Services | PaaS |
| AWS Certificate Manager | SSL/TLS certificate authorities |
| Amazon CloudFront | CDN |
| cdnjs | CDN |
| Bootstrap 3.3.7 | UI frameworks |
| Goober | JavaScript libraries |
| Google Analytics | Analytics |
| jQuery 3.7.1 | JavaScript libraries |
| Windows Server | Operating systems |
| VWO | Analytics, A/B Testing |
| PWA | Miscellaneous |
| Microsoft ASP.NET 4.0.30319 | Web frameworks |
| Cloudflare | CDN |
| Google Tag Manager | Tag managers |
| HubSpot | Marketing automation |
| HubSpot Chat | Live chat |
| IIS 10.0 | Web servers |
| JsObservable | JavaScript libraries |
| JsRender 1.0.14 | JavaScript libraries |
| JsViews | 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
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://mxtoolbox.com/WhatIsMyIP/ |
|
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.
Evidence
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://mxtoolbox.com/SuperTool.aspx | 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: feedback@mxtoolbox.com ping@tools.mxtoolbox.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 |
Evidence
| URL | Method | Summary |
|---|---|---|
| https://mxtoolbox.com/SuperTool.aspx | OPTIONS | We did a HTTP OPTIONS request. The server responded with a 405 status code and the header: `Allow: GET, HEAD, OPTIONS, TRACE` 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 |
Infrastructure Vulnerabilities
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.mxtoolbox.com | TXT | Text record | "v=DMARC1; p=reject; rua=mailto:634990a7@mxtoolbox.dmarc-report.com,mailto:634990a7@mxtoolbox.dmarc-report.net; ruf=mailto:634990a7@forensics.dmarc-report.com,mailto:634990a7@forensics.dmarc-report.net; fo=1; pct=100" |
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
We found insecure EDNS configuration on the following nameservers: ns-1736.awsdns-25.co.uk ns-1736.awsdns-25.co.uk:
Vulnerability description
We found that the server does not properly implement EDNS (Extension Mechanisms for DNS). EDNS allows larger DNS packets and supports modern features such as DNSSEC.
Risk description
The risk exists because improper or missing EDNS support can lead to truncated responses, degraded DNS performance, and compatibility issues with DNSSEC. This exposes users to risks such as incomplete DNS resolution and failed DNSSEC validation.
Recommendation
We recommend ensuring the proper implementation of EDNS on the DNS server. Update the DNS server software to support EDNS fully, including modern features like DNSSEC. Regularly test DNS configurations to ensure compliance and performance.
Evidence
We found insecure DNS cookie usage on the following nameservers: ns-1320.awsdns-37.org, ns-1736.awsdns-25.co.uk, ns-495.awsdns-61.com, ns-984.awsdns-59.net
Vulnerability description
We found that the server does not implement DNS Cookies or uses them insecurely. DNS Cookies help prevent DNS-based attacks, such as spoofing and amplification attacks.
Risk description
The risk exists because without DNS Cookies, the server is vulnerable to DNS spoofing and amplification attacks. Attackers can manipulate responses or use the server in distributed denial-of-service (DDoS) attacks, compromising network availability and security.
Recommendation
We recommend enabling DNS Cookies to prevent spoofed DNS responses. Ensure proper cookie validation is implemented to mitigate DNS amplification attacks. Regularly update DNS servers to support the latest DNS security features.
Evidence
| Software / Version | Category |
|---|---|
| Windows Server | Operating systems |
| Microsoft ASP.NET 4.0.30319 | Web frameworks |
| Amazon Web Services | PaaS |
| IIS 10.0 | Web servers |
| AngularJS | JavaScript frameworks |
| Google Analytics | Analytics |
| Amazon CloudFront | CDN |
| AWS Certificate Manager | SSL/TLS certificate authorities |
| JsObservable | JavaScript libraries |
| JsViews | JavaScript libraries |
| Cloudflare | CDN |
| VWO | Analytics, A/B Testing |
| Qualaroo | Surveys |
| JsRender 1.0.14 | JavaScript libraries |
| HubSpot Chat | Live chat |
| HubSpot Analytics | Analytics |
| HubSpot | Marketing automation |
| Google Tag Manager | Tag managers |
| cdnjs | CDN |
| Customer.io | Marketing automation |
| Crazy Egg | Analytics |
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 |
|---|---|---|---|
| rsa | 1296 | "v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCJEzpQHzFwyeMdycpwhHK6KlnqPFIbysy/ENw1SnzI2LjTi4loS9KcLNjUlbogAyn4JsQprwkMqwUrA5uATSVpKRBclXdlDrlLLmkTR1nISsg0WPfehPNU6K6NxiZ3YyoiHhHx2EiulpesEGn502RYcxqNN9JSPGr/mmorqPrF+QIDAQAB" | |
| mailo | rsa | 1296 | "v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQD4t0bsSbqtI8qX3gx0gQcinrSUJG3KVZBupcwOFYFhiDYlH6GykZwVe4w4p/qFhunnARd6VGWiThUMbhC41P2LQRPsGO7QIXiiDDBtRs5C3Oiln49/FAK6lbLnKxAbqx9cVJIlv5gCl6oGStukY+hKHX4VsIPnQgJWRRQ0Czos/QIDAQAB" |
| selector1 | rsa | 1296 | "v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCx/LE2O48EFy1ufqdfYmMMs97Rt1QHnzqKWwhoXxuzKmYZGCqVHJOzz9dm6QrVXKvlWJpCOLv3X9v43w6A1SAD8+IDtvyys01uohGADbyzsa0xbmrFxdFTq2llHHqKFWVm2xY1DSkkOO5a5/Ytcd8cvfIhmCpOhSd8KnlxSgtD+QIDAQAB;" |
| selector2 | rsa | 1422 | "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA2K3gFzEID2McvjfMu0S66upmSeszUpChJBagZ/IKS/bus0bXqdWiVXzOr11NQZ7+MSS+tpKojJfE8tTTJyMHAdwiq3I83570m7SJ/g4zWcM1TLiwXCinepjumwIrpbHCFpVLmBQEOfegWFYcGervDmro6nv3toVDCf9AdD5jhlEG6EW0OmSWtnDb+5pEcGIqG" "z2+RG12VO0L3DV0Xr4elBmI4yCS85pYXmrn1bCSS2T9o+XYbgIGAi6kTSeUBCK60OZ2owBlvu2kkjm+xZ8XK1+uNwsBFcyNu9R6E7YxRWupxnB0qbT+L6ewoNnsAusMLrX0FKnG1h84fC69NqZ56QIDAQAB;" |
| smtpapi | rsa | 1296 | "k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDPtW5iwpXVPiH5FzJ7Nrl8USzuY9zqqzjE0D1r04xDN6qwziDnmgcFNNfMewVKN2D1O+2J9N14hRprzByFwfQW76yojh54Xu3uSbQ3JP0A7k8o8GutRF8zbFUA8n0ZH2y0cIEjMliXY4W4LwPA7m4q0ObmvSjhd63O9d8z1XkUBwIDAQAB" |
Evidence
| Operating System | Accuracy |
|---|---|
| Apple macOS 10.13 (High Sierra) - 10.15 (Catalina) or iOS 11.0 - 13.4 (Darwin 17.0.0 - 19.2.0) | 88% |
Vulnerability description
OS Detection
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| mxtoolbox.com | SPF | Sender Policy Framework | "v=spf1 redirect=mxtoolbox.com.hosted.spf-report.com" |
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| mxtoolbox.com | A | IPv4 address | 108.157.194.48 |
| mxtoolbox.com | A | IPv4 address | 108.157.194.103 |
| mxtoolbox.com | A | IPv4 address | 108.157.194.11 |
| mxtoolbox.com | A | IPv4 address | 108.157.194.25 |
| mxtoolbox.com | NS | Name server | ns-1320.awsdns-37.org |
| mxtoolbox.com | NS | Name server | ns-1736.awsdns-25.co.uk |
| mxtoolbox.com | NS | Name server | ns-495.awsdns-61.com |
| mxtoolbox.com | NS | Name server | ns-984.awsdns-59.net |
| mxtoolbox.com | MX | Mail server | 0 aspmx.l.google.com |
| mxtoolbox.com | MX | Mail server | 10 aspmx2.googlemail.com |
| mxtoolbox.com | MX | Mail server | 10 aspmx3.googlemail.com |
| mxtoolbox.com | MX | Mail server | 5 alt1.aspmx.l.google.com |
| mxtoolbox.com | MX | Mail server | 5 alt2.aspmx.l.google.com |
| mxtoolbox.com | SOA | Start of Authority | ns-1320.awsdns-37.org. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400 |
| mxtoolbox.com | TXT | Text record | "6ffyqp6bfm0xx4bcgd1ybz0jtknhgpdy" |
| mxtoolbox.com | TXT | Text record | "google-site-verification=a72lcHiaH48r427O4d4O6SrvOBQkmH4IGZ98mH9YWwU" |
| mxtoolbox.com | TXT | Text record | "lml8nrmxdc063ms0skf3bnvm2zvslffz" |
| mxtoolbox.com | TXT | Text record | "mailru-verification: 18440d267f8068a2" |
| mxtoolbox.com | TXT | Text record | "yahoo-verification-key=VtY1K1/IZ0c2E6oFnpXiTymAITi3lqo8IlXNDII0LdE=" |
| mxtoolbox.com | SPF | Sender Policy Framework | "v=spf1 redirect=mxtoolbox.com.hosted.spf-report.com" |
| _dmarc.mxtoolbox.com | TXT | Text record | "v=DMARC1; p=reject; rua=mailto:634990a7@mxtoolbox.dmarc-report.com,mailto:634990a7@mxtoolbox.dmarc-report.net; ruf=mailto:634990a7@forensics.dmarc-report.com,mailto:634990a7@forensics.dmarc-report.net; fo=1; pct=100" |
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.