Vulnerability Scan Result
| Title: | CoinVerify - Instant USDT Verification |
| Description: | CoinVerify - Instantly verify if your USDT is real or flash. Fast, secure, and reliable verification for Tron and BEP-20 networks. |
| ip_address | 75.2.60.5 |
| country | US  |
| network_name | Amazon Inc |
| asn | AS16509 |
9/tcp | tcpwrapped | - - |
25/tcp | smtp | - - |
26/tcp | tcpwrapped | - - |
80/tcp | http | Netlify - |
81/tcp | hosts2-ns | - - |
102/tcp | iso-tsap | - - |
106/tcp | tcpwrapped | - - |
135/tcp | msrpc | - - |
138/tcp | tcpwrapped | - - |
179/tcp | tcpwrapped | - - |
199/tcp | tcpwrapped | - - |
201/tcp | at-rtmp | - - |
383/tcp | tcpwrapped | - - |
443/tcp | https | Netlify - |
464/tcp | kpasswd5 | - - |
515/tcp | printer | - - |
540/tcp | tcpwrapped | - - |
544/tcp | kshell | - - |
548/tcp | afp | - - |
563/tcp | tcpwrapped | - - |
691/tcp | resvc | - - |
860/tcp | tcpwrapped | - - |
873/tcp | rsync | - - |
995/tcp | pop3s | - - |
1026/tcp | tcpwrapped | - - |
1028/tcp | tcpwrapped | - - |
1241/tcp | tcpwrapped | - - |
1589/tcp | tcpwrapped | - - |
1720/tcp | tcpwrapped | - - |
1723/tcp | tcpwrapped | - - |
2082/tcp | infowave | - - |
2100/tcp | tcpwrapped | - - |
2222/tcp | tcpwrapped | - - |
2483/tcp | ttc | - - |
2484/tcp | ttc-ssl | - - |
3000/tcp | ppp | - - |
3128/tcp | squid-http | - - |
3389/tcp | ms-wbt-server | - - |
3784/tcp | tcpwrapped | - - |
4280/tcp | vrml-multi-use | - - |
4445/tcp | upnotifyp | - - |
5009/tcp | tcpwrapped | - - |
5013/tcp | fmpro-v6 | - - |
5051/tcp | tcpwrapped | - - |
5101/tcp | admdog | - - |
5223/tcp | hpvirtgrp | - - |
5432/tcp | tcpwrapped | - - |
5631/tcp | pcanywheredata | - - |
5800/tcp | vnc-http | - - |
5900/tcp | vnc | - - |
5986/tcp | tcpwrapped | - - |
6588/tcp | tcpwrapped | - - |
6699/tcp | tcpwrapped | - - |
7001/tcp | tcpwrapped | - - |
7070/tcp | tcpwrapped | - - |
7199/tcp | tcpwrapped | - - |
8000/tcp | tcpwrapped | - - |
8008/tcp | http | - - |
8009/tcp | tcpwrapped | - - |
8222/tcp | tcpwrapped | - - |
8500/tcp | tcpwrapped | - - |
9000/tcp | tcpwrapped | - - |
9042/tcp | None | - - |
19638/tcp | tcpwrapped | - - |
49153/tcp | tcpwrapped | - - |
49155/tcp | tcpwrapped | - - |
49156/tcp | unknown | - - |
| Software / Version | Category |
|---|---|
| Firebase | Databases, Development |
| Lucide | Font scripts |
| Open Graph | Miscellaneous |
| React | JavaScript frameworks |
| React Router 6 | JavaScript frameworks |
| Vite | Miscellaneous |
| Netlify | PaaS, CDN |
| HSTS | Security |
Web Application Vulnerabilities
Evidence
| URL | Evidence |
|---|---|
| https://coinverify.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 | Evidence |
|---|---|
| https://coinverify.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-693 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://coinverify.net/ | 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
| Software / Version | Category |
|---|---|
| Firebase | Databases, Development |
| Lucide | Font scripts |
| Open Graph | Miscellaneous |
| React | JavaScript frameworks |
| React Router 6 | JavaScript frameworks |
| Vite | Miscellaneous |
| Netlify | PaaS, CDN |
| HSTS | Security |
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
Website is accessible.
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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.coinverify.net | TXT | Text record | "v=DMARC1; p=quarantine; adkim=r; aspf=r; rua=mailto:dmarc_rua@onsecureserver.net;" |
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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.coinverify.net | TXT | Text record | "v=DMARC1; p=quarantine; adkim=r; aspf=r; rua=mailto:dmarc_rua@onsecureserver.net;" |
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
We found insecure DNS cookie usage on the following nameservers: ns67.domaincontrol.com, ns68.domaincontrol.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.coinverify.net | TXT | Text record | "v=DMARC1; p=quarantine; adkim=r; aspf=r; rua=mailto:dmarc_rua@onsecureserver.net;" |
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
| Software / Version | Category |
|---|---|
| Firebase | Databases, Development |
| Netlify | PaaS, CDN |
| HSTS | Security |
| Vite | Miscellaneous |
| 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 |
|---|---|---|---|
| coinverify.net | A | IPv4 address | 75.2.60.5 |
| coinverify.net | NS | Name server | ns67.domaincontrol.com |
| coinverify.net | NS | Name server | ns68.domaincontrol.com |
| coinverify.net | SOA | Start of Authority | ns67.domaincontrol.com. dns.jomax.net. 2025081608 28800 7200 604800 600 |
| _dmarc.coinverify.net | TXT | Text record | "v=DMARC1; p=quarantine; adkim=r; aspf=r; rua=mailto:dmarc_rua@onsecureserver.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
| Operating System | Accuracy |
|---|---|
| Windows | 100% |
Vulnerability description
OS Detection