VirusTotal
16 / 91
“Powered by CapRover”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@digitalocean.com.
The latest stored availability evidence still shows the domain reachable; 23 days 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.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| Quad9 DNS | sefa14.com |
malicious | Sinkholed |
| DNS4EU | sefa14.com |
malicious | Sinkholed |
| OpenDNS | sefa14.com |
phishing | Phishing Block |
| DigiCert UltraDNS | sefa14.com |
malicious | Sinkholed |
| Cloudflare DNS | sefa14.com |
malicious | Sinkholed |
sefa14.com was recorded with an HTTP status 200 on 2026-10-01, indicating a successful response at that time. The domain is also listed in the PhishDestroy internal catalogue, providing an additional source for review.
The domain was first observed on 2026-09-17, coinciding with an OTX check that reported 4 pulses. VirusTotal, on 2026-09-29, recorded 16 detections out of 91 scanners. The HTTP check on 2026-10-01 confirmed a status 200 response. The registrar is Realtime Register B.V., and the SSL certificate issuer was CapRover.com / caprover.com as of 2026-09-17.
These source records reflect separate observations, each with its own date and focus. The OTX pulses and VirusTotal detections provide distinct perspectives on the domain, while the PhishDestroy internal listing offers a publisher-specific catalogue entry. Chronological details allow for comparison between the first observation, subsequent checks, and the recorded HTTP response.
For sefa14.com, retain the OTX pulse count and VirusTotal detection results as distinct records for ongoing review. Compare the PhishDestroy internal listing with these source observations to inform any future assessment. Revisit the HTTP response in subsequent checks and keep all dated results for reference.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='sefa14.com', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SOC
ns1.hosting.com.trns2.hosting.com.trsefa14.compriority 0Location describes the IP network.
d46e7b5d915fd74f31d1548e2f1759886649886ba97e39269ca4e8ec5aa9e422Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
134.199.244.50. 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.
PD-20260917-98AE5C Recipient: abuse@digitalocean.com Policy Violations: Illegal Activities: Active phishing operation targeting victims Fraud & Deception: Impersonation of legitimate services Identity Theft: Collection of credentials under false pretenses Applicable Laws (Unknown): International Anti-Cybercrime Regulations Budapest Convention on Cybercrime Universal Fraud Prevention Laws Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws. Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
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
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