2ur.jp is a phishing page detected by PhishDestroy on 2026-08-28. Risk: critical (100/100). Status: Last known active. Hosting: SAKURA Internet Inc. VirusTotal: 14/89 engines flag it. Do not enter credentials or connect a wallet.
Security engines reporting a detection: 14. Public blocklists reporting a match: 1. Exercise extreme caution — do not enter credentials or personal information.
2ur.jp presents itself as a free link-shortening and QR code service, and PhishDestroy classifies it as an impersonation phishing page. PhishDestroy first saw it on 2026-08-28. As of 2026-10-19 the site was still online and serving content. The page title advertises a "Functional" URL shortener with ShortLink and QR code creation, while our classification places the domain in the impersonation category.
How the scam works
Impersonation pages borrow the look of a trusted service or brand so that visitors lower their guard and hand over something valuable. That can be login credentials, a wallet seed phrase, or approval to connect a wallet. A shortener or QR tool is a convenient front for this, because people routinely click shortened links and scan codes without checking where they lead. Anyone who arrives here, or follows a link generated through it, may end up on a page built to capture credentials or wallet access. If that happens, the result can be a hijacked account or drained funds.
Evidence
The classification has independent backing. On 2026-09-12, 14 of 89 VirusTotal engines flagged the domain, including BitDefender, Fortinet, Forcepoint ThreatSeeker, G-Data, Gridinsoft, alphaMountain.ai, ADMINUSLabs and CyRadar. That is a meaningful minority made up of established vendors, not a single outlier. The domain also appears on the PhishDestroy and CryptoFirewall blocklists. It is referenced in 50 AlienVault OTX pulses, which shows that many researchers have tracked it in threat reporting.
Infrastructure
The domain was registered on 2024-09-03, nearly two years before PhishDestroy flagged it. That gap suggests a long-lived domain rather than a throwaway created for a single campaign. It is hosted on SAKURA Internet Inc. in Japan, which matches the country-code domain. The site serves HTTPS through a Let's Encrypt certificate, so the padlock in the browser only confirms encryption and says nothing about whether the site is safe.
What to do
Do not shorten links, scan codes or follow redirects through 2ur.jp. If you entered a password or email on a page reached through it, change that password everywhere you reuse it and turn on app-based two-factor authentication. If you typed a seed phrase, treat the wallet as compromised and move the funds to a new wallet right away. If you connected a wallet, review and revoke any token approvals you do not recognize. Defenders should block the domain at DNS and the proxy, look for historical traffic to it, and treat links from this shortener in email or chat as suspicious.
No. PhishDestroy classifies 2ur.jp as a phishing page (risk: critical, 100/100); it was first detected on 2026-08-28. VirusTotal: 14/89 engines flag it. Treat the site as unsafe.
Is 2ur.jp safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on 2ur.jp. 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 2ur.jp?
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.
Issued by Let's Encrypt· stored validity ends in 74 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
160.16.237.149
Network ASN
AS9370
Organization
SAKURA
Observed location
Tokyo, JP
Server header
Apache/2.4.37 (centos) OpenSSL/1.1.1k PHP/7.4.33
Nameservers 2
ns1.dns.ne.jp
ns2.dns.ne.jp
Mail routing 1 MX record
2ur.jppriority 10
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt
Valid from
2026-08-15 20:26:56
Valid until
2026-11-13 20:26:55
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-10-10 22:02:31 UTC
Collection source
PhishDestroy collector
Certificate fingerprinte844c149fef0c0907a9271b1961f37ae41aef17f32b8dd42a821ee94b1ec6956Certificate names · 1 SAN
2ur.jp
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-22 10:37:04 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-22 10:37:04 UTClast content: 2026-10-22 10:37:04 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.
Technologies · 8 identified
P
PHP
Programming languages
PHP is a general-purpose scripting language used for web development.
CentOS is a Linux distribution that provides a free, community-supported computing platform functionally compatible with its upstream source, Red Hat Enterprise Linux (RHEL).
OpenSSL is a software library for applications that secure communications over computer networks against eavesdropping or need to identify the party at the other end.
Bootstrap is a free and open-source CSS framework directed at responsive, mobile-first front-end web development. It contains CSS and JavaScript-based design templates for typography, forms, buttons, navigation, and other interface components.
4 evidence signal groups linked0 stored notification recordsLast known active
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 2ur.jp)
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.
