Vulnerability Scan Result
| Title: | No title found |
| Description: | No description found |
| ip_address | 65.109.174.128 |
| country | FI  |
| network_name | Hetzner Online GmbH |
| asn | AS24940 |
22/tcp | ssh | OpenSSH 9.6p1 Ubuntu 3ubuntu13.12 |
80/tcp | http | Golang net/http server - |
443/tcp | https | Golang net/http server - |
No technologies could be detected.
Web Application Vulnerabilities
Evidence
| URL | Response URL | Evidence |
|---|---|---|
| http://servotec.com.pe/ | http://servotec.com.pe/ | Communication is made over unsecure, unencrypted HTTP. |
Vulnerability description
We noticed that the communication between the web browser and the server is done using the HTTP protocol, which transmits data unencrypted over the network.
Risk description
The risk is that an attacker who manages to intercept the communication at the network level can read and modify the data transmitted (including passwords, secret tokens, credit card information and other sensitive data).
Recommendation
We recommend you to reconfigure the web server to use HTTPS - which encrypts the communication between the web browser and the server.
Classification
| CWE | CWE-311 |
| 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.
Infrastructure Vulnerabilities
Evidence
We managed to detect a publicly accessible SSH service. Starting Nmap ( https://nmap.org ) at 2026-02-02 07:52 EET Nmap scan report for servotec.com.pe (65.109.174.128) Host is up (0.032s latency). rDNS record for 65.109.174.128: static.128.174.109.65.clients.your-server.de
PORT STATE SERVICE VERSION 22/tcp open ssh OpenSSH 9.6p1 Ubuntu 3ubuntu13.12 (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 0.79 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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| servotec.com.pe | SPF | Sender Policy Framework | "v=spf1 include:_spf.mlsend.com ip4:216.246.47.162 +a +mx include:relay.mailchannels.net ~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.servotec.com.pe | TXT | Text record | "v=DMARC1;p=none;sp=none;adkim=r;aspf=r;pct=100;fo=0;rf=afrf;ri=86400" |
Vulnerability description
We found that the DMARC record for the domain is not configured with ruf tag. A missing ruf (forensic reporting) tag in a DMARC record indicates that the domain owner has not enabled the collection of detailed failure reports. Forensic reports provide valuable insights into specific instances where emails fail DMARC authentication. Without the ruf tag, the domain administrator loses the ability to receive and analyze these reports, making it difficult to investigate individual email failures or identify targeted phishing or spoofing attacks that may be exploiting weaknesses in the email authentication setup.
Risk description
Without forensic reports (ruf), domain owners have limited visibility into the specifics of failed DMARC validation. This means potential malicious activity, such as email spoofing or phishing attempts, might go unnoticed until they result in more significant security breaches or reputational damage. Forensic reports allow for quick response to email abuses by providing detailed information about the failure, including the header information of the emails involved. The absence of this data hampers an organization's ability to identify and mitigate threats targeting its domain, increasing the risk of ongoing spoofing and fraud.
Recommendation
We recommend configuring the ruf tag in the DMARC record. This tag specifies where forensic reports should be sent, providing the domain owner with detailed data on DMARC validation failures. Forensic reports allow administrators to analyze why certain emails failed authentication, making it easier to fine-tune DMARC policies or address potential vulnerabilities. Ensure that the ruf email address belongs to a secure and trusted location capable of handling sensitive email data.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.servotec.com.pe | TXT | Text record | "v=DMARC1;p=none;sp=none;adkim=r;aspf=r;pct=100;fo=0;rf=afrf;ri=86400" |
Vulnerability description
We found that the DMARC record for the domain is not configured with rua tag. When a DMARC record is not configured with the rua (Reporting URI for Aggregate Reports) tag, the domain owner misses out on critical feedback regarding the domain's email authentication performance. Aggregate reports are essential for monitoring how a domain's DMARC policy is applied across various mail servers and whether legitimate or malicious emails are being sent on behalf of the domain. Without this reporting, domain administrators have no visibility into how their DMARC policy is being enforced, which hinders their ability to detect potential spoofing or authentication issues.
Risk description
The absence of rua reporting creates a significant blind spot in the domain's email security posture. Without aggregate reports, domain administrators cannot track DMARC compliance across email sent from their domain, leaving them unaware of potential misconfigurations or unauthorized use of their domain for malicious purposes, such as phishing or spoofing. This lack of visibility increases the risk of undetected spoofing attempts, which could damage the domain's reputation and lead to financial, operational, or reputational harm. Moreover, legitimate email issues, such as misaligned SPF or DKIM configurations, may also go unnoticed, affecting email deliverability.
Recommendation
We recommend configuring the rua tag in the DMARC record to receive aggregate reports from mail servers. This tag should point to a reliable email address or monitoring service capable of handling DMARC aggregate reports, such as rua=mailto:dmarc-reports@example.com. These reports provide valuable insights into how email from the domain is being treated by receiving mail servers, highlighting potential authentication issues and attempts to spoof the domain. Regularly reviewing these reports will help ensure the DMARC policy is properly enforced and that any email authentication failures are addressed in a timely manner.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.servotec.com.pe | TXT | Text record | "v=DMARC1; p=quarantine; rua=mailto:email@servotec.com.pe; ruf=mailto:email@servotec.com.pe; fo=1; sp=none; pct=100;" |
| _dmarc.servotec.com.pe | TXT | Text record | "v=DMARC1;p=none;sp=none;adkim=r;aspf=r;pct=100;fo=0;rf=afrf;ri=86400" |
Vulnerability description
We found that the target is configured with more than one DMARC (Domain-based Message Authentication, Reporting, and Conformance) record in its DNS settings. According to the DMARC specification, only a single DMARC record is allowed per domain. When multiple DMARC records exist, email receivers may ignore the DMARC policy, leading to an improper application of email authentication and security checks. This misconfiguration weakens the domain’s email authentication stance, potentially allowing spoofed or fraudulent emails to bypass security checks. Such inconsistencies can lead to confusion for mail receivers on how to handle emails that fail SPF (Sender Policy Framework) and DKIM (DomainKeys Identified Mail) checks.
Risk description
When a domain has multiple DMARC records, email servers may not process the DMARC policy correctly, leading to confusion about how to handle emails that fail SPF and DKIM checks. This misconfiguration can be exploited by malicious actors to send spoofed or fraudulent emails that appear to come from the affected domain. As a result, organizations may face an increased risk of phishing attacks targeting employees or customers, potential damage to their reputation, and disruptions to the delivery of legitimate emails, as some mail servers may ignore the intended DMARC policy altogether.
Recommendation
To resolve the issue of multiple DMARC records, ensure that only one valid DMARC record is published in your domain's DNS. Remove any duplicate or conflicting entries and verify the configuration using tools like MXToolbox or DMARCian. Additionally, implement a strict DMARC policy such as p=reject or p=quarantine to ensure emails that fail SPF or DKIM checks are properly handled. If subdomains are in use, configure the sp tag appropriately. Enable DMARC reporting by setting up the rua and ruf tags to receive aggregate and forensic reports, which can help monitor for ongoing issues or abuse.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.servotec.com.pe | TXT | Text record | "v=DMARC1; p=quarantine; rua=mailto:email@servotec.com.pe; ruf=mailto:email@servotec.com.pe; fo=1; sp=none; pct=100;" |
Vulnerability description
We found that the DMARC record for the domain is configured with sp=none, meaning that no policy is enforced for subdomains. This allows subdomains to send emails without being subject to DMARC checks, making it easier for attackers to spoof emails from these subdomains. Subdomains are often overlooked in email security, and attackers can exploit this misconfiguration to launch phishing or spoofing attacks from seemingly legitimate subdomains of a protected domain.
Risk description
When the DMARC record is configured with sp=none, subdomains are not subject to DMARC enforcement, allowing attackers to spoof emails from subdomains without being blocked. This creates a significant risk of phishing and impersonation attacks, where malicious emails appear to originate from trusted subdomains. These spoofed emails can be used to deceive users or damage the organization's reputation, undermining the security benefits of DMARC for the primary domain.
Recommendation
To mitigate the risk, we recommend that the subdomain policy should be updated to sp=reject to ensure that any email failing DMARC checks from subdomains is automatically rejected. This will help prevent unauthorized emails from being sent from subdomains, reducing the risk of spoofing and phishing. Additionally, it's important to regularly monitor DMARC reports to track email activity from subdomains and adjust policies as needed to maintain consistent security across the entire domain.
Evidence
We found insecure DNS cookie usage on the following nameservers: ns4788.banahosting.com, ns4789.banahosting.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 |
|---|---|---|---|
| _dmarc.servotec.com.pe | TXT | Text record | "v=DMARC1;p=none;sp=none;adkim=r;aspf=r;pct=100;fo=0;rf=afrf;ri=86400" |
Vulnerability description
We found that the DMARC record for the domain is configured with sp=none, meaning that no policy is enforced for subdomains. This allows subdomains to send emails without being subject to DMARC checks, making it easier for attackers to spoof emails from these subdomains. Subdomains are often overlooked in email security, and attackers can exploit this misconfiguration to launch phishing or spoofing attacks from seemingly legitimate subdomains of a protected domain.
Risk description
When the DMARC record is configured with sp=none, subdomains are not subject to DMARC enforcement, allowing attackers to spoof emails from subdomains without being blocked. This creates a significant risk of phishing and impersonation attacks, where malicious emails appear to originate from trusted subdomains. These spoofed emails can be used to deceive users or damage the organization's reputation, undermining the security benefits of DMARC for the primary domain.
Recommendation
To mitigate the risk, we recommend that the subdomain policy should be updated to sp=reject to ensure that any email failing DMARC checks from subdomains is automatically rejected. This will help prevent unauthorized emails from being sent from subdomains, reducing the risk of spoofing and phishing. Additionally, it's important to regularly monitor DMARC reports to track email activity from subdomains and adjust policies as needed to maintain consistent security across the entire domain.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.servotec.com.pe | TXT | Text record | "v=DMARC1; p=quarantine; rua=mailto:email@servotec.com.pe; ruf=mailto:email@servotec.com.pe; fo=1; sp=none; pct=100;" |
Vulnerability description
We found that the target uses p=quarantine in the DMARC policy. When a DMARC policy is set to p=quarantine, emails that fail DMARC validation are delivered but placed in the recipient’s spam or junk folder. Although it offers some protection, this policy is less strict than p=reject, which blocks such emails entirely.
Risk description
While emails failing DMARC validation are sent to the spam folder, users may still retrieve them from there, leading to a higher risk of phishing and spoofing attacks succeeding. Moreover, less strict enforcement may allow more fraudulent emails to reach user inboxes if misclassified.
Recommendation
We recommend considering moving to a stricter policy, such as p=reject, where emails that fail DMARC validation are completely rejected rather than delivered to spam folders. This reduces the risk of users interacting with potentially malicious emails.
Evidence
| DKIM selector | Key type | Key size | Value |
|---|---|---|---|
| default | rsa | 1422 | "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA2a6w8ii3C2w7JqvYDu++wjqLaxea84Pw/v9LumMFErhQNMKTd2KTZCa8DHJBr0QD6FuMbT6Gx2u8rgAXEOIB3FQjzCa7emBDdHyyt9IDGK0GIJKXbR1UZRxShpayZP4LsYjUFEJ6/9hZAmxM5zEh9+HUMZPFpADQrfDtGOG8BeNQY6IGRyOclRrrWjdqxBWhW" "ORpXVhjCK4X71Kn6jF0h+eIBiuSbkTBY8D/dQRCT9u5hXnqRZ3Hy+X3wjOAyXS9EQAzHDTK/Qd+2NOb38ZzFzc+S0afaLRhs6KniGq2Vvf3lNa4psIdb1+sQAemBl8+Y4hYgQaLUK927SaucWQvrwIDAQAB;" |
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 |
|---|---|
| Next.js | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| React | JavaScript frameworks |
| Google Analytics | Analytics |
| Webpack | Miscellaneous |
| Priority Hints | Performance |
| Lucide | Font scripts |
| Open Graph | 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 |
|---|---|---|---|
| servotec.com.pe | A | IPv4 address | 65.109.174.128 |
| servotec.com.pe | NS | Name server | ns4788.banahosting.com |
| servotec.com.pe | NS | Name server | ns4789.banahosting.com |
| servotec.com.pe | MX | Mail server | 0 single-4788.banahosting.com |
| servotec.com.pe | SOA | Start of Authority | ns4788.banahosting.com. support.banahosting.com. 2026020200 3600 1800 1209600 86400 |
| servotec.com.pe | TXT | Text record | "google-site-verification=0IyrMna6KjnVOHxE0qZDL2o78I49alJdZN0n9TTn9OM" |
| servotec.com.pe | TXT | Text record | "mailerlite-domain-verification=6fd902b3fed4b0ff2aa937c8be0ba76cfa55d1cd" |
| servotec.com.pe | SPF | Sender Policy Framework | "v=spf1 include:_spf.mlsend.com ip4:216.246.47.162 +a +mx include:relay.mailchannels.net ~all" |
| _dmarc.servotec.com.pe | TXT | Text record | "v=DMARC1; p=quarantine; rua=mailto:email@servotec.com.pe; ruf=mailto:email@servotec.com.pe; fo=1; sp=none; pct=100;" |
| _dmarc.servotec.com.pe | TXT | Text record | "v=DMARC1;p=none;sp=none;adkim=r;aspf=r;pct=100;fo=0;rf=afrf;ri=86400" |
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 5.0 - 5.4 | 96% |
Vulnerability description
OS Detection
Evidence
| DKIM selector | Key type | Key size | Value |
|---|---|---|---|
| default | rsa | 1422 | "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA2a6w8ii3C2w7JqvYDu++wjqLaxea84Pw/v9LumMFErhQNMKTd2KTZCa8DHJBr0QD6FuMbT6Gx2u8rgAXEOIB3FQjzCa7emBDdHyyt9IDGK0GIJKXbR1UZRxShpayZP4LsYjUFEJ6/9hZAmxM5zEh9+HUMZPFpADQrfDtGOG8BeNQY6IGRyOclRrrWjdqxBWhW" "ORpXVhjCK4X71Kn6jF0h+eIBiuSbkTBY8D/dQRCT9u5hXnqRZ3Hy+X3wjOAyXS9EQAzHDTK/Qd+2NOb38ZzFzc+S0afaLRhs6KniGq2Vvf3lNa4psIdb1+sQAemBl8+Y4hYgQaLUK927SaucWQvrwIDAQAB;" |
Evidence
| Software / Version | Category |
|---|---|
| Next.js | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| React | JavaScript frameworks |
| Google Analytics | Analytics |
| Webpack | Miscellaneous |
| Priority Hints | Performance |
| Lucide | Font scripts |
| Open Graph | 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.