VirusTotal
5 / 89
ReportInterpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
Assessment based on the stored source evidence below. Review sources →
These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.
5 / 89
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
3 community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
provider verdict: clean
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
stored report
A preserved page image documents what the collector received; a capture is not a safety verdict.
Analysis completed
ReportThis is the recorded automated analysis. Completion alone is not a safety verdict.
Checked; no threat flag recorded
ReportA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Stored narrative · generated . Provider checks below retain their own observation dates.
kr2n.cc returned an HTTP status code of 502 during a check conducted on 2026-10-01, which is the latest recorded response for this domain. The domain was first observed on 2026-08-31, establishing a clear timeline for the available evidence.
An HTTP check on 2026-10-01 recorded a status of 502 for kr2n.cc. VirusTotal reported 5 detections out of 89 scanners on 2026-09-14. OTX recorded 3 pulses as of 2026-09-10. The domain is included in the publisher-owned PhishDestroy internal listing. The registrar is Dynadot Inc, and the SSL issuer was Google Trust Services / WE1, as scanned on 2026-09-11.
The evidence covers several aspects of kr2n.cc, including HTTP response, security scanner results, and internal catalogue listing. The records from VirusTotal and OTX provide insight into how external security sources have observed the domain, while the HTTP status and internal listing offer additional context. Each source provides a unique perspective based on its own methodology and observation date.
To assess kr2n.cc, retain the HTTP status record, VirusTotal results, and OTX pulse count as separate reference points. Compare these with the PhishDestroy internal listing for a fuller understanding of the domain's recorded history. Repeating these checks in the future will allow for monitoring any changes in the domain's observed status.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='kr2n.cc', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SOCKSC
Edge-IP reputation is not attributed to this domain.
harlee.ns.cloudflare.commail.kr2n.ccpriority 10Location describes the IP network.
b89ae42d9de4c46af506c9c8e28f8332731e783b34679b0d6502d2b6710b211aSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive