On 2026-10-01, a recorded HTTP request to ajbells.netlify.app returned status 404. The same domain was first observed on 2026-08-09, according to the available records.
Recorded Evidence
The HTTP check on 2026-10-01 recorded status 404 for ajbells.netlify.app. The domain was first observed on 2026-08-09. VirusTotal recorded 13 detections across 89 scanners on 2026-09-13. The publisher-owned PhishDestroy catalogue listed the domain, and the blocklist check occurred on 2026-10-01. The resolved IP address was 63.176.8.218, associated with AWS EC2 (eu-central-1) in DE.
Interpretation
The HTTP 404 record describes only the response observed on that date, not all content that may exist on the domain. The VirusTotal detection count and scanner total describe one dated scan result, and the PhishDestroy listing is a separate publisher-owned record. The first-observed date and the HTTP check date are different, so the records do not establish a continuous state or a trend.
Recommended Actions
Preserve the ajbells.netlify.app HTTP 404 record and the VirusTotal scan result as separate source records for comparison. Compare the PhishDestroy listing against the HTTP response record without treating either as a complete picture. Review the ajbells.netlify.app domain against these dated records when assessing its status.
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.
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Waiting
Domain details
Domain
IP ContextNetlify shared edgeorigin IP hiddenEdge-IP reputation is not attributed to this domain.
Platform providerNetlify(US)
HTTP Status404 Not Found
Time to First Unavailability34 days
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 DetectedAug 9, 2026
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
63.176.8.218
Network ASN
AS16509
Organization
AWS EC2 (eu-central-1)
Observed location
Frankfurt, DE
Server header
Netlify
Edge-IP reputation is not attributed to this domain.
Primary outcomeInactivereason: Http No Content70% confidence
Attributionsource: Current Http Probe
Evidence layersAvailability: Root path has no contentContent: Absent At RootDNS: StaleRegistration: Unknown
Latest HTTP observationInactiveHttp No Content70%2026-10-11 01:14:29 UTC
RDAP registrationUnknown
Observed timelinecurrent episode first observed: 2026-10-01 01:39:08 UTCfirst terminal observation: 2026-10-01 01:39:08 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 · 2 identified
N
Netlify
PaaSCDN
Netlify providers hosting and server-less backend services for web applications and static websites.
Last analyzed First positive detection Previous stored snapshot: 13 detections
alphaMountain.ai
BitDefender
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
LevelBlue
Lionic
Sophos
VIPRE
Webroot
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.
Domain Status Transition2026-09-12 19:56:29 UTC
Domain state transitioned from alive to dead.
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.
Threat Ingested
ajbells.netlify.app detected and queued for full analysis
Aug 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.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Sep 12, 2026
Time to First Unavailability
819 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.
1 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 · ajbells.netlify.app
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)
