VirusTotal
4 / 89
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
“krnl.rocks”
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.
4 / 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
ReportA 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.
0 external matches
DetailsA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.
On 2026-10-01 the domain krnl.rocks returned HTTP 302 according to the recorded HTTP check. The same evidence set records a PageSpeed performance score of 98 measured on 2026-08-13, and the domain appears in the PhishDestroy internal listing.
The domain krnl.rocks was first observed on 2026-07-27. On 2026-08-13 SSL scanning recorded Let's Encrypt / YR2 as the certificate issuer. OTX recorded three pulses on 2026-08-15. VirusTotal recorded 4 detections across 89 scanners on 2026-09-14. The registrar is Domain Science Kutatási Szolgáltató Korlátolt Felelősségű Társaság.
The PhishDestroy listing and the OTX pulses are separate named source observations, each with its own scope and date. The HTTP 302 describes only the response recorded on its check date, not all content served by krnl.rocks. The PageSpeed score reflects a single dated measurement rather than ongoing performance. Because the source dates differ, the records cannot be treated as simultaneous or directly comparable.
For krnl.rocks, preserve the PhishDestroy listing, OTX pulses, and VirusTotal detection record as separate source files. Compare the HTTP response record against the PageSpeed measurement when reassessing the domain. Recheck the VirusTotal detection record alongside the OTX pulses to see whether the named sources continue to flag krnl.rocks.
18 · datasets with records / 13 · not recorded
What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.
These checks have no retained result. This does not mean they passed or that a scan is running.
0 · external source matches
Domain Science Kutatási Szolgáltató Korlátolt Felelősségű Társaság · 103.224.182.253 · DNS, TLS and retained responses
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
5579.ns2.abovedomains.compark-mx.above.compriority 10Location describes the IP network.
4ce502faa0999044f8d85498c1720a7a6bcc9f06fc48e4bd65aa7b0865ebca27academia-profesionalizacion.comaktcom.coakubisa18.clickavcio.storebabyname.itcartonize.netcasashop.bizhdmoviesflix.ioiaphlsr.orgletpartys.buzzlullaby.lifeminhphuoc.meneoupdatephone.clubred-pack.comrochesterrockettv.comsarahmontufar.vipthemoviemod.orgwestsidelaundrydc.comSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of krnl.rocks · checked Aug 13, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Stored browser and crawler observations
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
ApacheScanner note: redirect: raw=redirect_302; http=302; via=https_proxy; location=https://expireddomains.com/domain/krnl.rocks; server=Apache
Collection history, report status and investigation channels
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
Unavailable→Reachable
Reachable→Unavailable
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
redirected→Unknown
stale_current_evidence
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
Unknown
probe_inconclusive
0→4
Reachable
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.
Shared hosting, registrar records and related domains
Original reports, independent checks and evidence links
Recovery steps, reporting contacts and complaint drafts
Listed domains receive at least one abuse report; this entry has no retained notification history.
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
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
krnl.rocks)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
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
Stored evidence snapshot. Source timestamps appear where available.
Captured title: “krnl.rocks”.
VirusTotal detections for krnl.rocks: 4 (2026-09-14 02:13:06 UTC).
Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.
submit an appeal or review the FAQ page.