Skip to security report
Analytics Dashboard
Recorded security signals
VirusTotal: result unavailable for this observation. Listed by external blocklists: MetaMask, SEAL. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
kr-telegeram.cc favicon

kr-telegeram.cc

In short

PhishDestroy first recorded kr-telegeram.cc on 2026-11-12. VirusTotal: result unavailable for this observation. Listed by external blocklists: MetaMask, SEAL.

Review the evidence
Registrar
Hefei Juming Network T…
Resolved IP
152.32.139.249
Registered
Oct 24, 2026
First observed
Nov 12, 2026
PhishDestroy assessment High
66/100
Evidence score
First observed Nov 12, 2026 21:22 UTC · PhishDestroy
Risk signals
Stored blocklist matches: 2 Young domain: 19 days old
Blocklist matches
2
MetaMask, SEAL
URLScan
Malicious
Page captures
1
open gallery
Domain age
19 days
registered 2026-10-24 according to WHOIS
Reports sent
1
view timeline
Nov 12, 2026 1 Report Sent
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded kr-telegeram.cc on 2026-11-12. VirusTotal: result unavailable for this observation. Listed by external blocklists: MetaMask, SEAL. Risk: high (66/100). Registrar: Hefei Juming Network T…. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.

High
Blocklist matches
2
Hosting
152.32.139.249
Registrar
Hefei Juming Network T…
Registered
Oct 24, 2026
Page captures
1
Page captures Source results Registration record

Recorded source summary

PhishDestroy first observed kr-telegeram.cc on Nov 12, 2026. Current evidence score: 66/100 (high).

Positive findings are stored from 3 sources: MetaMask, SEAL, and URLScan. MetaMask and SEAL listed the hostname in the separate external-blocklist snapshot on Nov 12, 2026 at 19:20 UTC. URLScan returned a malicious verdict with score 100; scan metadata linked the capture to telegram and assigned phishing as its category on Nov 12, 2026 at 21:20 UTC.

The collector marked the hostname reachable on Nov 12, 2026 at 21:22 UTC, but did not retain the HTTP response code. Latest classified outcome: unknown; cause probe inconclusive on Nov 12, 2026 at 20:22 UTC. Registration records for the domain list Hefei Juming Network Technology Co., Ltd. as the registrar and Oct 24, 2026 as the creation date. Registration preceded first observation by 19 days. At collection time, the hostname resolved to 152.32.139.249. The stored server header is nginx. The evidence archive retains 1 visual capture from URLScan; the captures preserve the landing-page appearance. TLS metadata lists LiteSSL RSA CA 2025 as the certificate issuer with validity through Jan 23, 2027.

The record contains 3 positive source findings supporting the current phishing classification.

Source evidence 1 source

URLScan

Malicious

SHA-256 b9f5676ed90aaebb414fcf8ac71291c8c08df767a780e3a06a8f44f253afd300

Open report
URLScanOriginal source recordObserved: 19 fields

Observed: · Retrieved:

Report ID

01a1d1a2-6898-70dd-a1b7-82fea178c2ad

Final URL

https://kr-telegeram.cc/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://kr-telegeram.cc/
    From
    http://kr-telegeram.cc/
    Status
    307

IP address

152.32.139.249

Contacted IP addresses

  • 152.32.139.249

Autonomous systems (ASN)

  • 135377

Server countries

  • KR

Linked domains

  • telegram.org
  • web.telegram.org
  • desktop.telegram.org

Document hash

b9f5676ed90aaebb414fcf8ac71291c8c08df767a780e3a06a8f44f253afd300

TLS session and certificate

Subject alternative names
  • kr-telegeram.cc
Cipher
AES_256_GCM
Issuer
LiteSSL RSA CA 2025
Subject
kr-telegeram.cc
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

16

Registered domain age, days

16

Certificate age, days

18

Certificate validity, days

89

Page requests

2

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-2aab354
Score
100
Malicious
Yes
Overall verdict
Tags
  • phishing
