Sicherheits-Engines melden eine Entdeckung: 8. Öffentliche Blocklisten, die eine Übereinstimmung melden: 2. Seien Sie äußerst vorsichtig – Geben Sie keine Anmeldeinformationen oder persönlichen Daten ein.
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+registry@porkbun.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.
Stored evidence for polymarket.reviews: VirusTotal recorded 4 detections among 91 scanners on 2026-09-01. 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 polymarket.reviews. Each item in this report remains at the scope supplied by its dated source record.
Detection Evidence
VirusTotal records 4 detections among 91 scanners in the stored snapshot dated 2026-09-01. 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-01 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.
Source Context
MetaMask and SEAL are recorded as named external blocklist observations for polymarket.reviews in the snapshot dated 2026-08-31. 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 polymarket.reviews 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.
Reachability and Timeline
The record first observed polymarket.reviews on 2026-08-31. The MetaMask and SEAL blocklist snapshot is dated 2026-08-31 and remains a separate event in the stored timeline. The registration date is separately recorded as 2025-12-13. A URLScan reference was stored on 2026-08-31 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.
Registration and Infrastructure
For polymarket.reviews, the registrar field records Porkbun LLC; this is kept as an exact source value. The source stores 207.207.210.36 as the observed address in this record. The registration date for polymarket.reviews is recorded as 2025-12-13. The SSL issuer is recorded as Let's Encrypt / YR1 in the snapshot dated 2026-08-31. 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.
Conclusion
The polymarket.reviews record states that VirusTotal recorded 4 detections among 91 scanners on 2026-09-01. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-08-31. PhishDestroy remains a separate publisher catalogue entry in the stored record. For polymarket.reviews, the registrar field records Porkbun LLC; this remains separate from the other source fields. The observed address field in this record contains 207.207.210.36. The supported conclusion is bounded to the exact stored observations for polymarket.reviews. Any statement beyond those source values would require additional dated material.
Recommended Actions
Avoid submitting sensitive information to polymarket.reviews during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain polymarket.reviews 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 polymarket.reviews. The stored record does not justify extending that rule to 207.207.210.36 or to other infrastructure records.
Extracted from stored page analysis
Observed indicators
19 wallet · 0 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
DOM Analysisanalyzed 09.10.2026score 95/1001 brand signal
IoC Extractionscanned 01.09.202619 wallet · 0 Telegram IoCs
Submitted URLhttp://polymarket.reviews/
Favicon Hash
Fall-ID
ICANN OVERSIGHT
Akkreditierung und RAA-Kontext
Registrar accreditation and DNS abuse obligations
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-19 01:54:34 UTC
RDAP registrationUnbekannt
Observed timelinelast reachable: 2026-10-19 01:54:34 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.
Technologien · 11 identified
S
Sanity
CMS
Sanity is a platform for structured content. It comes with an open-source, headless CMS that can be customized with Javascript, a real-time hosted data store and an asset delivery pipeline.
Amazon Web Services (AWS) is a comprehensive cloud services platform offering compute power, database storage, content delivery and other functionality.
Google Tag Manager is a tag management system (TMS) that allows you to quickly and easily update measurement codes and related code fragments collectively known as tags on your website or mobile app.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Amazon S3 or Amazon Simple Storage Service is a service offered by Amazon Web Services (AWS) that provides object storage through a web service interface.
Gespeicherte Beziehungen werden nach dem genau passenden Attribut gruppiert. Ein gemeinsam genutzter Anbieter oder Registrar allein beweist keinen gemeinsamen Besitz.
Infrastrukturkarte · polymarket.reviews
Jede Spalte gibt einen Grund an, warum eine Domain mit diesem Host verknüpft ist. Knoten in voller Größe kennzeichnen „VirusTotal“-Erkennungen, gestrichelte Knoten sind bereits offline. Die vollständigen Listen folgen weiter unten.
Inhaltliche Übereinstimmungen8
Derselbe Favicon-Hash oder derselbe Seitentitel wie bei diesem Host.
Weitere Berichte zur gemeinsamen Nutzung von Cloudflare Edge3
Diese Berichte werden auf dieselbe gemeinsame Edge-IP aufgelöst. Sie helfen bei der Berichtserkennung, bedeuten jedoch keinen gemeinsamen Besitz oder einen gemeinsamen Ursprungsserver.
Über denselben Registrar registriert. Ein Registrar betreut Millionen von Kunden, die in keiner Verbindung zueinander stehen; daher werden hier lediglich Berichte zusammengefasst, anstatt eine Verbindung nachzuweisen.
7 evidence signal groups linked1 stored notification recordsLetzter bekanntermaßen aktiv
If credentials were compromised, report immediately. Do not engage with recovery scammers.
Wenn Sie Kontoanmeldeinformationen, persönliche oder Zahlungsinformationen eingegeben oder eine Datei von dieser Domain heruntergeladen haben, ergreifen Sie sofort Maßnahmen. Nachfolgend finden Sie Ressourcen, die Ihnen helfen, den Vorfall zu melden und sich zu schützen.
Vorsicht vor Betrügern, die mit der Rückforderung von Geldern locken! Kriminelle nehmen unter Umständen erneut Kontakt zu Opfern auf und geben dabei vor, Ermittler, Anwälte oder Beitreibungsbeamte zu sein. Zahlen Sie keine Vorabgebühren und geben Sie keine Anmeldeinformationen weiter.Erfahren Sie mehr über Betrug im Zusammenhang mit Wiederaufbaumaßnahmen →
Template-based draft · optional AI wording assistance requires separate consent
KI-gestützter Entwurf – Vorfalldetails werden vom KI-Anbieter verarbeitet · Überprüfen Sie es und reichen Sie es selbst ein
After a phishing incident
Empfehlungen und Ratschläge für Betroffene
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Was soll ich sofort tun?
Dringend
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Alle Passwörter ändern — E-Mail, Exchange-Konten, alles, wofür dasselbe Passwort verwendet wird
2FA aktivieren mit einer Authentifizierungs-App (nicht per SMS). Deaktivieren Sie die SMS-basierte Wiederherstellung
Karten einfrieren Falls Sie auf der Phishing-Seite Ihre Bankdaten eingegeben haben
Welche Informationen sollte ich für meinen Bericht sammeln?
FBI-Richtlinien
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Genaue Daten und Uhrzeiten — jeder Transaktion und des ersten Kontakts mit dem Betrüger
Alle URLs und Domains die der Betrüger verwendet (einschließlich polymarket.reviews)
Kommunikation — E-Mails, SMS, Telefonnummern, Benutzernamen, die der Betrüger verwendet hat
Auch wenn dir nicht alle Details bekannt sind — trotzdem Anzeige erstatten. Auch unvollständige Informationen sind für die Ermittlungen hilfreich.
Wo soll ich den Betrugsfall melden?
FBI IC3 — Internet Crime Complaint Center (Meldestelle der US-Bundesbehörden)
Europol — Meldungen zu Cyberkriminalität in Europa (EU)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
Ortspolizei — sorgt für eine offizielle Dokumentation, auch wenn sie nicht sofort handeln können
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Schweineschlachtung — über Wochen hinweg über Telegram, WhatsApp und Dating-Apps aufgebautes Vertrauen, dann wurde Geld gestohlen
Betrugsmaschen im Zusammenhang mit der Rückforderung von Geldern — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
Durch KI gestützte Betrugsmaschen — Deepfakes, automatisiertes Phishing und KI-generierte Websites, die es erschweren, Betrugsversuche zu erkennen
Wie kann ich mich in Zukunft schützen?
Offizielle Websites als Lesezeichen speichern — Klicken Sie niemals auf Links in E-Mails, Direktnachrichten oder Anzeigen
Domains überprüfen — nachsehen, ob PhishDestroy Bevor Sie Kontakt aufnehmen: Überprüfen Sie HTTPS, die Rechtschreibung und das Alter der Domain.
„Zu schön, um wahr zu sein“ = Betrug — garantierte Renditen, Prominente als Werbeträger, dringende Fristen
Beobachten Sie aktuelle Bedrohungen oder legen Sie Widerspruch gegen diesen Eintrag ein, wenn Sie der Meinung sind, dass es sich um einen Fehlalarm handelt
About this reportSources, observation dates and corrections
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.
