VirusTotal
4 / 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 →
No stored capture is available for this domain.
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.
DBL_PHISH
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
no 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.
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.
tr.meritiking-gunceliz2.net was recorded returning HTTP status 502 on 2026-10-01, according to the HTTP check. This domain also appears in the PhishDestroy internal listing, which is a separately documented observation.
The HTTP check on 2026-10-01 recorded status 502 for tr.meritiking-gunceliz2.net. VirusTotal reported 4 detections out of 89 scanners on 2026-09-14. The domain was first observed on 2026-08-09. The SSL scan on 2026-09-14 identified Let's Encrypt / YR1 as the certificate issuer. The PhishDestroy internal listing was marked as true.
Each source provides a distinct perspective on tr.meritiking-gunceliz2.net, with the HTTP status reflecting one response, and VirusTotal offering a snapshot of detections from multiple scanners. The PhishDestroy internal listing is a publisher record, separate from external blocklists. The sequence of dated observations allows for comparison between different types of evidence without merging their scopes.
When reviewing tr.meritiking-gunceliz2.net, retain the HTTP check and VirusTotal detection records as separate evidence sources. Compare the PhishDestroy internal listing with VirusTotal results in distinct sentences to maintain clarity. Keep all dated records for reference when assessing the domain’s evidence history.
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='tr.meritiking-gunceliz2.net', port=80): Max retries exceeded with url: / (Caused by NewCon
guy.ns.cloudflare.comLocation describes the IP network.
d7e3dd22694764ece215ea166916c9abab4b432d6488f66e21fd43ae27a40876girizssabit.orgSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
8 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.
1 community report
CategoryPHISHING
Phishing / brand impersonation
“Phishing / brand impersonation”
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