btint46826.wcard.me is a phishing page detected by PhishDestroy on 2026-10-23. Risk: critical (95/100). Registrar: GoDaddy. Status: Last known active. Hosting: DigitalOcean, LLC. VirusTotal: 15/92 engines flag it. Do not enter credentials or connect a wallet.
PhishDestroy added btint46826.wcard.me to its internal blocklist on 2026-10-23 based on a trusted intake report. The prior automated assessment on the same day could not determine malicious behavior because the page content was insufficient for analysis. The recorded page title reads “Bt Internet - Important Notice from Bt”. An HTTP 200 response was observed on 2026-10-23.
How the scam works
The detections label the domain as phishing, a category where attackers impersonate legitimate brands to lure users into revealing credentials or personal data. The page title suggests an attempt to appear as an official notice from the brand “Bt”, but no specific credential‑collection form or malicious payload was observed. Without concrete evidence of a particular technique, the risk remains the generic threat of brand‑spoofing phishing.
Evidence
VirusTotal scanned the domain on 2026-10-20 and reported 15 malicious detections out of 92 engines, with vendors such as BitDefender, ESET and Fortinet flagging it as phishing. Google Safe Browsing checked the URL on 2026-10-23 and did not flag it. urlscan.io captured the site on 2026-10-03; its machine‑learning engine gave a malicious score of 61, but the overall verdict was clean. Cloudflare Radar scanned the site on 2026-10-23 and marked it malicious with a phishing category. OTX listed zero pulses on the same day, and no external blocklists reported the domain.
Infrastructure
The recorded observation showed the domain pointed to 165.232.181.150, which was hosted by DigitalOcean, LLC in Bengaluru, India, and used a Let’s Encrypt certificate for HTTPS. The domain was created 446 days ago and its apex domain is 1,576 days old; the TLS certificate was issued on 2026-09-21 and expires on 2026-12-20. Nameservers are ns1‑ns3.digitalocean.com and DNSSEC is not enabled.
What to do
If you entered any login credentials on the site, change those passwords immediately and enable multi‑factor authentication where possible. Monitor associated accounts for unauthorized activity and consider blocking the domain at the network perimeter. Defenders should add btint46826.wcard.me to web filtering rules and review server logs for any requests to the recorded IP address.
{
"ogUrl": "https://btint46826.wcard.me",
"title": "Bt Internet - Important Notice from Bt",
"ogType": "website",
"robots": "noindex,nofollow",
"ogImage": "https://wcardcdn.b-cdn.net/api/og/image.jpg",
"ogTitle": "Bt Internet - Important Notice from Bt",
"description": "Digital Business Card of Bt Internet Important Notice from Bt",
"twitterCard": "summary",
"twitterSite": "@officialwcard",
"canonicalUrl": "https://btint46826.wcard.me",
"ogDescription": "Digital Business Card of Bt Internet Important Notice from Bt"
}
No. PhishDestroy classifies btint46826.wcard.me as a phishing page (risk: critical, 95/100); it was first detected on 2026-10-23. VirusTotal: 15/92 engines flag it. Treat the site as unsafe.
Is btint46826.wcard.me safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on btint46826.wcard.me. 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 btint46826.wcard.me?
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.
Registration (base domain)wcard.me · Created Aug 1, 2023 —Expires Aug 1, 2028
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 23, 2026
DOM Analysisanalyzed Oct 23, 2026score 0/100
Submitted URLhttp://btint46826.wcard.me/
Favicon Hash
Observed page title
Bt Internet - Important Notice from Bt
TLS Certificate
Issued by Let's Encrypt / YR2· stored validity ends in 57 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
165.232.181.150
Network ASN
AS14061
Organization
DigitalOcean, LLC
Observed location
Bengaluru, IN
Server header
Apache
Nameservers 3
ns1.digitalocean.com
ns2.digitalocean.com
ns3.digitalocean.com
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt / YR2
Valid from
2026-09-21 13:12:24
Valid until
2026-12-20 13:12:23
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprinta1ed56d167a45b6737323f124cdb911d82136579591ebf35cfe2d6bc4bd802b5Certificate names · 2 SANs
*.wcard.me
wcard.me
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
3 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 btint46826.wcard.me)
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.
(US)
