VirusTotal
16 / 91 engine detections
PhishDestroy first recorded special.services on 2025-12-18. Stored VirusTotal result: 16/91 engines flagged.
Page title: “Special Services | special.services”
Stored VirusTotal result: 16/91 engines flagged. Use caution — do not enter credentials or personal information.
Risk score, higher = worse · How this score works
Pick what happened and tick the steps as you go. The ticks are kept only in this browser.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
PhishDestroy analysis, earlier unreviewed version
The capture of special.services, taken on 2026-01-17, shows a default WordPress 404 error page titled "Oops! That page can't be found." The page offers two identical search forms as its main interaction, alongside standard sidebar sections for recent posts, archives, categories, and a Meta list containing a Log in link. The footer reads "Special Services. Proudly powered by WordPress."
VirusTotal analysis retrieved on 2026-09-26 shows 16 of 91 engines flagged the domain, including BitDefender and Kaspersky. The scan scope was not preserved in the record, so it cannot be confirmed as a domain-level scan.
16 / 91 engine detections
5 det.
Open report5/100
Trust score, lower = worse
Open report50 community references
Open reportScan report
Open reportPage capture
Open reportSeparate stored monitor snapshot; does not replace the primary report record or establish current availability.
98 / 100 · heuristic score · 0 brand references · 1 classification
Content heuristic only; not the final score
Open reportThis dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.
Narrative generation metadata
Open reportThe narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.
Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
Stored page, network and scanner observations, grouped by source and observation time.
PhishDestroy rates special.services as critical risk (evidence score 100/100) from the recorded evidence; it was first recorded on 2025-12-18. Stored VirusTotal result: 16/91 engines flagged. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on special.services. A confirmed blockchain transaction cannot be reversed.
Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned. Step-by-step help: emergency guide.
Separate monitor record
b06561d27b196838e52c617efdd87eb484fcdbead06d9b1ac81bddbe82c53ff2 · 510660 bytes 76cc8b95bd2c49d4e4a76eb18ece275181a6c1993fcb3a0e248850ce3bbcbfac · 23089 bytes f65918cafdc7de8c0853fb666dbc7bca0c76a0529d0b40876f966c7d1bac4c26 · 161906 bytes b27fdd491fe444e00582ced17396c9c9d0dbdeed886a7e955fc7a36feb9c33d0 · 23844 bytes 47ea25013d16ec9cfea866cd634031cc053e3880222a84c2dc0ddf063254471b · 478895 bytes 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.
dns1.name-services.comdns2.name-services.comdns3.name-services.comdns4.name-services.comdns5.name-services.commx.special.services.cust.a.hostedemail.compriority 10Location describes the IP network.
79ee1a1c7c99c458bd990edf71c21a405f089d3f334894d0f8e81c2dd550dd4cspecial.servicesSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
The site was redirecting visitors elsewhere at the latest check.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Network requests: 12 SHA-256 hashes: 9 URLScan scan:
Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-29 07:11 UTC.
Open this scan on URLScan 019bcb6d-7b9d-76be-84fe-126b65ad7ffa ↗
Loads saved data; the suspicious site is not opened.
| # | Network request | HTTP method · status | Type | Uncompressed size | Response body SHA-256 |
|---|
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
Our scanner could not complete this check.
special.services Source: domain_monitor. This stored snapshot does not establish current availability.
Recorded events: 13. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Lifecycle
Reported 3795 d 10 h after registration
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.
Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.
Download all records as JSON| ID | Stored data |
|---|
Reported by 1 community member, first seen 2025-12-18
Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.
The draft stays only with you.
First secure your money: call your bank or revoke wallet approvals. Immediate steps →
Emergency help from security researchers when a crypto wallet is being drained right now.
Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.
Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.
Forward scam emails and text messages to the National Cyber Security Centre, which takes down the malicious sites it finds.
Emailreport@phishing.gov.uk Text messages7726Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.
Forward phishing emails to the Anti-Phishing Working Group.
Emailreportphishing@apwg.orgNational Cyber Crime Reporting Portal. For financial fraud, also call the 1930 helpline straight away.
Helpline1930Choose 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 ↗
special.services)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
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.