Skip to security report
Analytics Dashboard
Domain security and threat intelligence
slon6.id favicon

slon6.id

In short

slon6.id is a Kraken impersonation page detected by PhishDestroy on 2026-09-14. Risk: critical (81/100). Registrar: PT Jagoan Hosting Indo…. Hosting: Cloudflare, Inc. PhishDestroy sent 1 abuse report. VirusTotal: 4/91 engines flag it. Do not enter credentials or connect a wallet.

“Captcha | KRAKEN MARKET | ВХОД НА ДАРКНЕТ САЙТ КРАКЕН”

Registrar
PT Jagoan Hosting Indo…
Resolved IP
104.21.88.108
Registered
Apr 14, 2026
PhishDestroy assessment Critical
First observed Sep 14, 2026 21:22 UTC · PhishDestroy
Risk signals
VirusTotal detections: 4/91 Automated brand label: Kraken
OTX: 4 refs Sep 14, 2026 1 Report Sent CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 4. Exercise extreme caution — do not enter credentials or personal information.
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is care@jagoanhosting.id. The latest stored availability evidence still shows the domain reachable; 1 month has elapsed since the first outgoing report.

ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.

Elapsed since first report
1 month
Reports sent
1
Latest case ID
PD-20260914-8FC898
Current status
Observed active at latest stored check
VirusTotal
4 / 91
engine detections
Google Safe Browsing
No threat flag
OTX
4
community references
Page captures
5
open gallery
Domain age
191 days
Reports sent
1
view timeline
Source evidenceVirusTotal 4 / 91 · OTX 4 references 6 sources

VirusTotal

4 / 91 engine detections

Open report

URLQuery

checked — no detections recorded

Open report

OTX

4 community references

Open report

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

Open report

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

Critical
VirusTotal
4 / 91
OTX
4 community refs
Page captures
5
Page captures Source results Registration record

PhishDestroy threat report

Overview

slon6.id is a phishing page that uses the Kraken name and opens with a captcha screen titled "Captcha | KRAKEN MARKET | ВХОД НА ДАРКНЕТ САЙТ КРАКЕН". The Russian-language title targets people searching for a way to log in to a site called Kraken. PhishDestroy first detected the domain on 2026-09-14. As of 2026-10-19 the domain still responded, but its DNS no longer pointed to working page content.

How the scam works

The page title presents the site as an entrance to the Kraken darknet market rather than the Kraken cryptocurrency exchange, while we classified it as Kraken impersonation. Lookalike login gateways of this kind usually show a fake captcha first, so the visitor feels they have reached the real entry point. They then present a copied login form. Anything typed there, including usernames, passwords and one-time codes, goes to the operators. Any cryptocurrency sent to deposit addresses shown on the page is lost and cannot be recovered.

Evidence

Detection by independent vendors is low. On 2026-09-27, 4 of 91 VirusTotal engines flagged the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker and SOCRadar. The domain appears in 4 AlienVault OTX threat pulses, so other researchers have also tagged it. PhishDestroy is currently the only blocklist carrying it. Many browsers and security tools may therefore still let users reach it without a warning.

Infrastructure

The domain was registered on 2026-04-14 through PT Jagoan Hosting Indonesia under the Indonesian .id extension. It was detected five months later, which suggests it was registered early and kept in reserve before being put to use. Traffic passes through Cloudflare, Inc. on an address geolocated to Canada. Because Cloudflare acts as a proxy, the server that actually hosts the page is not visible from outside. The short numbered name "slon6" fits a pattern of disposable domains that can be swapped quickly when one gets blocked.

What to do

If you entered a username or password on this page, change it right away on the genuine service and on any other site where you reused it. Then turn on or reset two-factor authentication. Do not send cryptocurrency to any address this page displayed, and treat any balance you already sent as lost. Security teams should block slon6.id at DNS and proxy level and watch for sibling domains with similar numbered names. Abuse reports to Cloudflare and to the registrar can help get the domain taken down.

Useful links

urlscan.io scan and screenshotVirusTotal reportGoogle Safe Browsing statusArchived copyReport phishing to GoogleSite owner? Request a review

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

URLScan · 2026-09-14T21:21:25Z

Observed: · Retrieved:

