Vulnerability Scan Result
| Title: | Insurance Dallas tx, life insurance, Dallas Financial Services |
| Description: | At MyLifeWerks Insurance, we believe that doing things together is everything. We take the time to listen, to understand, to work together and to give you access to innovative financial solutions that help you prepare for all your needs today, and into your future. |
| ip_address | 138.197.108.91 |
| country | US  |
| network_name | DigitalOcean |
| asn | AS14061 |
22/tcp | ssh | OpenSSH 7.2p2 Ubuntu 4ubuntu2.10 |
80/tcp | http | nginx - |
443/tcp | https | nginx - |
| Software / Version | Category |
|---|---|
| All in One SEO 4.9.6.1 | SEO, WordPress plugins |
| Clipboard.js | JavaScript libraries |
| Contact Form 7 6.1.5 | WordPress plugins, Form builders |
| Font Awesome | Font scripts |
| Google Font API | Font scripts |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| AddToAny Share Buttons 1.1 | WordPress plugins |
| prettyPhoto | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| GSAP | JavaScript frameworks |
| Jetpack | WordPress plugins |
| jQuery 3.7.1 | JavaScript libraries |
| jQuery UI 1.13.3 | JavaScript libraries |
| Modernizr \1 | JavaScript libraries |
| MySQL | Databases |
| Nginx | Web servers, Reverse proxies |
| Open Graph | Miscellaneous |
| PHP | Programming languages |
| React | JavaScript frameworks |
| Really Simple SSL & Security | Security |
| Site Kit 1.176.0 | Analytics, WordPress plugins |
| DoubleClick Floodlight | Advertising |
| Visual Composer | Page builders |
| WordPress 6.9.4 | CMS, Blogs |
| AddToAny | Widgets |
| Drip | Marketing automation |
| reCAPTCHA | Security |
| Google Tag Manager | Tag managers |
| Lodash 1.13.7 | JavaScript libraries |
| RSS | Miscellaneous |
| Slider Revolution 6.7.35 | Widgets, Photo galleries |
| Wordfence Login Security 1.1.15 | WordPress plugins, Security |
| WordPress Super Cache | Caching, WordPress plugins |
Web Application Vulnerabilities
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://mylifewerksinsurance.com/ | 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://mylifewerksinsurance.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
| Software / Version | Category |
|---|---|
| All in One SEO 4.9.6.1 | SEO, WordPress plugins |
| Clipboard.js | JavaScript libraries |
| Contact Form 7 6.1.5 | WordPress plugins, Form builders |
| Font Awesome | Font scripts |
| Google Font API | Font scripts |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| AddToAny Share Buttons 1.1 | WordPress plugins |
| prettyPhoto | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| GSAP | JavaScript frameworks |
| Jetpack | WordPress plugins |
| jQuery 3.7.1 | JavaScript libraries |
| jQuery UI 1.13.3 | JavaScript libraries |
| Modernizr \1 | JavaScript libraries |
| MySQL | Databases |
| Nginx | Web servers, Reverse proxies |
| Open Graph | Miscellaneous |
| PHP | Programming languages |
| React | JavaScript frameworks |
| Really Simple SSL & Security | Security |
| Site Kit 1.176.0 | Analytics, WordPress plugins |
| DoubleClick Floodlight | Advertising |
| Visual Composer | Page builders |
| WordPress 6.9.4 | CMS, Blogs |
| AddToAny | Widgets |
| Drip | Marketing automation |
| reCAPTCHA | Security |
| Google Tag Manager | Tag managers |
| Lodash 1.13.7 | JavaScript libraries |
| RSS | Miscellaneous |
| Slider Revolution 6.7.35 | Widgets, Photo galleries |
| Wordfence Login Security 1.1.15 | WordPress plugins, Security |
| WordPress Super Cache | Caching, 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://mylifewerksinsurance.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://mylifewerksinsurance.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 |
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 |
Infrastructure Vulnerabilities
Evidence
We managed to detect a publicly accessible SSH service. Starting Nmap ( https://nmap.org ) at 2026-04-17 21:37 EEST Nmap scan report for mylifewerksinsurance.com (138.197.108.91) Host is up (0.077s latency).
PORT STATE SERVICE VERSION 22/tcp open ssh OpenSSH 7.2p2 Ubuntu 4ubuntu2.10 (Ubuntu Linux; protocol 2.0) | ssh-auth-methods: | Supported authentication methods: | publickey |_ password Service Info: OS: Linux; CPE: cpe:/o:linux:linux_kernel
Service detection performed. Please report any incorrect results at https://nmap.org/submit/ . Nmap done: 1 IP address (1 host up) scanned in 1.50 seconds
Vulnerability description
We found that the SSH service with username/password authentication is publicly accessible. Network administrators often use remote administration protocols to control devices like switches, routers, and other essential systems. However, allowing these services to be accessible via the Internet can increase security risks, creating potential opportunities for attacks on the organization.
Risk description
Exposing this service online with username/password authentication can enable attackers to launch authentication attacks, like guessing login credentials, and potentially gaining unauthorized access. Vulnerabilities, such as unpatched software, protocol flaws, or backdoors could also be exploited. An example is the CVE-2024-3094 (XZ Utils Backdoor) vulnerability.
Recommendation
We recommend turning off SSH with username/password authentication access over the Internet and instead using a Virtual Private Network (VPN) that mandates two-factor authentication (2FA). If the SSH service is essential for business purposes, we recommend limiting access only from designated IP addresses using a firewall. Furthermore, it is advisable to utilize SSH Public Key Authentication since it employs a key pair to verify the identity of a user or process.
Evidence
We found insecure DNS cookie usage on the following nameservers: ns01.gcd-dns.com, ns02.gcd-dns.com
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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| mylifewerksinsurance.com | SPF | Sender Policy Framework | "v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all" |
Vulnerability description
We found that the Sender Policy Framework (SPF) record for the domain is configured with ~all (soft fail), which indicates that emails from unauthorized IP addresses are not explicitly denied. Instead, the recipient mail server is instructed to treat these messages with suspicion but may still accept them. This configuration may not provide enough protection against email spoofing and unauthorized email delivery, leaving the domain more vulnerable to impersonation attempts.
Risk description
The ~all directive in an SPF record allows unauthorized emails to pass through some email servers, even though they fail SPF verification. While such emails may be marked as suspicious or placed into a spam folder, not all mail servers handle soft fail conditions consistently. This creates a risk that malicious actors can spoof the domain to send phishing emails or other fraudulent communications, potentially causing damage to the organization's reputation and leading to successful social engineering attacks.
Recommendation
We recommend changing the SPF record's ~all (soft fail) directive to -all (hard fail). The -all setting tells recipient mail servers to reject emails from any IP addresses not listed in the SPF record, providing stronger protection against email spoofing. Ensure that all legitimate IP addresses and services that send emails on behalf of your domain are properly included in the SPF record before implementing this change.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.mylifewerksinsurance.com | TXT | Text record | "v=DMARC1; p=reject; fo=1; rua=mailto:dmarc_rua@emaildefense.proofpoint.com; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com;" |
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 |
|---|---|---|---|
| mylifewerksinsurance.com | A | IPv4 address | 138.197.108.91 |
| mylifewerksinsurance.com | NS | Name server | ns01.gcd-dns.com |
| mylifewerksinsurance.com | NS | Name server | ns02.gcd-dns.com |
| mylifewerksinsurance.com | SOA | Start of Authority | ns01.gcd-dns.com. dns.jomax.net. 2025050201 28800 7200 604800 600 |
| mylifewerksinsurance.com | SPF | Sender Policy Framework | "v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all" |
| _dmarc.mylifewerksinsurance.com | TXT | Text record | "v=DMARC1; p=reject; fo=1; rua=mailto:dmarc_rua@emaildefense.proofpoint.com; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com;" |
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
| Operating System | Accuracy |
|---|---|
| Linux 3.10 - 4.11 | 100% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| WordPress 6.9.4 | CMS, Blogs |
| Slider Revolution 6.7.35 | Widgets, Photo galleries |
| Visual Composer | Page builders |
| MySQL | Databases |
| PHP | Programming languages |
| Contact Form 7 6.1.5 | WordPress plugins, Form builders |
| Nginx | Web servers, Reverse proxies |
| React | JavaScript frameworks |
| WordPress Super Cache | Caching, WordPress plugins |
| Jetpack | WordPress plugins |
| All in One SEO Pack 4.9.6.1 | SEO, WordPress plugins |
| AddToAny Share Buttons 1.1 | WordPress plugins |
| All in One SEO 4.9.6.1 | SEO, WordPress plugins |
| Site Kit 1.176.0 | Analytics, WordPress plugins |
| prettyPhoto | JavaScript libraries |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| jQuery | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Google Analytics GA4 | Analytics |
| Drip | Marketing automation |
| AddToAny | Widgets |
| DoubleClick Floodlight | Advertising |
| Wordfence Login Security 1.1.15 | WordPress plugins, Security |
| Underscore.js 1.13.7 | JavaScript libraries |
| reCAPTCHA | Security |
| Clipboard.js | 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.