Score
100
Brands
  • telegram
Malicious
Yes
Categories
  • phishing
URLScan verdict
Tags
  • phishing
Score
100
Brands
  • Telegram
Malicious
Yes
Categories
  • phishing

HTTP headers

Server
nginx
Content-type
text/html
Strict-transport-security
max-age=31536000
Original source fields · JSON
Uuid
01a1d1a2-6898-70dd-a1b7-82fea178c2ad
Final url
https://kr-telegeram.cc/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://kr-telegeram.cc/",
        "from": "http://kr-telegeram.cc/",
        "status": 307
    }
]
Ip
152.32.139.249
Contacted IP addresses
[
    "152.32.139.249"
]
Asns
[
    "135377"
]
Countries
[
    "KR"
]
Linked domains
[
    "telegram.org",
    "web.telegram.org",
    "desktop.telegram.org"
]
Document hash
b9f5676ed90aaebb414fcf8ac71291c8c08df767a780e3a06a8f44f253afd300
Tls
{
    "san": [
        "kr-telegeram.cc"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "LiteSSL RSA CA 2025",
    "subject": "kr-telegeram.cc",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-23T01:59:59Z",
    "valid_from": "2026-10-25T02:00:00Z"
}
Domain age days
16
Apex age days
16
Tls age days
18
Tls valid days
89
Requests
2
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-2aab354"
        ],
        "score": 100,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "telegram"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "Telegram"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "nginx",
    "content-type": "text/html",
    "strict-transport-security": "max-age=31536000"
}
Separate monitor record · date not recorded

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

record_source
domain_monitor.urlscan
uuid
01a1d1a2-6898-70dd-a1b7-82fea178c2ad
score
null
malicious
null
result_at
null
enriched_at
null
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":null}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

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

Collected source details

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

Every stored field, with its source and date

Questions about kr-telegeram.cc

Is kr-telegeram.cc legit?

PhishDestroy rates kr-telegeram.cc as high risk (66/100) from the recorded evidence; it was first recorded on 2026-11-12. VirusTotal: result unavailable for this observation. Listed by external blocklists: MetaMask, SEAL. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is kr-telegeram.cc safe to connect a wallet?

This report does not record which wallet requests kr-telegeram.cc makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.

What should I do if I used kr-telegeram.cc?

It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority; a report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Blocklist matchesMetaMask · PhishDestroy · SEAL · no match in the other 9 3
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Checked, no match

Last checked

Stored Capture · 1 capture

URLScan · 2026-11-12 1 / 1
SourceURLScan · 2026-11-12
Recorded
StateStored capture
HTTP status200
Final URLhttps://kr-telegeram.cc/
Position1 / 1
Open capture Source Report Wayback Download
All capture links and hashes (1)

Domain details

Domain
Registrar Hefei Juming Network T…
Abuse contactymn@juming.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for kr-telegeram.cc →
RegistrationCreated Oct 24, 2026 (19d · Very New!) — Expires Oct 24, 2027
Technical detailsProvenance & timestamps
First DetectedNov 12, 2026
Submitted URLhttp://kr-telegeram.cc/
TLS Certificate
Issued by LiteSSL RSA CA 2025 · stored validity ends in 71 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
152.32.139.249
Server header
nginx

Nameservers 4

  • ns1.julydns.com
  • ns1.onclouddns.com
  • ns2.julydns.com
  • ns2.onclouddns.com

TLS certificate

Issuer
LiteSSL RSA CA 2025
Valid from
2026-10-25 02:00:00
Valid until
2027-01-23 01:59:59
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate names · 1 SAN
  • kr-telegeram.cc

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

viewdns.info · 152.32.139.249rapiddns.io
Report This Domain Submit evidence & help protect others

Archived Evidence

Wayback Machine Snapshot
View Archive

