VirusTotal
9 / 91
“Problem loading page”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@ionos.com.
The latest stored availability evidence still shows the domain reachable; 16 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.
9 / 91
Report stored; detailed verdict not recorded
Report4 community references
Reportprovider verdict: suspicious
Reportstored report
Report Analysis completed
ReportChecked; no threat flag recorded
ReportStored evidence for jointmeetingpoint.com: VirusTotal recorded 1 detections among 89 scanners on 2026-09-24. That ratio reproduces the stored check in its original units and is not converted into another measure. MetaMask and SEAL appear as named external blocklist observations for jointmeetingpoint.com. Each item in this report remains at the scope supplied by its dated source record.
VirusTotal records 1 detections among 89 scanners in the stored snapshot dated 2026-09-24. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-09-24 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.
MetaMask and SEAL are recorded as named external blocklist observations for jointmeetingpoint.com in the snapshot dated 2026-09-24. The stored MetaMask and SEAL blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains jointmeetingpoint.com as a publisher record. That PhishDestroy record is counted separately from the MetaMask and SEAL external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.
The record first observed jointmeetingpoint.com on 2026-09-23. The MetaMask and SEAL blocklist snapshot is dated 2026-09-24 and remains a separate event in the stored timeline. A stored HTTP status 200 was observed for jointmeetingpoint.com on 2026-09-24. The HTTP status 200 dated 2026-09-24 records a single response for later comparison. The registration date is separately recorded as 2026-09-20. A URLScan reference was stored on 2026-09-23 as a dated artifact for review. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.
For jointmeetingpoint.com, the registrar field records InterNetX GmbH; this is kept as an exact source value. The source stores 217.160.0.81 as the observed address in this record. The registration date for jointmeetingpoint.com is recorded as 2026-09-20. The SSL issuer is recorded as Sectigo Limited / Sectigo Public Server Authentication CA DV R36 in the snapshot dated 2026-09-23. The stored ASN observation records 8560 and IONOS SE in this record. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.
The jointmeetingpoint.com record states that VirusTotal recorded 1 detections among 89 scanners on 2026-09-24. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-09-24. PhishDestroy remains a separate publisher catalogue entry in the stored record. For jointmeetingpoint.com, the registrar field records InterNetX GmbH; this remains separate from the other source fields. The observed address field in this record contains 217.160.0.81. The supported conclusion is bounded to the exact stored observations for jointmeetingpoint.com. Any statement beyond those source values would require additional dated material.
Avoid submitting sensitive information to jointmeetingpoint.com during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain jointmeetingpoint.com as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and MetaMask and SEAL blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to jointmeetingpoint.com. The stored record does not justify extending that rule to 217.160.0.81 or to other infrastructure records.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/+W1Zsn1_cRKM5ZDQ0Stored page referenceIoC extraction recorded 2026-09-24 04:00:15 UTC
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
ApacheScanner note: alive_content: raw=ok; http=200; via=https_direct; server=Apache
docks12.rzone.deshades19.rzone.desmtp.rzone.depriority 5Location describes the IP network.
84a77cda1d4c39e0bf04b1c2e6ae56843cd5a1578bc8e338775bd27f0d8dc65dwww.jointmeetingpoint.comSaved 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 jointmeetingpoint.com · checked Sep 23, 2026
217.160.0.81. 13 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.
79 stored lookalike domains
PD-20260923-1421D4 Recipient: abuse@ionos.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 (NL): Dutch Criminal Code - Article 326 (Computer Fraud) Dutch Criminal Code - Article 326c (Phishing) GDPR Netherlands law explicitly criminalizes phishing and computer fraud. 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