Uuid
01a0a1cb-b88a-753c-b0ee-faa509789ff6
Final url
https://slon6.id/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://slon6.id/",
        "from": "http://slon6.id/",
        "status": 307
    },
    {
        "to": "https://slon6.id/",
        "from": "https://slon6.id/"
    }
]
Ip
172.67.176.230
Contacted IP addresses
[
    "172.67.176.230"
]
Asns
[
    "13335"
]
Document hash
e1c831f821121942bcf451bd77649b0cba6d0400032ab3245147ba6ec30b9ac9
Script hashes
[
    "10a50430d5ba794708dc4279299ca9c73e281ab09fe2847e2b55f68c21177cc8"
]
Globals
[
    "slowAES",
    "toNumbers",
    "toHex",
    "a",
    "b",
    "c"
]
Cookies
[
    "check_bot",
    "kraken_pm",
    "TCK"
]
Tls
{
    "san": [
        "slon6.id",
        "*.slon6.id"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WE1",
    "subject": "slon6.id",
    "protocol": "QUIC",
    "valid_to": "2026-11-12T14:18:30Z",
    "valid_from": "2026-08-14T13:19:57Z"
}
Domain age days
31
Apex age days
31
Tls age days
31
Tls valid days
90
Requests
5
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 94,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=UTF-8",
    "x-powered-by": "PHP/8.5.0",
    "strict-transport-security": "max-age=15552000; includeSubDomains; preload"
}
Cloudflare Radar · 2026-09-14T21:54:59Z

Observed: · Retrieved:

Uuid
5b1b1f0c-d457-4257-ab23-9645932e4c2b
Final url
https://slon6.id/
Status
200
History
[
    {
        "url": "https://slon6.id/",
        "status": 200
    },
    {
        "url": "https://slon6.id/",
        "status": 200
    },
    {
        "url": "https://slon6.id/",
        "status": 200
    }
]
DOM structure hash
0c5b87dccedda8936e1089e2cf7a46f0ec1fcdc68f08fcec260d7c4ac631c4b5
Document hash
72848a20c02da99667e164a4f4e729cb5c38ae55c4389aa2b8bef304292d599f
Phishing v2
[
    "phishing"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "slon6.id",
        "type": "A",
        "value": "104.21.88.108"
    },
    {
        "name": "slon6.id",
        "type": "A",
        "value": "172.67.176.230"
    },
    {
        "name": "slon6.id",
        "type": "AAAA",
        "value": "2606:4700:3032::ac43:b0e6"
    },
    {
        "name": "slon6.id",
        "type": "AAAA",
        "value": "2606:4700:3037::6815:586c"
    }
]
Dnssec valid
false
Ip
104.21.88.108
Registration record
{
    "registrar": "PT Jagoan Hosting Indonesia",
    "created": "2026-04-14T08:40:00Z",
    "updated": "2026-08-14T14:15:30Z",
    "expires": "2027-04-14T23:59:59Z",
    "nameservers": [
        "kyle.ns.cloudflare.com",
        "sara.ns.cloudflare.com"
    ]
}
VirusTotal · 2026-10-05T03:33:51Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 54,
    "malicious": 4,
    "suspicious": 0,
    "undetected": 34
}
Vendor labels
{
    "CRDF": "malicious",
    "SOCRadar": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
First seen
2026-06-22T01:43:45Z
DNS records
[
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3032::ac43:b0e6"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "kyle.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.176.230"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3037::6815:586c"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "sara.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.88.108"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "kyle.ns.cloudflare.com"
    }
]
Dns at
2026-09-27T02:00:45Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "slon6.id",
        "*.slon6.id"
    ],
    "issuer": "Google Trust Services / WE1",
    "serial": "c0d4210e86e8d9870ecb2c185c886399",
    "sha256": "73618bfedc8ae00d4df62b4e7ee0ce431cbfcaca1f217f34620aef6da8fe4dba",
    "subject": "slon6.id",
    "valid_to": "2026-11-12T14:18:30Z",
    "valid_from": "2026-08-14T13:19:57Z"
}

Questions about slon6.id

Is slon6.id legit?

No. PhishDestroy classifies slon6.id as a Kraken impersonation page (risk: critical, 81/100); it was first detected on 2026-09-14. VirusTotal: 4/91 engines flag it. Treat the site as unsafe.

Is slon6.id safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on slon6.id. 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 slon6.id?

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.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 5 captures

Primary capture 1 / 5
SourcePrimary capture
Recorded2026-09-14 21:22 UTC
StateStored capture
Position1 / 5
Open capture Wayback Download

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-09activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar PT Jagoan Hosting Indo… (Unknown)
Abuse contactcare@jagoanhosting.id
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for slon6.id →
RegistrationCreated Apr 14, 2026 (191d) — Expires Apr 14, 2027
Technical detailsProvenance & timestamps
First DetectedSep 14, 2026
DOM Analysisanalyzed Sep 15, 2026score 81/1001 brand signal
Submitted URLhttp://slon6.id/
Favicon Hash
Case ID
Observed page title
Captcha | KRAKEN MARKET | ВХОД НА ДАРКНЕТ САЙТ КРАКЕН
Automated brand references
Kraken
TLS Certificate
Issued by Google Trust Services / WE1 · stored validity ends in 20 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
104.21.88.108
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • kyle.ns.cloudflare.com
  • sara.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-08-14 13:19:57
