invcard.pages.dev returned HTTP status 403 on 2026-10-01, according to the recorded HTTP check. The same domain was first observed on 2026-09-04, and a PhishDestroy internal listing is recorded for it.
Recorded Evidence
The PhishDestroy internal listing marks invcard.pages.dev in the publisher-owned catalogue. VirusTotal recorded 10 detections out of 89 scanners on 2026-09-17. The SSL certificate scanned on 2026-09-15 was issued by Google Trust Services / WE1, and the PageSpeed check on 2026-09-15 returned a performance score of 100. The IP address 172.66.47.109 is associated with Cloudflare, Inc. in CA, per the recorded IP data.
Interpretation
The PhishDestroy listing and the VirusTotal scan were recorded on different dates, so their observations describe separate points in time rather than one combined state. The HTTP check on 2026-10-01 and the SSL scan on 2026-09-15 also come from different dates, which limits direct comparison across those records. Because the observation dates differ, the named sources should be read as dated snapshots, not as a single synchronized assessment.
Recommended Actions
Retain the recorded observations for invcard.pages.dev, including the PhishDestroy listing and the VirusTotal result, with their exact dates. Compare any later HTTP or SSL observations against the 2026-10-01 and 2026-09-15 records to see whether the recorded values change. Avoid submitting sensitive information while reviewing invcard.pages.dev, since the recorded HTTP status and listing do not establish what the domain currently serves.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Observed timelinelast reachable: 2026-09-15 22:06:49 UTCcurrent episode first observed: 2026-10-01 01:39:30 UTCobserved RIP window: 2026-09-15 22:06:49 UTC → 2026-10-01 01:39:30 UTC · 363.54hmidpoint estimate ≈ 2026-09-23 11:53:09 UTC · precision 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.
技术 · 3 identified
H
HSTS
安全
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Last analyzed First positive detection Previous stored snapshot: 10 detections
alphaMountain.ai
BitDefender
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Lionic
Sophos
URLQuery
VIPRE
网站性能分析
Google PageSpeed Insights — mobile performance audit of invcard.pages.dev· checked Sep 15, 2026
100
Good
Performance
FCP
0.78s
First Contentful Paint
LCP
0.78s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.9s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
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-09-16 17:31:51 UTC
VirusTotal scanner detections updated from 6 to 10. Added scanner alerts: Forcepoint ThreatSeeker, Lionic, Sophos, VIPRE, alphaMountain.ai. Resolved alerts: LevelBlue.
Domain Status Transition2026-09-16 10:00:37 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-14 22:23:13 UTC
Domain ingestion complete. Initial state is marked as alive.
威胁响应 Pipeline
发现
Analysis
Monitoring
11 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.
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.
(US)
