VirusTotal
3 / 89
ReportInterpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
“로그인으로 돌아가기”
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.
3 / 89
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
4 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
A 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.
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.
gdeaiodine.vip returned HTTP status 502 in an HTTP check recorded on 2026-10-01, a dated response that describes only that request. The same domain was first observed on 2026-09-02, according to the recorded first-observation date.
The HTTP check on 2026-10-01 recorded status 502 for gdeaiodine.vip. VirusTotal, checked on 2026-09-13, reported 3 detections across 89 scanners. OTX, checked on 2026-09-13, listed 4 pulses. The domain was first observed on 2026-09-02, and the registrar is Dynadot Inc. The IP address 154.91.66.194 is associated with Singapore and the organization Tcloudnet, Inc. The publisher-owned PhishDestroy catalogue includes an internal listing for this domain, and the blocklist check date is 2026-10-01.
The named source records give a reader several dated reference points: an HTTP response, a VirusTotal detection ratio, an OTX pulse count, and a first-observation date. These records come from different checks on different dates, so they should be compared as separate observations rather than merged into one conclusion. The chronology from first observation to the later checks is useful for ordering events, but it does not by itself establish a trend or a change in the domain.
For gdeaiodine.vip, preserve the HTTP check record, the VirusTotal record, and the OTX record as separate source documents. Compare the HTTP status record against the VirusTotal and OTX records in separate sentences when reviewing the domain. Also retain the PhishDestroy internal listing and the first-observation record for future reference. Re-check the domain's HTTP response and the named sources to see whether later records differ from the ones described here.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='gdeaiodine.vip', port=80): Max retries exceeded with url: / (Caused by NewConnectionError(
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.
a3.share-dns.comLocation describes the IP network.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
10 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.
1 community report
CategoryPHISHING
The PhishFort Detection System has flagged this as a domain threat, classified as null. Threat detected at 2026-09-02T10:19:21.123Z.
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