VirusTotal
15 / 91 engine detections
Open report“От 100 000 рублей в месяц - стабильный доход от ГазИнвест для граждан РФ. Регистрация открыта с 1 а…”
15 / 91 engine detections
Open report1 threat-system alert
Open reportDBL_SPAM
no community references
Open reportprovider verdict: clean
Open report80/100
Open reportNo threat flag
Open reportNo malicious flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | brightgo.digital |
malicious | Sinkholed |
PhishDestroy threat report
Analysis as of July 20, 2026 indicates that the domain brightgo.digital, registered through Dynadot Inc on December 28, 2025, is currently active and tied to a generic phishing threat. The domain uses Cloudflare DNS, with authoritative name servers abby.ns.cloudflare.com and anuj.ns.cloudflare.com, and resolves to the single IPv4 address 196.251.107.124. The IP address appears on at least one public security blocklist, and the domain is explicitly listed by PhishDestroy, confirming that multiple threat‑intelligence sources have classified it as malicious. VirusTotal records show that the domain has been scanned by 95 antivirus and URL‑reputation vendors, with no detections reported at the time of the scan; however, the absence of detections does not constitute assurance of safety and may reflect evasion or limited coverage. No additional evidence such as SSL certificate details, HTTP response codes, page titles, or content signatures is presently available, leaving the exact phishing payload and targeted brand undefined. Defenders should treat brightgo.digital as a high‑confidence malicious indicator. Recommended actions include adding the domain and its resolving IP to network‑level blocklists, configuring web‑proxy and DNS filtering solutions to deny traffic, monitoring outbound connections for attempts to reach 196.251.107.124, and correlating any internal logs that reference the domain with existing phishing incident response playbooks. Continuous re‑evaluation is advised as further intelligence, such as content analysis or additional vendor detections, becomes available.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 019f7f9f-2261-776a-9a3f-ea04f67fc5a2 |
|---|---|
| Final url | https://brightgo.digital/ |
| Status | 200 |
| Ip | 196.251.107.124 |
| Contacted IP addresses | [
"196.251.107.124"
] |
| Asns | [
"214351"
] |
| Countries | [
"DE"
] |
| Document hash | e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 |
| Cookies | [
"_subid",
"ea0ac"
] |
| Tls | {
"san": [
"brightgo.digital"
],
"cipher": "AES_256_GCM",
"issuer": "YE2",
"subject": "brightgo.digital",
"protocol": "TLS 1.2",
"valid_to": "2026-08-27T04:10:39Z",
"valid_from": "2026-05-29T04:10:40Z"
} |
| Domain age days | 203 |
| Apex age days | 203 |
| Tls age days | 52 |
| Tls valid days | 89 |
| Requests | 2 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 87,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"server": "nginx",
"content-type": "text/html; charset=UTF-8"
} |
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.
abby.ns.cloudflare.comanuj.ns.cloudflare.comLocation describes the IP network.
2d20815899ca9c0140d52563bdde53aab0dec85657ebc803a1dd62493dcfff25brightgo.digitalSaved 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.
brightgo.digital
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
Reachable→Unavailable
15/91 engine detections
View sourcePD-20260720-FC834D
No threat flag
View sourcebrightgo.digital
View sourcePage captured
View sourcePD-20260720-FC834D Recipient: abuse@dynadot.com Registrar: Dynadot LLC / Dynadot Inc (United States) Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
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
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 ↗
brightgo.digital)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
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
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
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.