Security engines reporting a detection: 3. Public blocklists reporting a match: 3. Exercise extreme caution — do not enter credentials or personal information.
SSL certificate is invalid or expired. Issuer: Google Trust Services / WE1
Evidence Summary
Critical
VirusTotal
3/91
OTX
2 community refs
URLScan
Stored capture
This domain, multiplier-saturn.credit, is flagged as a generic phishing site targeting cryptocurrency users. Analysis indicates it operates as a credential harvester and wallet drainer, likely leveraging cloned interfaces of legitimate wallet services to deceive victims into entering private keys or seed phrases. The infrastructure shows no direct brand impersonation, but the use of generic terms like 'multiplier' and 'saturn' suggests an attempt to appear as a yield-boosting or staking platform, a common tactic in crypto-themed phishing campaigns. Technical indicators confirm the domain's malicious nature. multiplier-saturn.credit has a VirusTotal detection score of 3/95, with security vendors identifying it as a phishing threat. It was registered on June 10, 2026, through PDR Ltd. d/b/a PublicDomainRegistry.com, and resolves to the IP address 172.67.182.133, hosted on AS13335 (Cloudflare, Inc.). The domain appears on 4 security blocklists and is actively blocked by multiple transaction monitoring systems. Its SSL certificate is issued by Google Trust Services (WE1), a common choice for phishing sites due to its free availability and perceived legitimacy. As of the latest verification, multiplier-saturn.credit remains active and continues to resolve to its Cloudflare-hosted IP. The domain's creation date in 2026 suggests either a typo-squatting attempt or an error in registration records, but its operational status and blocklist presence confirm ongoing malicious activity. Users are advised to treat any interaction with this domain as high-risk, particularly links or scripts referencing it in crypto-related contexts. Network-level blocking of the IP 172.67.182.133 and monitoring for related domains registered through the same registrar are recommended defensive measures. The domain's use of Cloudflare complicates takedown efforts, but reporting to the registrar and certificate authority may aid in disruption.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not observedNo cloaking was observed in the stored scan
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not observed
Cloaking score
0/6
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='multiplier-saturn.credit', port=80): Max retries exceeded with url: / (Caused by NewConnec
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
RegistrationCreated Jun 10, 2026 (125d)—Expires Jun 10, 2027
Time to First Unavailability2 days
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedJun 10, 2026
DOM Analysisanalyzed Jun 11, 2026score 88/100
Submitted URLhttp://multiplier-saturn.credit/
Case ID
ICANN OVERSIGHT
Accreditation and RAA context
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.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-13 01:10:43 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-07-02 10:03:50 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-07-02 10:03:50 UTC → 2026-09-30 16:14:55 UTC · 2,166.18hmidpoint estimate ≈ 2026-08-16 13:09:22 UTC · precision very low · basis bounded
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.
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
multiplier-saturn.credit detected and queued for full analysis
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Jun 13, 2026
Time to First Unavailability
57 hours elapsed from detection to the first unavailable observation.
How we investigate & report
Public scans, evidence and abuse channels
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.
6 evidence signal groups linked1 reports recordedContent unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · multiplier-saturn.credit
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Same registrar: PDR6
Registered through the same registrar. A registrar serves millions of unrelated customers, so this groups reports rather than proving a link.
