Skip to security report
Analytics Dashboard
Domain security report
ameus.cc favicon

ameus.cc

Threat verdict
CriticalDomain Appeal
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Availability Last known active Latest stored reachability observation Observed · HTTP probe
Risk signals
VirusTotal detections: 13/89 Spamhaus DBL: DBL_SPAM Scam type: Impersonation Google Safe Browsing: threat flag recorded
OTX: 3 refs Sep 9, 2026 1 Report Sent
API
Registrar
CNOBIN INFORMATION TEC…
Resolved IP
66.198.225.39
Registered
Apr 24, 2026
2 sources
The capture source is temporarily unavailable.
1 / 2
Source
Primary capture
Collected · UTC
Open capture
In this reportGet help
This domain has been flagged as malicious
Security engines reporting a detection: 13. Exercise extreme caution — do not enter credentials or personal information.
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@verisign-grs.com. The latest stored availability evidence still shows the domain reachable; 1 month 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.

Elapsed since first report
1 month
Reports sent
1
Latest case ID
PD-1788907628-ameus.cc
Current status
HTTP 301 at latest stored check

Additional indicators at a glance

Spamhaus DBL
DBL_SPAM
VirusTotal
VirusTotal
13 det.
OTX references
3 community refs
URLScan
URLScan
Report ↗
TLS Certificate
Within stored validity dates
Let's Encrypt / YE1 · Hostname coverage not recorded
Age
6 mo
Observed status
Last known active 301
PhishDestroy
DestroyList
Listed
Reports Sent
1

Source evidence

8 · sources

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.

VirusTotal

13 / 89

Report
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

Google Safe Browsing

Threat flag recorded

Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Spamhaus DBL

DBL_SPAM

Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

OTX

3 community references

Report
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

CF Radar

provider verdict: clean

Observation time not recorded
Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

URLScan capture

stored report

View stored capture ↗
Report
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

URLScan verdict

Analysis completed

Report
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

Public blocklists

0 external matches

Details
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Evidence Summary

Critical
VirusTotal
13/89
OTX
3 community refs
URLScan
Stored capture

AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.

Assessment

The domain ameus.cc returned an HTTP status 301 on 2026-10-09, documenting a redirect response at that time. Google Safe Browsing also recorded a flag for social engineering on 2026-09-22, providing another dated observation relevant to the domain's profile.

Recorded Evidence

VirusTotal recorded 13 detections out of 89 scanners for ameus.cc on 2026-09-15. OTX referenced the domain in three pulses on 2026-09-15. Google Safe Browsing flagged the domain for social engineering on 2026-09-22. The domain was listed internally by PhishDestroy as of 2026-10-09.

Interpretation

PhishDestroy contains an internal listing for ameus.cc, which documents its inclusion in the publisher's catalogue. VirusTotal provides a measurement of external scanner detections, offering a perspective on how the domain was assessed by multiple sources. OTX records pulse activity, reflecting its presence in external intelligence entries. These sources present a range of observations that can be compared over time.

Recommended Actions

Retain the PhishDestroy internal listing and VirusTotal scanner results for ameus.cc for future reference. Compare the Google Safe Browsing and OTX records to monitor for any changes in external intelligence entries. Use these dated records to inform ongoing analysis and track new observations related to the domain.

Data coverage & collection

19 · datasets with records / 12 · not recorded

What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.

Recorded dataPartial recordUTC
VirusTotal
13 / 89 · engine detections
URLScan analysis
Automated verdict retained
Google Safe Browsing
Threat flag recorded
OTX publications
3 · community references
External blocklists
0 · external matches
Cloudflare Radar
cleanCollection time not recorded
Spamhaus DBL
DBL_SPAM
Domain registration
CNOBIN INFORMATION TECHNOLOGY LIMITEDCollection time not recorded
Network & DNS
66.198.225.39 · 1 · nameserversCollection time not recorded
TLS certificate
Let's Encrypt / YE1
Page captures
2 · retained captures
Page analysis
0 · automated brand labels
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
Response records
1 · outgoing report records
Availability history
30 · stored state changes
Source observation history
4 · stored source events
IP reputation
Network-level observations
Wayback archive
Archive link retained
Not recorded in this report 12

These checks have no retained result. This does not mean they passed or that a scan is running.

  • URLQuery
  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • HTML archives
  • Site configuration files
  • PageSpeed performance
  • Recorded subdomains
  • Lookalike relationships
  • Community reports
  • Chainabuse records
Download the dated observations and supporting metadata.

Blocklist records

0 · external source matches

Public Blocklist Status

Domain, network & archive