Valid until
2026-11-12 14:18:30
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-10-20 16:02:22 UTC
Collection source
PhishDestroy collector
Certificate fingerprint73618bfedc8ae00d4df62b4e7ee0ce431cbfcaca1f217f34620aef6da8fe4dba
Certificate names · 2 SANs
  • slon6.id
  • *.slon6.id

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 104.21.88.108rapiddns.io

Latest Classified Outcome 2026-10-21 14:53:36 UTC

Primary outcome DNS inactive reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Unknown Probe Inconclusive 20% 2026-10-22 10:11:59 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-09-29 22:18:44 UTC current episode first observed: 2026-09-30 16:14:55 UTC observed RIP window: 2026-09-29 22:18:44 UTC → 2026-09-30 16:14:55 UTC · 17.94h midpoint estimate ≈ 2026-09-30 07:16:49 UTC · precision medium · 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 · 5 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

4 / 91 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 4 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
SOCRadar

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Registration & observation details8

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
17.94
Estimate basis
Bounded by observations
Estimate precision
Medium

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

slon6.id
Saved result
Unreachable
Stored observation history20

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

Earlier observations 15
  1. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  6. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  7. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  8. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  9. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  10. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  11. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  12. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  13. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  14. VirusTotal · Detection count

    2→4

  15. Availability monitor · First collection record

    Reachable

Recorded activity

6 entries
  1. AlienVault OTX

    4 community references

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. VirusTotal

    4/91 engine detections

    View source
  4. Abuse report sent

    PD-20260914-8FC898

    care@jagoanhosting.id
  5. Added to PhishDestroy

    slon6.id

    View source
  6. URLScan

    Page captured

    View source

Lookalike domains

114 stored lookalike domains

krakden.com insertion Internal report krakend.com addition Internal report krakenj.com addition Internal report xn--kaken-6o1b.com homoglyph Internal report xn--kran-xva5q.com homoglyph Internal report xn--krken-ucc.com homoglyph Internal report xn--krken-yqa.com homoglyph Internal report ikraken.com insertion jkraken.com insertion kaken.com omission karken.com transposition keaken.com replacement
Show all (88)
kkraken.com repetition kr2aken.com insertion kraaken.com repetition kraekn.com transposition kraen.com omission kraiken.com insertion krak3n.com replacement krake.com omission krakeb.com replacement krakeen.com repetition krakeh.com replacement krakencom.com various krakewn.com insertion krakien.com insertion krakin.com vowel-swap krakjen.com insertion krakken.com repetition krakn.com omission krakne.com transposition krakon.com vowel-swap krakren.com insertion krakrn.com replacement krakwen.com insertion krakwn.com replacement kralen.com replacement kramen.com replacement kreaken.com insertion krkaen.com transposition krken.com omission kroken.com vowel-swap krraken.com repetition krsken.com replacement kruken.com vowel-swap kryken.com replacement ktaken.com replacement lkraken.com insertion lraken.com replacement mkraken.com insertion mraken.com replacement okraken.com insertion raken.com omission rkaken.com transposition craken.com bitsquatting jraken.com bitsquatting k-raken.com hyphenation k2aken.com bitsquatting kbaken.com bitsquatting kpaken.com bitsquatting kra-ken.com hyphenation kracen.com bitsquatting krajen.com bitsquatting krak-en.com hyphenation krakan.com bitsquatting krakel.com bitsquatting kraken1.com addition kraken2.com addition kraken3.com addition kraken4.com addition kraken5.com addition kraken6.com addition kraken7.com addition kraken8.com addition kraken9.com addition krakena.com addition krakenc.com addition krakene.com addition krakenf.com addition krakeng.com addition krakenh.com addition krakeni.com addition krakenk.com addition krakenl.com addition krakenn.com addition krakeno.com addition krakenr.com addition krakens.com addition krakent.com addition krakenv.com addition krakenx.com addition krakeny.com addition krakenz.com addition kraker.com homoglyph krakgn.com bitsquatting krakmn.com bitsquatting krakun.com bitsquatting kreken.com bitsquatting kriken.com bitsquatting kvaken.com bitsquatting

Showing 100 of 114

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 4 det. ChainPatrol URLQuery Report stored SSL Labs Stored certificate dates valid CF Radar Open report OTX 4 refs WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20260914-8FC898 Recipient: care@jagoanhosting.id
Page title stored with report: Captcha | KRAKEN MARKET | ВХОД НА ДАРКНЕТ САЙТ КРАКЕН
PDF notice generated
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback Archived
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

6 evidence signal groups linked 1 stored notification records Unverified
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.

Immediate steps Find reporting contacts

Official reporting routes

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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 →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

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 slon6.id)
  • 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)
  • Europol — European cybercrime reporting (EU)
  • 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

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
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.

Request a correction or appeal How PhishDestroy works
Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/slon6.id"
  title="PhishDestroy threat report for slon6.id"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>