Saved snapshots 1

Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://kr-telegeram.cc/
텔레그램 다운로드 | PC·안드로이드·아이폰 공식 설치 안내
텔레그램 다운로드와 설치 방법을 한눈에 확인하세요. Windows PC, Mac, Android, iPhone 및 Telegram 웹 버전의 공식 다운로드 링크와 안전한 설치 팁을 제공합니다.
Response
HTTP 200
HTML body
19.3 KB
Compressed
6.1 KB
Links
7 internal · 11 external
Detected technologies
nginx
Selected response headers
Server: nginx
Content-Type: text/html
Content-Encoding: gzip
Security headers present
Strict-Transport-Security
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Open Graph title: 텔레그램 다운로드 | 공식 설치 안내
Open Graph description: 기기에 맞는 텔레그램 공식 다운로드 경로와 설치 방법을 확인하세요.
Saved response-header values · 10
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html
Date
Thu, 12 Nov 2026 21:23:23 GMT
Etag
W/"6add79a7-4d38"
Last-Modified
Sun, 25 Oct 2026 03:38:15 GMT
Server
nginx
Strict-Transport-Security
max-age=31536000
Transfer-Encoding
chunked
Vary
Accept-Encoding

Values retained by the collector; long values may be shortened during collection.

Archived
Registration & observation details1

Availability observations

Last reachable observation

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

All stored data56

Detections & threat intelligence

