VirusTotal
5 / 89
“BABE”
The sent-report ledger records the first outgoing report at .
The recorded recipient is compliance@tucows.com.
The latest stored availability evidence still shows the domain reachable; 2 months 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.
5 / 89
DBL_SPAM
checked — no detections recorded
Report3 community references
Reportprovider verdict: clean
Reportstored report
Report Analysis completed
ReportChecked; no threat flag recorded
ReportOn 2026-10-01, plug.contact returned an HTTP status 200 according to a recorded check, indicating a successful response was observed on that date. The domain also appears in the PhishDestroy internal listing, a catalogue record held by the publisher.
A check on 2026-10-01 recorded HTTP status 200 for plug.contact. VirusTotal, checked on 2026-09-21, reported 5 detections out of 89 scanners. OTX, checked on 2026-08-21, recorded 3 pulses for this domain. The domain was first observed on 2026-08-10, with a PageSpeed performance score of 94 also recorded that day. The SSL certificate, issued by Let's Encrypt / YR2, was scanned on 2026-08-10, and registration was through Tucows Domains Inc. on 2026-01-06.
These records provide observations from different sources, each reflecting the state of plug.contact at specific times. The HTTP status documents the response observed on its check date, while VirusTotal and OTX provide security and reputation data from their respective platforms. The inclusion in the PhishDestroy internal listing is a separate publisher record. Each source offers a distinct perspective without indicating any overall conclusion about the domain.
For plug.contact, retain the HTTP response, VirusTotal detection results, and OTX pulse count as individual records for future reference. Compare subsequent HTTP checks to the recorded status for changes. Review the PhishDestroy catalogue entry alongside other source records, and keep the PageSpeed and SSL certificate details available for comparison with future observations.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/MAJESTIC_GOODSStored page referencehttps://t.me/b4b3_gen_botStored page referenceIoC extraction recorded 2026-08-11 04:00:07 UTC
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
nginx/1.18.0 (Ubuntu)Scanner note: alive_content: raw=ok; http=200; via=https_proxy; server=nginx/1.18.0 (Ubuntu)
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.
1-you.njalla.no2-can.njalla.in3-get.njalla.foLocation describes the IP network.
433b3c9a025d67865dd3e16dc362b90c7a89ac826674ddbbeff74fd34f735f8dSaved 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 plug.contact · checked Aug 10, 2026
80.78.23.46. 14 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-20260810-C357B4 Recipient: compliance@tucows.com Registrar: Tucows Domains Inc (Canada) Policy Violations: Participates in DNS Abuse Framework; explicitly recognizes phishing, malware, botnets, pharming, spam-as-vector as abuse requiring registrar action Applicable Laws: Criminal Code §342.1 (unauthorized access), §380 (fraud)
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