84.95.177.78.forward.012.net.il is a blocklisted domain detected by PhishDestroy on 2026-08-09. Risk: high (65/100). Status: Content unavailable. Hosting: Partner Communications Ltd. VirusTotal: 3/89 engines flag it. Do not enter credentials or connect a wallet.
Resolved IP
84.95.177.78
PhishDestroy assessment
High65/100Evidence score
Availability
Content unavailableContent was unavailable in the latest observationObserved · HTTP probe
84.95.177.78.forward.012.net.il is on the PhishDestroy blocklist as a suspicious domain. It is not a branded lookalike. The name embeds a raw IPv4 address under an Israeli provider's domain, the pattern ISPs use for hostnames tied to individual connections. PhishDestroy first recorded it on 2026-08-09. The site went offline on 2026-09-13 and was still unreachable with DNS inactive at the last check on 2026-10-19.
How the scam works
No impersonated brand, page title or phishing kit is tied to this host, so it cannot be pinned to a specific scheme. What the evidence does show is that security vendors treat it as a source of malicious or phishing content. Hosts like this usually serve a page that either collects logins and personal details or pushes visitors toward an action that hands control of an account or wallet to the operator. The danger lies in whatever was entered or approved while the page was live.
Evidence
On 2026-09-16, VirusTotal showed 3 of 89 engines flagging the host: CRDF, Forcepoint ThreatSeeker and VIPRE. That is a thin but independent signal from three separate vendors, and it supports our listing rather than establishing a firm verdict. PhishDestroy is the only blocklist carrying it. The low count means many browsers and filters would not have warned visitors while the site was up.
Infrastructure
The address 84.95.177.78 belongs to Partner Communications Ltd. in Israel. The 012.net.il hostname is generated by the provider for that address rather than registered separately, which points to content served from a connection inside the provider's network rather than from a purpose-bought domain. The host went dark about five weeks after PhishDestroy first saw it.
What to do
If you entered a password or other login details on this host, change that password, change it anywhere you reused it, and enable app-based two-factor authentication. If you connected a crypto wallet or signed anything there, review and revoke unfamiliar token approvals, and move funds to a fresh wallet if you shared a seed phrase. If you only visited, scan the device for unwanted downloads. Defenders should block the hostname and 84.95.177.78 at the proxy and DNS layer, search logs for past connections, and report renewed activity to Partner Communications' abuse contact.
{
"Sophos": "information technology",
"BitDefender": "business",
"Forcepoint ThreatSeeker": "phishing and other frauds"
}
First seen
2026-07-30T22:15:14Z
Registration record
{
"dnssec": "unsigned"
}
Questions about 84.95.177.78.forward.012.net.il
Is 84.95.177.78.forward.012.net.il legit?
No. PhishDestroy classifies 84.95.177.78.forward.012.net.il as a blocklisted domain (risk: high, 65/100); it was first detected on 2026-08-09. VirusTotal: 3/89 engines flag it. Treat the site as unsafe.
Is 84.95.177.78.forward.012.net.il safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on 84.95.177.78.forward.012.net.il. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
What should I do if I used 84.95.177.78.forward.012.net.il?
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
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.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-21 01:58:30 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-15 22:17:47 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-15 22:17:47 UTC → 2026-09-30 16:14:55 UTC · 353.95hmidpoint estimate ≈ 2026-09-23 07:16:21 UTC · precision 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.
Hello,
I am reporting an extortion and sextortion scam email that was delivered from IP address 84.95.177.78.
The SMTP headers show:
Sending IP: 84.95.177.78
Reverse hostname: 84.95.177.78.forward.012.net.il
Date received: 27 July 2026 at 16:02:27 UTC
Subject: Openstaande beta
Check for cloaking
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
1 report filed for 84.95.177.78.forward.012.net.il (1 written by a person) · category: Sextortion · source checked
“Hello,
I am reporting an extortion and sextortion scam email that was delivered from IP address 84.95.177.78.
The SMTP headers show:
Sending IP: 84.95.177.78
Reverse hostname: 84.95.177.78.forward.012.net.il
Date received: 27 July 2026 at 16:02:27 UTC
Subject: Openstaande betaling.
Message-ID: 001901dd1dfa$02b534c4$6dea87b1$@lbs4.nl
Bitcoin address demanded by the sender: 13DxNrjxWh5wsXYkTMrvih2wdkKTHUx4G1
The sender spoofed both the From and Return-Path addresses using my domain. SPF did no”
— reported by Anonymous on Jul 28, 2026 · Source: ChainAbuse (TRM Labs) — full report and evidence there.
1 evidence signal groups linked0 stored notification recordsContent unavailable
Listed domains receive at least one abuse report; this entry has no retained notification history.
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
After a phishing incident
Recommendations & Advice for Victims
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
What should I do immediately?
Urgent
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Change all passwords — email, exchange accounts, anything that shares the same password
Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
Freeze cards if you entered banking details on the phishing site
What information should I collect for my report?
FBI guidelines
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.
Exact dates & times — of each transaction and first contact with scammer
Screenshots — scam website, chat messages, emails, wallet transactions, social media
All URLs & domains used by the scammer (including 84.95.177.78.forward.012.net.il)
Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
FBI IC3 — Internet Crime Complaint Center (US federal reporting)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
Local police — creates an official record, even if they can't act immediately
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Bookmark official sites — never click links from emails, DMs, or ads
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
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.
