gov-dfkg.one was observed with a Google Safe Browsing threat record dated 2026-10-12, documenting social engineering as an identified risk. The domain also achieved a perfect performance score in a PageSpeed check.
Recorded Evidence
VirusTotal recorded 13 detections out of 92 scanners for gov-dfkg.one on 2026-10-09. Google Safe Browsing flagged the domain for social engineering threats on 2026-10-12. OTX documented three pulses referencing gov-dfkg.one as of 2026-10-12. The domain was listed in the PhishDestroy internal catalogue and registered with Dynadot Inc on 2026-04-27.
Interpretation
PhishDestroy contains an internal listing for gov-dfkg.one, which records its presence in a publisher-managed catalogue. VirusTotal provides a measurement of detections from multiple scanners, offering insight into external scanning results. The evidence spans several sources and dates, allowing for comparison of threat intelligence and performance metrics over time.
Recommended Actions
Preserve the VirusTotal, Google Safe Browsing, and OTX records for gov-dfkg.one to support ongoing reviews and comparisons. Reference the PhishDestroy internal listing and PageSpeed performance score when evaluating future observations.
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.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-13 10:00:51 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 10:00:51 UTC
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.
技术 · 2 identified
Cloudflare
CDN
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Google PageSpeed Insights — mobile performance audit of gov-dfkg.one· checked Oct 12, 2026
100
Good
Performance
FCP
0.76s
First Contentful Paint
LCP
0.76s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.76s
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 11:33:41 UTC
Telemetry event observed.
Threat First Observed2026-10-12 11:33:00 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 172.67.183.61.
威胁响应 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)
