ABUSE NOTICE · 7D+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@spaceship.com.
The latest stored availability evidence still shows the domain reachable; 26 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.
kehilot.net returned HTTP status 200 in an HTTP check dated 2026-10-01, a recorded response that does not by itself establish present availability or content. The domain was first observed on 2026-09-17, and a PhishDestroy internal listing is also recorded for it.
Recorded Evidence
An OTX check dated 2026-09-19 recorded 5 pulses for kehilot.net. VirusTotal, checked 2026-09-29, recorded 15 detections across 91 scanners, with observation time known marked false. The domain's registration date is 2011-04-22 under registrar Spaceship, Inc., and an SSL scan dated 2026-09-18 recorded the issuer as Let's Encrypt / R13. The IP address 154.83.186.199 is recorded in NL under Datagear LLP.
Interpretation
The OTX pulses, VirusTotal detections, and PhishDestroy listing are separate source records with different collection dates, so their counts should be read individually rather than merged into one score or trend. The HTTP 200 response describes only the response recorded on its check date, not all content served by the domain. The first-observed date and later checks show a sequence of observations, but the differing dates alone do not demonstrate a change in the domain's state.
Recommended Actions
For kehilot.net, preserve the PhishDestroy listing, the OTX pulse record, and the VirusTotal result as separate source records for later comparison. Compare the HTTP response record against future HTTP checks of kehilot.net, and compare the VirusTotal detection count against later VirusTotal scans. Retain the SSL scan record alongside these sources so each dated observation remains traceable.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observation内容在线Ordinary HTTP content served90%2026-10-14 10:06:21 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-14 10:06:21 UTClast content: 2026-10-14 10:06:21 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-09-17 18:40:38 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 154.83.186.199.
威胁响应 Pipeline
发现
Analysis
Notifications
Monitoring
11 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.
Web Archive
Preserved in 互联网档案馆 — historical evidence archived
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.
PDF notice generated Notice text archived (650 chars)
Abuse notice text as sent to the provider
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.
