VirusTotal
7 / 91 engine detections
보고서 열기“ФинЩит”
fin-shield.solutions — 콘텐츠를 사용할 수 없음. 증거 요약: VirusTotal 7/91 (ChainPatrol); URLQuery 2 det.; Spamhaus DBL_PHISH; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 100/100. 등록기관: PDR.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
7 / 91 engine detections
보고서 열기2 det.
보고서 열기DBL_PHISH
no community references
보고서 열기provider verdict: clean
보고서 열기No threat flag
보고서 열기No malicious flag
보고서 열기Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
The domain fin-shield.solutions is currently under investigation for being involved in a generic_phishing campaign. The risk level associated with this domain is under investigation, indicating that while there is no definitive high-risk classification, further analysis is warranted to understand the potential threat vector and impact.
Analysis indicates that the domain was registered through PDR Ltd. d/b/a PublicDomainRegistry.com on February 11, 2026. The SSL certificate is issued by Let's Encrypt, which is a common practice for legitimate and malicious sites alike. The domain resolves to the IP address 93.95.231.181. As of the latest scan, VirusTotal reports 0/95 detections, suggesting that the domain has not been flagged by major security vendors yet. However, the lack of detections does not necessarily imply safety, as the domain could be a recent addition to a phishing campaign. Infrastructure analysis reveals that the domain is still active and accessible, which may indicate ongoing malicious activity.
To mitigate the risks associated with generic_phishing, it is recommended that users exercise caution when interacting with this domain. Avoid clicking on any links or providing sensitive information. Administrators should consider adding the domain to their network's blocklist and monitoring traffic to this IP address for any suspicious activity. Additionally, implementing multi-factor authentication and regularly updating security protocols can help protect against potential phishing attempts. Organizations should also educate their employees on recognizing and reporting phishing activities to enhance overall security posture.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/FinShchitStored page referenceIoC extraction recorded 2026-07-29 02:49:55 UTC
Last checked
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.
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.
ns0.1984.isns1.1984.isns1.1984hosting.comns2.1984.isns2.1984hosting.comLocation describes the IP network.
c66f4fab8cc9490bf66a4d7c2df1795e6b2d93959ff72be3e28bad197192f315www.fin-shield.solutionsSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.fin-shield.solutionsDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of fin-shield.solutions · checked Jun 30, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='fin-shield.solutions', port=80): Max retries exceeded with url: / (Caused by NewConnection
fin-shield.solutions
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
7/91 engine detections
View sourcePage captured
View sourcePD-20260630-E06576
No threat flag
View sourcefin-shield.solutions
View sourcePD-20260630-E06576 Recipient: abuse@publicdomainregistry.com Registrar: PublicDomainRegistry (PDR Ltd.) (India) Policy Violations: Explicit policy to immediately suspend domains used for phishing, 419 scams, identity fraud, malware distribution without prior notice Applicable Laws: IT Act 2000 §§66C–66D (identity theft, cheating by personation), Indian Penal Code §420 / Bharatiya Nyaya Sanhita §318 (fraud)
계정 자격 증명, 개인 정보 또는 결제 정보를 입력했거나 이 도메인에서 파일을 다운로드한 경우 즉시 조치를 취하세요. 다음은 사건을 신고하고 자신을 보호하는 데 도움이 되는 리소스입니다.
공식 사이버 범죄 연락처 또는 불만사항 초안 작성 →를 받으려면 국가를 선택하세요.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
fin-shield.solutions)비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.