VirusTotal
11 / 91 engine detections
Open reportPhishDestroy first recorded colinsapii.digital on 2026-02-21. VirusTotal: 11/91 engines flag it. Listed on Spamhaus DBL.
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; 8 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.
PhishDestroy rates colinsapii.digital as critical risk (98/100) from the recorded evidence; it was first recorded on 2026-02-21. VirusTotal: 11/91 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.
This report does not record which wallet requests colinsapii.digital makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.
It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. 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.
11 / 91 engine detections
Open reportSuspicious
Open reportObserved: · Retrieved:
| Uuid | 4d599db7-39e7-4f23-9473-15e90e6c291e |
|---|---|
| Final url | https://colinsapii.digital/ |
| Status | 403 |
| History | [
{
"url": "https://colinsapii.digital/",
"status": 403
}
] |
| DOM structure hash | b9524eddac1ba274c9d05bf8c6720c6e967e6331726bd4195410aad6c92b4f83 |
| Document hash | 8548215da9bc3fa053e973155fb99462a65aea8b9ee8f6419a1d2c11ca0189f6 |
| Domain risks | [
"Newly Seen Domains",
"Security Risks"
] |
| DNS records | [
{
"name": "colinsapii.digital",
"type": "A",
"value": "178.16.52.147"
}
] |
| Dnssec valid | true |
| Ip | 178.16.52.147 |
| Registration record | {
"registrar": "Unstoppable Domains Inc",
"created": "2026-02-05T10:32:05Z",
"updated": "2026-02-10T10:32:55Z",
"expires": "2027-02-05T10:32:05Z",
"nameservers": [
"ns-cloud-b1.googledomains.com",
"ns-cloud-b2.googledomains.com",
"ns-cloud-b3.googledomains.com",
"ns-cloud-b4.googledomains.com"
]
} |
spam domain
Malicious · engine verdict · score 52
Open reportObserved: · Retrieved:
| Uuid | 019c7d8e-f22e-77e8-9a9f-292957ac43b1 |
|---|---|
| Final url | https://colinsapii.digital/user/login |
| Status | 403 |
| Ip | 178.16.52.147 |
| Contacted IP addresses | [
"178.16.52.147"
] |
| Asns | [
"202412"
] |
| Countries | [
"DE"
] |
| Document hash | 9c8c654fe26ffff624d54b10e91c30938ac4019fe8c64eb6d739783b9b5f10d0 |
| Globals | [
"crashReport"
] |
| Tls | {
"san": [
"colinsapii.digital",
"www.colinsapii.digital"
],
"cipher": "AES_128_GCM",
"issuer": "R13",
"subject": "colinsapii.digital",
"protocol": "TLS 1.3",
"valid_to": "2026-05-06T09:58:58Z",
"valid_from": "2026-02-05T09:58:59Z"
} |
| Domain age days | 15 |
| Apex age days | 15 |
| Tls age days | 15 |
| Tls valid days | 89 |
| Requests | 2 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 52,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"server": "nginx/1.18.0 (Ubuntu)",
"content-type": "text/html"
} |
Separate stored monitor snapshot; does not replace the primary report record or establish current availability.
checked — no detections recorded
Open report23 community references
Open reportNo threat flag
Open reportNo report found
Open reportA missing report is not a trust verdict. Legacy zeroes remain in the stored record; the measured trust score is unavailable.
98 / 100 · heuristic score · 0 brand references · 1 classification
Open reportThis dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.
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.
Checked, no match
Last checked
9f77d5d2a92dac67360fe77fe293eb13844a69cfdb53fcbff286891c5f669be1 · 18397 bytes 80ea3e8aa7881d69277a1fb5d55f6eff040a57bce39f8b1a34f0f9d61253e0bc · 5862 bytes 3b8b251f099f1ad6292239b6e9020d0c8b05f64b9a3899e093d6e27682a30f62 · 15460 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.
ns-cloud-b4.googledomains.comLocation describes the IP network.
944052e89bc60e12c66a63b6d555e680be547088ca33c8d9f7abaf0a7fa375a9www.colinsapii.digitalSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.colinsapii.digitalDomain recordNginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Network requests: 2 SHA-256 hashes: 2 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 06:10 UTC.
Open this scan on URLScan 019c7d8e-f22e-77e8-9a9f-292957ac43b1 ↗
| # | 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.
colinsapii.digital Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
redirected
http_redirect
redirected
http_redirect
redirected
http_redirect
redirected
http_redirect
redirected
http_redirect
redirected
http_redirect
redirected
http_redirect
redirected
http_redirect
redirected
http_redirect
redirected
http_redirect
redirected
http_redirect
redirected
http_redirect
redirected
http_redirect
redirected
http_redirect
Unavailable→Reachable
Unavailable→Reachable
https://radar.cloudflare.com/scan/0f4735d8-cc16-41a8-a4c9-0fd219a453e2
https://radar.cloudflare.com/scan/4d599db7-39e7-4f23-9473-15e90e6c291e
Reachable→Unavailable
Reachable→Unavailable
Source: domain_monitor. This stored snapshot does not establish current availability.
Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.
Recorded events: 17. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
23 community references
View sourcePage captured
View sourcecolinsapii.digital
View sourcePD-20260221-B3DD3B · Receipt 16167
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.
Reported by 1 community member, first seen Feb 21, 2026
PD-20260221-B3DD3B Recipient: abuse@omegatech.sc Policy Violations: Acceptable Use Policy (AUP): The domain colinsapii.digital is engaged in phishing activities, which directly contravenes the AUP prohibiting illegal activities, fraud, and deception. Terms of Service (TOS): The registrar reserves the right to suspend or terminate services for violations. The ongoing phishing activities constitute a clear violation of these terms, warranting immediate action. Applicable Laws (Unknown): Computer Fraud and Abuse Act (CFAA): This U.S. federal law prohibits unauthorized access to computers and networks, including phishing schemes that deceive users into providing sensitive information. Wire Fraud Statute (18 U.S.C. § 1343): This law criminalizes schemes to defraud individuals through electronic communications, which is applicable to the phishing activities associated with this domain. Anti-Phishing Act (15 U.S.C. § 7704): This statute specifically targets deceptive practices intended to solicit sensitive personal information, which is the primary function of the domain in question. Regulatory Note: Failure to take appropriate action against colinsapii.digital may expose your organization to legal liabilities and regulatory scrutiny. Immediate suspension of this domain is advised to mitigate potential risks.
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.
IC3 does not accept attachments. Keep original evidence for investigators. IC3 guidance
Federal tips line1-800-CALL-FBICurrent service: Report Fraud. England, Wales and Northern Ireland. Scotland: 101.
Contact centre0300 123 2040Report 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.
Helpline1930Select your country to get official cybercrime contacts, or create a complaint draft →.
If you made a payment, contact your bank or payment service through its official contacts as soon as possible. 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.
Scammers are criminals. Filing a report creates a legal record and helps protect others.
Template-based draft • optional AI wording assistance requires separate consent
Choose 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 ↗
colinsapii.digital)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.
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.