VirusTotal
6 / 89
ReportInterpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
“Abstract Engineering”
Assessment based on the stored source evidence below. Review 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.
6 / 89
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
2 external matches
DetailsA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
no community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
provider verdict: clean
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
stored report
View stored capture ↗ ReportA preserved page image documents what the collector received; a capture is not a safety verdict.
Analysis completed
ReportThis is the recorded automated analysis. Completion alone is not a safety verdict.
80/100
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Checked; no threat flag recorded
ReportA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Stored narrative · generated . Provider checks below retain their own observation dates.
On 2026-10-01, cache.dev.titan.abstract.engineering returned HTTP status 302, a recorded redirect response at that check. The same date shows two external blocklist entries, MetaMask and SEAL, alongside a Phishdestroy internal listing.
VirusTotal recorded 6 detections across 89 scanners on 2026-09-14. The SSL certificate, issued by Google Trust Services / WE1, was scanned on 2026-08-31. Phishdestroy's internal listing was recorded on 2026-08-31, and PageSpeed gave a performance score of 56 on 2026-08-31. The first observation of the domain was logged on 2026-08-31, while the HTTP check occurred on 2026-10-01.
The MetaMask and SEAL blocklist entries share the 2026-10-01 date with the HTTP check, so those records describe the same review window. VirusTotal's 2026-09-14 scan and the 2026-08-31 SSL, PageSpeed, and first-observation records predate that window, so their dates should be compared separately rather than treated as one snapshot.
Retain the dated records for cache.dev.titan.abstract.engineering from MetaMask, SEAL, VirusTotal, Phishdestroy, and PageSpeed so later checks can be compared against them. When reviewing the full domain again, note each source's own date and value rather than merging them into one conclusion. Avoid submitting sensitive information to the domain during any review, since the recorded status reflects only the listed check dates.
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.
These checks have no retained result. This does not mean they passed or that a scan is running.
For the registrable domain abstract.engineering behind this subdomain, 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.
Edge-IP reputation is not attributed to this domain.
betty.ns.cloudflare.comLocation describes the IP network.
98769dda155336b00aaaa7f2514e00a2827edd1af3d64a11168fac04d9a1e24aSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of cache.dev.titan.abstract.engineering · checked Aug 31, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareScanner note: redirect: raw=redirect_302; http=302; via=https_proxy; location=https://cache.dev.titan.abstract.engineering/outpost.goauthentik.io/start?rd=https%3A%2F%2Fcache.dev.titan.abstract.engi; server=cloudflare
172.67.134.145.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
Unknown
probe_inconclusive
0→6
6→Observation retained
5→6
2→5
Reachable
13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
79 stored lookalike domains
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
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