Stored registration data identifies Trustname / Fewmoretaps OÜ (IANA 4318) as the registrar. PhishDestroy maintains a separate registrar investigation; that material is contextual and is not an independent detection for this domain.
natapex.com was observed returning an HTTP 301 status code on 2026-10-07, indicating a recorded response from the domain at that time. The domain was also listed in the publisher's internal PhishDestroy catalogue, providing another source of information for review.
Recorded Evidence
VirusTotal recorded 2 detections out of 92 scanners for natapex.com on 2026-10-07. OTX referenced the domain in 3 pulses as of 2026-10-07. The domain was registered with Fewmoretaps OU d/b/a Trustname.com on 2026-09-21, and its SSL certificate was issued by Let's Encrypt / YE1, scanned on 2026-10-07.
Interpretation
The available records from VirusTotal, OTX, and the internal PhishDestroy catalogue offer a multi-source perspective on natapex.com. The HTTP response and detection data provide technical benchmarks, while registration and certificate details supply administrative context. Each dated observation can be used to compare domain status across different platforms.
Recommended Actions
For natapex.com, retain the HTTP response and VirusTotal detection records for ongoing monitoring. Compare OTX pulse mentions and PhishDestroy catalogue listings with future observations to identify any changes. Preserve registration and SSL certificate information for administrative review and historical reference.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo 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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-07 01:00:24 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-07 01:00:24 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.
Last analyzed First positive detection Previous stored snapshot: 2 detections
CRDF
Forcepoint ThreatSeeker
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.
VirusTotal Detections Update2026-10-07 02:56:09 UTC
VirusTotal scanner detections updated from 1 to 2. Added scanner alerts: CRDF.
Threat First Observed2026-10-07 00:29:21 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 104.21.42.192.
Threat Response Pipeline
Discovery
Analysis
Monitoring
9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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 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+
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.
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 · natapex.com
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.
Content matches4
Same favicon hash or the same page title as this host.
(BY)
PhishDestroy Investigation
