VirusTotal
17 / 91
Interpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
“Checkout”
Assessment based on the stored source evidence below. Review sources →
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@omegatech.sc.
The latest stored availability evidence still shows the domain reachable; 28 days 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.
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.
17 / 91
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
5 threat-system alerts
ReportAlerts refer to the preserved scan. They do not describe the current state of the site.
provider verdict: malicious
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
DBL_PHISH
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
5 community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
stored report
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.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DigiCert UltraDNS | relaysession.com |
malicious | Sinkholed |
| Quad9 DNS | relaysession.com |
malicious | Sinkholed |
| Cloudflare DNS | relaysession.com |
malicious | Sinkholed |
| DNS4EU | relaysession.com |
malicious | Sinkholed |
| OpenDNS | relaysession.com |
phishing | Phishing Block |
relaysession.com returned an HTTP status 200 during a check on 2026-10-01, indicating a successful response was recorded on that date. The domain is also listed in the PhishDestroy internal catalogue, which is a publisher-owned reference.
An HTTP check on 2026-10-01 recorded status 200 for relaysession.com. VirusTotal, checked on 2026-09-29, reported 17 detections out of 91 scanners. OTX, checked on 2026-09-19, recorded 5 pulses for the domain. The domain was first observed on 2026-09-16, and a PageSpeed check on the same date recorded a performance score of 98. The SSL certificate was scanned on 2026-09-17 and issued by Let's Encrypt / YR2. The registrar is TUCOWS.COM, CO., with registration recorded on 2026-04-07.
The source records from HTTP, VirusTotal, and OTX each provide distinct technical and catalogue information about relaysession.com, reflecting different aspects and dates. The PhishDestroy internal listing and OTX pulses indicate the domain appears in multiple catalogue-based records, while the HTTP, PageSpeed, and SSL results document technical checks without describing specific content.
Preserve the HTTP status record for relaysession.com and the VirusTotal detection report as separate references for future review. Compare the OTX pulse count with the PhishDestroy internal listing to monitor catalogue entries over time. Retain the PageSpeed and SSL scan results for technical context in subsequent evaluations.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
nginx/1.14.1Scanner note: alive_content: raw=ok; http=200; via=https_proxy; server=nginx/1.14.1
1-you.njalla.no2-can.njalla.in3-get.njalla.foLocation describes the IP network.
c84a98ae444310d4b1062b55da366cc70384683b2b2008f445a5bfc335e474bcSaved 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 relaysession.com · checked Sep 16, 2026
91.92.241.145.12 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.
PD-20260916-BC0D25 Recipient: abuse@omegatech.sc Policy Violations: Illegal Activities: Active phishing operation targeting victims Fraud & Deception: Impersonation of legitimate services Identity Theft: Collection of credentials under false pretenses Applicable Laws (KN): International Anti-Cybercrime Regulations Budapest Convention on Cybercrime Universal Fraud Prevention Laws Phishing activities violate international cybercrime conventions and KN's domestic fraud laws. Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
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