Security engines reporting a detection: 5. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
Stored evidence for fizjupiter.com: VirusTotal recorded 4 detections among 90 scanners on 2026-09-04. 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 fizjupiter.com. Each item in this report remains at the scope supplied by its dated source record.
Detection Evidence
VirusTotal records 4 detections among 90 scanners in the stored snapshot dated 2026-09-04. 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-04 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 fizjupiter.com in the snapshot dated 2026-09-13. 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 fizjupiter.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.
Reachability and Timeline
The record first observed fizjupiter.com on 2026-08-15. The MetaMask and SEAL blocklist snapshot is dated 2026-09-13 and remains a separate event in the stored timeline. A stored HTTP status 403 was observed for fizjupiter.com on 2026-09-13. The HTTP status 403 dated 2026-09-13 records a single response for later comparison. 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 fizjupiter.com, the registrar field records HOSTINGER operations, UAB; this is kept as an exact source value. The source stores 76.13.73.5 as the observed address in this record. The SSL issuer is recorded as Let's Encrypt / YE1 in the snapshot dated 2026-09-11. 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 fizjupiter.com record states that VirusTotal recorded 4 detections among 90 scanners on 2026-09-04. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-09-13. PhishDestroy remains a separate publisher catalogue entry in the stored record. For fizjupiter.com, the registrar field records HOSTINGER operations, UAB; this remains separate from the other source fields. The observed address field in this record contains 76.13.73.5. The supported conclusion is bounded to the exact stored observations for fizjupiter.com. Any statement beyond those source values would require additional dated material.
Recommended Actions
Avoid submitting sensitive information to fizjupiter.com during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain fizjupiter.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 fizjupiter.com. The stored record does not justify extending that rule to 76.13.73.5 or to other infrastructure records.
Detection-evasion analysis
Cloaking suspected: scanner and visitor titles differ
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
RegistrationCreated Aug 14, 2026 (57d · New)—Expires Aug 14, 2029
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedAug 15, 2026
Favicon Hash
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
76.13.73.5
Network ASN
AS47583
Organization
Hostinger US
Observed location
Asheville, US
Server header
LiteSpeed
Nameservers 1
nebula.dns-parking.com
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt / YE1
Valid from
2026-08-14 15:46:08
Valid until
2026-11-12 15:46:07
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-11 07:02:03 UTC
Collection source
PhishDestroy collector
Certificate fingerprint68b26c85fec8c0435995ff81fc48603a769de86ab343ab17a72aad6d982c64b1Certificate names · 1 SANs
www.fizjupiter.com
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 observationLive contentOrdinary HTTP content served90%2026-10-11 10:23:50 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-11 10:23:50 UTClast content: 2026-10-11 10:23:50 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.
Last analyzed First positive detection Previous stored snapshot: 4 detections
alphaMountain.ai
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
SOCRadar
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
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.
Domain Status Transition2026-09-29 01:52:28 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-09-08 10:00:29 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-02 23:33:11 UTC
Domain ingestion complete. Initial state is marked as alive.
Threat Response Pipeline
Discovery
Analysis
Monitoring
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
fizjupiter.com detected and queued for full analysis
Aug 15, 2026
Spamhaus DBL
Spamhaus DBL recorded DBL_PHISH
Oct 3, 2026
Cloudflare Radar Report
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.
The domain remains reachable or access-restricted; future checks may update this 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.
2 evidence signal groups linked0 reports recordedLast known active
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 · fizjupiter.com
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.
Content matches4
Same favicon hash or the same page title as this host.
(LT)
