VirusTotal
17 / 91
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
“resorte capitencia | a premium AI | Official Website”
Assessment based on the stored source evidence below. Review sources →
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@dynadot.com.
The latest stored availability evidence still shows the domain reachable; 1 month has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.
17 / 91
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
5 threat-system alerts
ReportAlerts refer to the preserved scan. They do not describe the current state of the site.
provider verdict: malicious
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
5 community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
stored report
View stored capture ↗ ReportA preserved page image documents what the collector received; a capture is not a safety verdict.
Analysis completed
ReportThis is the recorded automated analysis. Completion alone is not a safety verdict.
Checked; no threat flag recorded
ReportA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
0 external matches
DetailsA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| OpenDNS | resortecapitencia.pro |
phishing | Phishing Block |
| Cloudflare DNS | resortecapitencia.pro |
malicious | Sinkholed |
| DigiCert UltraDNS | resortecapitencia.pro |
malicious | Sinkholed |
| DNS4EU | resortecapitencia.pro |
malicious | Sinkholed |
| Quad9 DNS | resortecapitencia.pro |
malicious | Sinkholed |
AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.
resortecapitencia.pro returned HTTP status 200 in a check recorded on 2026-10-01, the most recent dated response in this evidence set. The same domain was first observed on 2026-09-15, roughly two weeks earlier, and a PageSpeed performance score of 70 was recorded that day.
The domain resortecapitencia.pro was first observed on 2026-09-15, and its PageSpeed performance score of 70 was recorded the same day. An SSL scan on 2026-09-15 identified the issuer as ZeroSSL GmbH / ZeroSSL ECC DV SSL CA 2. OTX was checked on 2026-09-17 and returned 5 pulses. VirusTotal, checked on 2026-09-29, reported 17 detections across 91 scanners. The HTTP check on 2026-10-01 returned status 200, and the publisher-owned PhishDestroy catalogue listed the domain. Registration data records Dynadot Inc and a registration date of 2026-07-12.
These records describe separate observations made by different sources on different dates, so each should be read on its own terms rather than combined into a single conclusion. The OTX pulses and VirusTotal detections are distinct source metrics with different collection methods, and the evidence does not establish that they describe the same underlying activity. The chronology from first observation through the later HTTP check shows only that checks occurred on those dates, not that the domain's behavior changed between them.
Preserve the resortecapitencia.pro records from OTX, VirusTotal, and the PhishDestroy catalogue as separate source artifacts for later comparison. Compare the OTX pulses against the VirusTotal detections in separate reviews rather than merging them into one score. Retain the HTTP response record alongside the PageSpeed observation so future checks can be compared against the same dated baselines.
21 · datasets with records / 10 · not recorded
What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.
These checks have no retained result. This does not mean they passed or that a scan is running.
0 · external source matches
Dynadot Inc · 185.62.58.179 · DNS, TLS and retained responses
arely.ns.cloudflare.commemphis.ns.cloudflare.comLocation describes the IP network.
564a26b5833753295d236dc231b145a761557bddb8e8ae168b9965377aa76362Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of resortecapitencia.pro · checked Sep 15, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Stored browser and crawler observations
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: alive_content: raw=ok; http=200; via=https_proxy
No live-check result has been retained.
1 · outbound report records
185.62.58.179.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
live_content→Unknown
stale_current_evidence
Unknown→live_content
content_served
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
Unknown
probe_inconclusive
Reachable
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
Shared hosting, registrar records and related domains
Original reports, independent checks and evidence links
PD-20260915-9E146D Recipient: abuse@dynadot.com Registrar: Dynadot LLC / Dynadot Inc (United States) Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
Recovery steps, reporting contacts and complaint drafts
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
resortecapitencia.pro)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
Stored evidence snapshot. Source timestamps appear where available.
Captured title: “resorte capitencia | a premium AI | Official Website”.
VirusTotal detections for resortecapitencia.pro: 17 (2026-09-29 02:19:14 UTC).
Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.
submit an appeal or review the FAQ page.