VirusTotal
14 / 91 engine detections
보고서 열기“Outlook”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@godaddy.com.
The latest stored availability evidence still shows the domain reachable; 3 months has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
Security analysis of srva.closer.website covers observed phishing indicators, infrastructure evidence, current status, and defensive guidance.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
14 / 91 engine detections
보고서 열기4 threat-system alerts
보고서 열기악성
보고서 열기악성
보고서 열기no community references
보고서 열기No threat flag
보고서 열기Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| Cloudflare DNS | srva.closer.website |
malicious | Sinkholed |
| OpenDNS | srva.closer.website |
phishing | Phishing Block |
| Hagezi Threat Feed | srva.closer.website |
malicious | Sinkholed |
| DNS4EU | srva.closer.website |
malicious | Sinkholed |
AI-assisted evidence review
The domain srva.closer.website was registered through GoDaddy.com, LLC on August 05, 2022 and currently uses the authoritative name servers ns1.closer.ws and ns2.closer.ws. DNS resolution points to the IPv4 address 94.130.129.186, which remains active as of the report date, July 15, 2026. The domain is classified as a generic_phishing threat and is listed as high‑risk. VirusTotal analysis shows that 18 of 91 security vendors have flagged the domain, indicating a notable detection rate across multiple scanning engines. No additional intelligence regarding the page content, targeted brand, or phishing kit has been disclosed, so the exact nature of the credential‑harvesting payload remains unknown. Infrastructure analysis suggests a modest operational footprint, relying on a single IP address and standard GoDaddy registration, which is a pattern observed in a number of low‑cost phishing campaigns. Defenders should treat the domain as malicious, incorporate the host and IP into blocklists, and monitor for any related activity such as DNS queries or outbound connections to the same address. Network sensors and email gateways ought to be configured to drop traffic to srva.closer.website, and any observed attempts to interact with the site should be logged for further investigation. Continuous re‑evaluation is advised in case additional indicators emerge.
For the registrable domain closer.website 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.
ns1.closer.wsns2.closer.wsLocation describes the IP network.
c2604b89b3a832277fadfd42958068ad98f03a7484a4a08807ecc03016d05b64closer.websiteSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
srva.closer.website
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
14/91 engine detections
View sourcePD-20260717-C75063
No threat flag
View sourcesrva.closer.website
View sourcePage captured
View sourcePD-20260717-C75063 Recipient: abuse@godaddy.com 계정 자격 증명, 개인 정보 또는 결제 정보를 입력했거나 이 도메인에서 파일을 다운로드한 경우 즉시 조치를 취하세요. 다음은 사건을 신고하고 자신을 보호하는 데 도움이 되는 리소스입니다.
공식 사이버 범죄 연락처 또는 불만사항 초안 작성 →를 받으려면 국가를 선택하세요.
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 ↗
srva.closer.website)비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
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.