Is puntoblu.me a scam? TrustSniffer's high-risk assessment: 0/100

Security Alert

Kaspersky, Sophos flagged this site in external intelligence checks, indicating elevated compromise/scam exposure that requires immediate caution.

The website is a publicly exposed web-server directory for puntoblu.me rather than a developed business or service platform. Its root page presents an “Index of /” listing of PHP files and an error log, with no apparent monetization, login flow, forms, social presence, or visitor-facing explanation of its purpose.

Scam/Impersonation Risk

The site has a material external reputation contradiction: it is reported as blacklisted, with multiple malicious and suspicious detections, including detections attributed to Kaspersky and Sophos. This evidence warrants a clearly cautionary posture for sensitive interaction, even though the observed page itself does not display a login form, payment workflow, or apparent brand-impersonation content. The directory listing exposes server-side filenames and an error log, which is a security-relevant misconfiguration and does not establish a legitimate operating identity. No on-page impersonation or phishing form was observed, but those absences do not offset the confirmed external detections. Evidence:

• External reputation telemetry recorded 14 malicious and 2 suspicious detections from 21 evaluated results; Kaspersky and Sophos were among the flagged vendors.
• The domain is blacklisted by two recorded sources, while the Google Safe Browsing result was not malicious.
• Domain registration telemetry records puntoblu.me as created on 2016-06-01 and approximately 10.23 years old.
• Historical telemetry records 54 archive snapshots from 2021-12-17 through 2026-05-21, covering 6 years; this is incomplete archival coverage and does not independently verify the current operator.

Regulatory Verification Notes

The observed site does not present a corporate identity, regulated-service description, licence claim, or registration number. Because the page is only a raw directory index, its legal and regulatory status cannot be established from the available content; this is a verification gap rather than, by itself, proof of fraud. The domain is registered through ME-NET, and its transport encryption uses a known issuer, but a domain-validated certificate confirms encrypted transport only and does not validate the operator or any regulatory permission. Evidence:

• The root page is titled “Index of /” and contains server-file listings rather than legal, terms, about, or licensing disclosures.
• WHOIS telemetry records registrar ME-NET, creation date 2016-06-01T10:51:18Z, and expiration date 2027-06-01T10:51:18Z.
• The site’s TLS certificate is issued by YR1 at DV validation level and is valid to 2026-10-11T16:15:11+00:00.

What to Verify Next

Before any sensitive interaction, an independent offline or registry-based confirmation should identify the responsible operator and establish whether the domain is intended to host a legitimate service. Any claimed licence or regulated activity should be checked directly with the relevant regulator using independently sourced records, and official contact channels should be confirmed through a separate trusted route. The exposed directory and error-log listing should also be treated as requiring technical remediation before the host can be considered suitable for business use. Evidence:

• The observed root page provides no identifiable business presentation from which operator or service purpose can be confirmed.
• The observed directory exposes PHP filenames and an `error_log`, creating a concrete basis for requesting server-configuration and exposure checks.
• No forms, login flow, payment mechanism, or service workflow was present on the captured page, so intended functionality remains unconfirmed.

Summary Verdict

The overall posture is critical trust risk, driven by confirmed external malicious detections and blacklist status combined with an unverified operating identity. The available evidence does not support treating the domain as suitable for credentials, account access, or financial interaction.

Infrastructure Integrity

The site resolves directly to hosting infrastructure operated by LiquidNet US LLC in the United States, with no CDN or WAF identified and one likely origin address visible. This provides no protective intermediary layer, and the hosting arrangement should be regarded only as infrastructure context rather than evidence of legitimacy. Evidence:

• Served from AS14555, LiquidNet US LLC, United States, using IP address 170.10.164.202; one unique IP and one likely origin IP were identified, with no CDN detected.

Closing Assessment

Sensitive interaction should be withheld unless the operator, purpose, and any claimed regulatory standing are independently established and the external detections are satisfactorily resolved.