Blocklist hits
PhishDestroy, MetaMask, SEAL
Blocklist count
3
Blocklist checked at
2026-11-12 20:20:02
URLScan ID
01a1d1a2-6898-70dd-a1b7-82fea178c2ad
Report count
0
User reports
0
URLScan checked at
2026-11-12 22:22:47
DOM risk score
0
URLScan captured at
2026-11-12 21:20:51
URLScan result ID
01a1d1a2-6898-70dd-a1b7-82fea178c2ad
URLScan payload hash
b9f5676ed90aaebb414fcf8ac71291c8c08df767a780e3a06a8f44f253afd300
URLScan evidence
{ "v": 1, "ip": "152.32.139.249", "ips": [ "152.32.139.249" ], "tls": { "san": [ "kr-teleg…
{
    "v": 1,
    "ip": "152.32.139.249",
    "ips": [
        "152.32.139.249"
    ],
    "tls": {
        "san": [
            "kr-telegeram.cc"
        ],
        "cipher": "AES_256_GCM",
        "issuer": "LiteSSL RSA CA 2025",
        "subject": "kr-telegeram.cc",
        "protocol": "TLS 1.3",
        "valid_to": "2027-01-23T01:59:59Z",
        "valid_from": "2026-10-25T02:00:00Z"
    },
    "asns": [
        "135377"
    ],
    "uuid": "01a1d1a2-6898-70dd-a1b7-82fea178c2ad",
    "status": 200,
    "headers": {
        "server": "nginx",
        "content-type": "text/html",
        "strict-transport-security": "max-age=31536000"
    },
    "doc_hash": "b9f5676ed90aaebb414fcf8ac71291c8c08df767a780e3a06a8f44f253afd300",
    "requests": 2,
    "task_url": "http://kr-telegeram.cc/",
    "verdicts": {
        "engines": {
            "tags": [
                "urlscan-ml",
                "urlscan-ml-2aab354"
            ],
            "score": 100,
            "malicious": true
        },
        "overall": {
            "tags": [
                "phishing"
            ],
            "score": 100,
            "brands": [
                "telegram"
            ],
            "malicious": true,
            "categories": [
                "phishing"
            ]
        },
        "urlscan": {
            "tags": [
                "phishing"
            ],
            "score": 100,
            "brands": [
                "Telegram"
            ],
            "malicious": true,
            "categories": [
                "phishing"
            ]
        }
    },
    "countries": [
        "KR"
    ],
    "final_url": "https://kr-telegeram.cc/",
    "redirects": [
        {
            "to": "https://kr-telegeram.cc/",
            "from": "http://kr-telegeram.cc/",
            "status": 307
        }
    ],
    "fetched_at": "2026-11-12T21:27:20Z",
    "redirected": "https-only",
    "scanned_at": "2026-11-12T21:20:51Z",
    "task_domain": "kr-telegeram.cc",
    "link_domains": [
        "telegram.org",
        "web.telegram.org",
        "desktop.telegram.org"
    ],
    "tls_age_days": 18,
    "apex_age_days": 16,
    "tls_valid_days": 89,
    "domain_age_days": 16
}

Network, hosting & TLS

IP address
152.32.139.249
Nameservers
ns1.julydns.com ns1.onclouddns.com ns2.julydns.com ns2.onclouddns.com
DNS resolves
Yes
TLS issuer
LiteSSL RSA CA 2025
TLS SANs
kr-telegeram.cc
TLS valid from
2026-10-25 02:00:00
TLS valid to
2027-01-23 01:59:59
Server header
nginx
CDN
No
DNS state
resolved

Registration

Registrar
Hefei Juming Network Technology Co., Ltd.
WHOIS emails
ymn@juming.com
Creation date
2026-10-24 19:04:14
Expiration date
2027-10-24 19:04:14
Registrar action verified
No
Registrar action linked to report
No
Registration state
unknown

Status, takedown & timeline

Detected at
2026-11-12 22:22:47
Status
pending
Site status
alive
Last alive
2026-11-12 22:22:47
Last checked
2026-11-12 22:22:47
Created at
2026-11-12 22:22:47
Updated at
2026-11-12 22:34:07
Outcome state
unknown
Outcome cause
probe_inconclusive
Outcome actor type
unknown
Outcome confidence
20
Outcome evidence source
current_state_backfill
Outcome evidence at
2026-11-12 22:22:47.000000
Outcome evidence
{ "reason": "", "http_status": 0, "observed_at": "2026-11-12 22:22:47", "latest_http_obser…
{
    "reason": "",
    "http_status": 0,
    "observed_at": "2026-11-12 22:22:47",
    "latest_http_observation": {
        "cause": "probe_inconclusive",
        "state": "unknown",
        "source": "http_observation",
        "mechanism": null,
        "actor_name": null,
        "actor_type": "unknown",
        "confidence": 20,
        "observed_at_utc": "2026-11-12 21:22:47",
        "availability_state": "unreachable",
        "provider_action_verified": false
    }
}
Outcome evidence at (UTC)
2026-11-12 21:22:47.000000
Availability state
unreachable
Content state
unknown
Last reachable at (UTC)
2026-11-12 21:22:47.000000
Shutdown time basis
inconclusive
Shutdown time precision
open

Page & captures

Source URL
http://kr-telegeram.cc/
Technologies
{ "urlscan": { "v": 1, "ip": "152.32.139.249", "ips": [ "152.32.139.249" ], "tls": { "san"…
{
    "urlscan": {
        "v": 1,
        "ip": "152.32.139.249",
        "ips": [
            "152.32.139.249"
        ],
        "tls": {
            "san": [
                "kr-telegeram.cc"
            ],
            "cipher": "AES_256_GCM",
            "issuer": "LiteSSL RSA CA 2025",
            "subject": "kr-telegeram.cc",
            "protocol": "TLS 1.3",
            "valid_to": "2027-01-23T01:59:59Z",
            "valid_from": "2026-10-25T02:00:00Z"
        },
        "asns": [
            "135377"
        ],
        "uuid": "01a1d1a2-6898-70dd-a1b7-82fea178c2ad",
        "status": 200,
        "headers": {
            "server": "nginx",
            "content-type": "text/html",
            "strict-transport-security": "max-age=31536000"
        },
        "doc_hash": "b9f5676ed90aaebb414fcf8ac71291c8c08df767a780e3a06a8f44f253afd300",
        "requests": 2,
        "task_url": "http://kr-telegeram.cc/",
        "verdicts": {
            "engines": {
                "tags": [
                    "urlscan-ml",
                    "urlscan-ml-2aab354"
                ],
                "score": 100,
                "malicious": true
            },
            "overall": {
                "tags": [
                    "phishing"
                ],
                "score": 100,
                "brands": [
                    "telegram"
                ],
                "malicious": true,
                "categories": [
                    "phishing"
                ]
            },
            "urlscan": {
                "tags": [
                    "phishing"
                ],
                "score": 100,
                "brands": [
                    "Telegram"
                ],
                "malicious": true,
                "categories": [
                    "phishing"
                ]
            }
        },
        "countries": [
            "KR"
        ],
        "final_url": "https://kr-telegeram.cc/",
        "redirects": [
            {
                "to": "https://kr-telegeram.cc/",
                "from": "http://kr-telegeram.cc/",
                "status": 307
            }
        ],
        "fetched_at": "2026-11-12T21:27:20Z",
        "redirected": "https-only",
        "scanned_at": "2026-11-12T21:20:51Z",
        "task_domain": "kr-telegeram.cc",
        "link_domains": [
            "telegram.org",
            "web.telegram.org",
            "desktop.telegram.org"
        ],
        "tls_age_days": 18,
        "apex_age_days": 16,
        "tls_valid_days": 89,
        "domain_age_days": 16
    }
}
Wayback saved at
2026-11-12 22:25:01

Other

AI queued
No
Indexnow sent at
2026-11-12 22:30:05

Captured network requests

Network requests: 2 SHA-256 hashes: 2 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-12 21:27 UTC.

Open this scan on URLScan 01a1d1a2-6898-70dd-a1b7-82fea178c2ad ↗

Stored observation history1

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

  1. Domain monitor · First collection record

    Reachable

All retained availability observations3

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

  1. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-12 22:22:47.000000
    Evidence SHA-256
    8b559b53b9f46bdf173545b28fd8d71bb7c5ad8be95c34a578ee38a85b9c4e35
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-12 22:22:47
    Evidence reason
  2. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-12 22:22:47.000000
    Evidence SHA-256
    8b559b53b9f46bdf173545b28fd8d71bb7c5ad8be95c34a578ee38a85b9c4e35
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-12 22:22:47
    Evidence reason
  3. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-12 11:35:23.119868
    Evidence SHA-256
    cabad2927cc72316f74a403a77154fc2bbea6e66ceaf06f086ee1e5437438f41
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-12 11:35:23.119868
    Evidence reason

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Notifications · recorded
  4. Monitoring · recorded

Recorded events: 8. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested Recorded: 1 of 1
  • Threat Ingested
    kr-telegeram.cc detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Web Archive · Blocklist Detection · Forensic Evidence Collected Recorded: 5 of 5
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan classified the page as malicious · Score: 100
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • Blocklist Detection
    Found in blocklists: MetaMask, SEAL
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
Notification RecordsSent Report Recorded Recorded: 1 of 1
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: Hefei Juming Network Technology Co., Ltd.. Abuse contacts: 1.
    • ymn@juming.com
Publication & AvailabilityDestroyList Published Recorded: 1 of 1

Recorded activity

4 entries
  1. Abuse report sent

    PD-78E848788F22889BECDD

    ymn@juming.com
  2. Wayback Machine

    Page archived

    View source
  3. Added to PhishDestroy

    kr-telegeram.cc

    View source
  4. URLScan

    Page captured

    View source
How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation
All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Check for cloaking

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

kr-telegeram.cc

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal ChainPatrol URLQuery SSL Labs Stored certificate dates valid WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-78E848788F22889BECDD Recipient: ymn@juming.com
Page title stored with report: 텔레그램 다운로드 | PC·안드로이드·아이폰 공식 설치 안내
Blocklist hits included with submission: MetaMask, SEAL
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
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?

4 evidence signal groups linked 1 stored notification records Unverified
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
More official reporting routes
FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

Report to Your Local Authorities

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

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

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.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website

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 kr-telegeram.cc)
  • 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

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 →
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.

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/kr-telegeram.cc"
  title="PhishDestroy threat report for kr-telegeram.cc"
  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>