The domain fidprimerlty.live was observed with a Google Safe Browsing classification for social engineering as of 2026-10-13. A PageSpeed performance score of 32 was also recorded for the domain on that date, reflecting technical measurements from that source.
Recorded Evidence
MetaMask and SEAL external blocklists each listed fidprimerlty.live as of 2026-10-13. Google Safe Browsing flagged the domain for social engineering on 2026-10-13. VirusTotal recorded 0 detections out of 92 scanners when it checked the domain on 2026-10-10. PhishDestroy internally listed the domain as of 2026-10-13. The domain was registered with DYNADOT LLC on 2026-10-09.
Interpretation
PhishDestroy contains an internal listing for fidprimerlty.live, documenting its inclusion in their records. VirusTotal’s scan-based measurement records the domain’s status across a wide range of scanners, providing a snapshot of detection intelligence. The combination of blocklist entries and scan-based assessments offers multiple points of comparison for future reviews.
Recommended Actions
For fidprimerlty.live, preserve the MetaMask and SEAL blocklist entries as reference records. Retain Google Safe Browsing and VirusTotal scan results for ongoing comparison with future measurements. Keep the PhishDestroy internal listing to support historical context in subsequent assessments.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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 fidprimerlty.live· checked Oct 13, 2026
32
Poor
Performance
FCP
5.89s
First Contentful Paint
LCP
8.56s
Largest Contentful Paint
CLS
0.317
Cumulative Layout Shift
TBT
494ms
Total Blocking Time
SI
5.89s
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.
Status Check2026-10-12 23:43:56 UTC
Telemetry event observed.
Threat First Observed2026-10-12 23:43:07 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 198.251.89.144.
위협 대응 Pipeline
발견
Analysis
Monitoring
7 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.
도메인은 계속 연결 가능하거나 액세스가 제한되어 있습니다. 향후 점검을 통해 이 관찰 내용이 업데이트될 수 있습니다.
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.
(US)
