PhishDestroy identifies cryptofather.company as an active cryptocurrency phishing domain posing as a legitimate crypto platform. The threat type has been classified as generic phishing with the domain currently marked as active and under investigation.
This domain was flagged by 1 of 95 VirusTotal vendors, registered through HOSTINGER operations, UAB, and resolves to IP address 88.223.85.35 using a Let's Encrypt SSL certificate. The domain was created on February 03, 2026, making it a very recent registration with minimal historical trust or reputation metrics available at this time.
The current status of cryptofather.company remains active with no known blocklist entries or vendor detections at the time of this assessment. Users should immediately avoid interacting with this domain, especially any requests for cryptocurrency deposits, account credentials, or personal financial information. If exposure has occurred, users are advised to revoke any shared credentials, monitor financial accounts, and report the incident to relevant authorities. Domain owners and security teams should consider immediate network-level blocking of IP 88.223.85.35 and domain cryptofather.company to prevent further compromise.
RegistrationCreated Apr 5, 2026 (189d)—Expires Feb 3, 2027
Time to First Unavailability13h
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 DetectedApr 5, 2026
DOM Analysisanalyzed Jul 29, 2026score 56/100
Submitted URLhttp://cryptofather.company/
Case ID
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.
Accountability draft
Nothing is sent automatically.
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
88.223.85.35
Network ASN
AS47583
Organization
UAB INIT
Observed location
Boston, US
Nameservers 2
ns1.dns-parking.com
ns2.dns-parking.com
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt
Valid until
2026-07-03 00:00:00
Hostname coverage
Hostname coverage not recorded
Validity
Stored certificate expired
Collection time
2026-04-21 23:00:07 UTC
Collection source
PhishDestroy collector
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-11 01:08:18 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-04-21 22:27:10 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-04-21 22:27:10 UTC → 2026-09-30 16:14:55 UTC · 3,881.80hmidpoint estimate ≈ 2026-07-11 19:21:02 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.
Google PageSpeed Insights — mobile performance audit of cryptofather.company· checked Apr 5, 2026
62
Needs Work
Performance
FCP
4.09s
First Contentful Paint
LCP
8.14s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
65ms
Total Blocking Time
SI
6.19s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Threat Response Pipeline
Discovery
Analysis
Notifications
Monitoring
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
cryptofather.company 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.
Apr 6, 2026
Time to First Unavailability
13 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.
6 evidence signal groups linked1 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 · cryptofather.company
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.
Report 