CNOBIN INFORMATION TECHNOLOGY LIMITED · 66.198.225.39 · DNS, TLS and retained responses

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
Google Safe Browsing Flagged Social engineering checked Sep 22, 2026
IP Reputation abuse score 2/100 1 report PhishingBad Web Bot checked Oct 9, 2026
OTX tags 2026-09activeall-domainsblocklistcontentcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
Registrar CNOBIN INFORMATION TEC… VN(VN)
Abuse contact["abuse@ordertld.com"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for ameus.cc →
RegistrationCreated Apr 24, 2026 (176d) — Expires Apr 24, 2027
HTTP Status301 Moved Permanently
Technical detailsProvenance & timestamps
First DetectedSep 9, 2026
DOM Analysisanalyzed Sep 17, 2026score 100/100
Favicon Hash
Case ID

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
66.198.225.39
Network ASN
AS402253
Organization
SKN-NETWORK-1 - SKN Subnet & Telecom Ltd, KN
Observed location
Edinburg, US
Server header
Caddy
Nameservers 1
  • ns2.nameserverhub.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-09-06 03:49:57
Valid until
2026-12-05 03:49:56
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection time
2026-10-09 13:03:25 UTC
Collection source
PhishDestroy collector
Certificate fingerprint3dea6551ba17e6eaa432531d92e321b650e5f4d552c3b7f27be8b7903dd377be

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 66.198.225.39rapiddns.io

Latest Classified Outcome 2026-10-17 10:12:46 UTC

Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-17 10:12:46 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-17 10:12:46 UTC
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.
Technologies · 1 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

13 / 89 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 13 detections
alphaMountain.ai
BitDefender
CRDF
CyRadar
Forcepoint ThreatSeeker
Fortinet
G-Data
Google Safe Browsing
Gridinsoft
Kaspersky
Lionic
SOCRadar
Sophos

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Registration & observation details2

Availability observations

Last reachable observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Detection & evasion checks

Stored browser and crawler observations

Detection-evasion analysis

Cloaking and traffic-distribution check

Not yet scanned No crawler-versus-browser difference has been recorded yet

Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.

Stored cloaking flag
Not yet scanned
Last cloaking scan
Server header seen by scanner
Caddy

Scanner note: redirect: raw=redirect_301; http=301; via=http_proxy; location=https://ameus.cc/; server=Caddy

Live TDS fingerprint check
Seven Keitaro fingerprints and a browser-versus-crawler comparison. A new scan starts only when you press the button.
Saved result
Cloaked / Filtered

Timeline & response

1 · outbound report records

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
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.
  1. VirusTotal Detections Update 2026-09-10 21:38:17 UTC
    Source: VirusTotal
    Event details
    VirusTotal scanner detections updated from 12 to 13. Added scanner alerts: Gridinsoft.
  2. VirusTotal Detections Update 2026-09-08 23:53:19 UTC
    Source: VirusTotal
    Event details
    VirusTotal scanner detections updated from 11 to 12. Added scanner alerts: SOCRadar.
  3. Status Check 2026-09-08 22:49:44 UTC
    Source: PhishDestroy monitoring
    Event details
    Telemetry event observed.
  4. Threat First Observed 2026-09-08 22:48:53 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as unknown.
Stored observation history34

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  2. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  3. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  4. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  5. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

Earlier observations 29
  1. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  2. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  3. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  4. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  5. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  6. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  7. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  8. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  9. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  10. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  11. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  12. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  13. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  14. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  15. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  16. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  17. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  18. Availability monitor · Recorded state

    redirected→Unknown

    stale_current_evidence

  19. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  20. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  21. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  22. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  23. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  24. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  25. Availability monitor · Recorded state

    Unknown

    probe_inconclusive

  26. VirusTotal · Detection count

    12→13

  27. VirusTotal · Detection count

    11→12

  28. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

  29. Availability monitor · First collection record

    Unknown

Threat Response Pipeline

Discovery
Analysis
Notifications
Monitoring

14 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Threat Ingested
ameus.cc detected and queued for full analysis
Sep 9, 2026
Spamhaus DBL
Spamhaus DBL recorded DBL_SPAM
Oct 9, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
Sep 9, 2026
Cloudflare Radar Report
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.
Web Archive
Preserved in Wayback Machine — historical evidence archived
Sep 23, 2026
VirusTotal
13/89 recorded on VirusTotal
Sep 15, 2026
Google Safe Browsing
Flagged via Google Transparency Report
Sep 22, 2026
OTX Community References
3 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
Oct 16, 2026
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
Sep 9, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 17, 2026
VT Detection +1
+1 new detection (12 → 13): Gridinsoft
Sep 10, 2026
VT Detection +1
+1 new detection (11 → 12): SOCRadar
Sep 9, 2026
Initial Abuse Report (#1)
Sent to 2 abuse contacts at CNOBIN INFORMATION TECHNOLOGY LIMITED with forensic evidence
abuse@verisign-grs.comcompliance@icann.org
Sep 9, 2026
DestroyList Published
Listed in the public PhishDestroy/DestroyList repository
Sep 9, 2026
Monitoring Continues
The domain remains reachable or access-restricted; future checks may update this 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
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. 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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Related infrastructure

Shared hosting, registrar records and related domains

Evidence & investigation tools

Original reports, independent checks and evidence links

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 13 det. ChainPatrol URLQuery Google SB Flagged SSL Labs Hostname coverage not recorded CF Radar Open report OTX 3 refs WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-1788907628-ameus.cc Recipient: abuse@verisign-grs.com
PDF notice generated
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback Archived
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Were You Affected by This Site?

5 evidence signal groups linked 1 stored notification records Last known active
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.

Immediate steps Find reporting contacts
Official reporting routes
PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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 →
Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

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
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including ameus.cc)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
Read the evidence in context

About This Report: ameus.cc

Stored evidence snapshot. Source timestamps appear where available.

VirusTotal detections for ameus.cc: 13 (2026-09-15 17:56:14 UTC).

Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.

submit an appeal or review the FAQ page.

Embed this report

A compact widget with a link to the evidence

HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/ameus.cc"
  title="PhishDestroy threat report for ameus.cc"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>