Security engines reporting a detection: 10. Public blocklists reporting a match: 3. Exercise extreme caution — do not enter credentials or personal information.
Adguard Default Adguard Family Cloudflare Family Cloudflare Security Controld Adblock Controld Family Controld Malware Mullvad Adblock Opendns Standard Quad9 Secure
Evidence Summary
Critical
VirusTotal
10/93
URLScan
Stored capture
The domain syncpages.support was registered on February 21, 2026 through Dynadot LLC and currently resolves to IP address 186.2.166.73, which is assigned to AS59692 IQWeb FZ-LLC in the United Arab Emirates. The authoritative name servers are pns41.cloudns.net, pns42.cloudns.net, pns43.cloudns.net, and pns44.cloudns.net, and the MX record is configured to localhost. An SSL certificate presented by the site lists PhishDestroy and botadmin.destroy.tools as the issuer, indicating possible reuse of compromised certificate infrastructure. HTTP requests return a 200 status code and the page title is "Index of /", providing no additional context about the payload. The domain is classified as generic_phishing with a high risk rating and is associated with a tech support scam campaign. Reputation metrics show a Gridinsoft trust score of 0 out of 100, and the domain appears on four security blocklists, including PhishDestroy, Polkadot, Enkrypt, and Codeesura. VirusTotal analysis shows that 10 of 93 scanned security vendors flagged the domain as malicious. Defenders should immediately block DNS resolution for syncpages.support, add the IP 186.2.166.73 to network deny lists, and monitor for any outbound connections to the listed name servers. Continuous threat intelligence feeds should be consulted for updates, and incident response teams should treat any related alerts as high priority given the confirmed active status and the technical support fraud context.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not observedNo cloaking was observed in the stored scan
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not observed
Cloaking score
0/6
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='syncpages.support', port=80): Max retries exceeded with url: / (Caused by NewConnectionErr
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedFeb 26, 2026
DOM Analysisanalyzed Jul 9, 2026score 80/100
ICANN OVERSIGHT
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
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.
Accreditation is a contract, not a safety certification.
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-13 01:12:54 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-07-09 02:12:57 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-07-09 02:12:57 UTC → 2026-09-30 16:14:55 UTC · 2,006.03hmidpoint estimate ≈ 2026-08-19 21:13:56 UTC · precision very low · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
syncpages.support detected and queued for full analysis
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Mar 15, 2026
Time to First Unavailability
390 hours elapsed from detection to the first unavailable observation.
How we investigate & report
Public scans, evidence and abuse channels
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.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
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.
5 evidence signal groups linked0 reports recordedContent unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · syncpages.support
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
(US)
