kra61.gl is a blocklisted domain detected by PhishDestroy on 2026-09-07. Risk: high (66/100). Status: Content unavailable. Hosting: Cloudflare, Inc. VirusTotal: 4/89 engines flag it. Do not enter credentials or connect a wallet.
“kra61.gl”
Resolved IP
104.21.3.245
Registered
Oct 10, 2025
PhishDestroy assessment
High66/100Evidence score
Availability
Content unavailableContent was unavailable in the latest observationObserved · HTTP probe
kra61.gl was a phishing site built to impersonate a legitimate service and catch people who believed they had reached the real one. PhishDestroy first flagged it on 2026-09-07. The site went offline on 2026-09-16, and when it was checked again on 2026-10-19 its DNS was still inactive. It was online for roughly nine days after we flagged it.
How the scam works
Impersonation pages copy the look, wording and flow of a real platform, then wait for visitors arriving from search ads, chat links or mistyped addresses. Anything typed in, such as usernames, passwords, one-time codes, card numbers or recovery details, goes straight to the operators, who can use it to take over the genuine account. The page title showed nothing more than the bare domain name and gave no hint of a brand. That is consistent with a short-lived page that never builds a public identity.
Evidence
On 2026-09-17, four of 89 VirusTotal engines marked the domain as malicious: alphaMountain.ai, CRDF, Fortinet and SOCRadar. That is a small share, but four unrelated vendors reached the same verdict independently, which supports our classification. The domain also appears in three AlienVault OTX threat pulses, so other researchers were tracking it. Among blocklists, it is listed by PhishDestroy.
Infrastructure
The site sat behind Cloudflare, Inc., on an address geolocated to Canada, so the real origin server stays hidden. Its HTTPS certificate came from Google Trust Services, an automated issuer that serves countless legitimate sites. A padlock in the address bar therefore said nothing about whether this page was genuine. The .gl country-code ending is uncommon for mainstream services, and that alone should have raised suspicion.
What to do
If you entered a password on kra61.gl, change it right away on the real service and on every other account that shares it. Then turn on app-based two-factor authentication and sign out all active sessions. If you typed card or bank details, contact your bank to block the card and dispute any charges you do not recognise. Watch your inbox for follow-up messages that cite this visit, because operators often return with fake support or recovery offers. Defenders should block the domain at DNS and proxy level and search logs for any traffic to it between 2026-09-07 and 2026-09-16. They should also stay alert for lookalike domains built on the same naming pattern.
No. PhishDestroy classifies kra61.gl as a blocklisted domain (risk: high, 66/100); it was first detected on 2026-09-07. VirusTotal: 4/89 engines flag it. Treat the site as unsafe.
Is kra61.gl safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on kra61.gl. 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 kra61.gl?
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.
RegistrationCreated Oct 10, 2025 —Expires Oct 10, 2026
Time to First Unavailability8 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 DetectedSep 7, 2026
Observed page title
kra61.gl
TLS Certificate
Issued by Google Trust Services / WE1· stored validity ends in 26 days
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
104.21.3.245
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare
Edge-IP reputation is not attributed to this domain.
Nameservers 2
deb.ns.cloudflare.com
shane.ns.cloudflare.com
Location describes the IP network.
TLS certificate
Issuer
Google Trust Services / WE1
Valid from
2026-08-19 18:14:08
Valid until
2026-11-17 19:13:50
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-09-15 19:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprintaae5bd6307d3f1fa090f05a3873a11e2cd344a1000186c8be92b857a5b041888Certificate names · 2 SANs
kra61.gl
*.kra61.gl
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-21 01:18:53 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-07 16:28:10 UTCcurrent episode first observed: 2026-10-15 20:22:19 UTCobserved RIP window: 2026-09-07 16:28:10 UTC → 2026-10-01 01:39:25 UTC · 561.19hmidpoint estimate ≈ 2026-09-19 09:03:47 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.
Technologies · 2 identified
Cloudflare
CDN
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
4 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 kra61.gl)
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.
