Stored registration data identifies Trustname / Fewmoretaps OÜ (IANA 4318) as the registrar. PhishDestroy maintains a separate registrar investigation; that material is contextual and is not an independent detection for this domain.
karemex.com was first observed on 2026-10-08, with a VirusTotal scan reporting 1 detection from 92 scanners on 2026-10-04. The domain is also listed in the PhishDestroy internal catalogue, which reflects its inclusion in internal monitoring records.
Recorded Evidence
VirusTotal checked karemex.com on 2026-10-04, recording 1 detection out of 92 scanners. OTX noted 4 pulses for the domain as of 2026-10-08. The domain was registered with Fewmoretaps OU d/b/a Trustname.com on 2026-08-13. PhishDestroy internal listing was recorded on 2026-10-08.
Interpretation
The source observations indicate that karemex.com has been tracked by multiple security platforms, including VirusTotal, OTX, and PhishDestroy. These dated records show that monitoring began shortly after the domain's registration, but do not describe the domain's content or specific activity. The presence of a detection and catalogue listing suggests ongoing attention from internal and external sources.
Recommended Actions
For karemex.com, it is advisable to retain all records from VirusTotal, OTX, and PhishDestroy for future comparison. Review these sources regularly to track any changes or new observations. Continued monitoring is recommended to ensure that any updates in security findings are promptly identified.
スキャナーに関する注記:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='karemex.com', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SO
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observation不明Probe Inconclusive20%2026-10-11 10:07:54 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 01:41:07 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Threat First Observed2026-10-08 02:17:49 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 172.67.163.174.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
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.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
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.
(BY)
PhishDestroy Investigation
