Skip to security report
Analytics Dashboard
Domain security and threat intelligence
jdbdkdbsosu.blogspot.com favicon

jdbdkdbsosu.blogspot.com

In short

jdbdkdbsosu.blogspot.com is a Google impersonation page detected by PhishDestroy on 2026-09-16. Risk: critical (83/100). Registrar: MarkMonitor. Status: Content unavailable. Hosting: Google LLC. VirusTotal: 6/89 engines flag it. Do not enter credentials or connect a wallet.

“GET FREE ROBUX”

Registrar
MarkMonitor
Resolved IP
142.251.127.132
PhishDestroy assessment Critical
Availability Content unavailable Content was unavailable in the latest observation Observed · HTTP probe
Risk signals
VirusTotal detections: 6/89 Automated brand label: Google
Sep 16, 2026
API
This domain has been flagged as malicious
Security engines reporting a detection: 6. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
6 / 89
engine detections
Google Safe Browsing
No threat flag
Page captures
7
open gallery
Source evidenceVirusTotal 6 / 89 5 sources

VirusTotal

6 / 89 engine detections

Open report

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Phishing Security threats Phishing
View full Cloudflare Radar report

Analysis

Critical
VirusTotal
6 / 89
Page captures
7
Page captures Source results Registration record

PhishDestroy threat report

Overview

jdbdkdbsosu.blogspot.com is a Blogspot page titled "GET FREE ROBUX" that PhishDestroy classifies as a gaming scam. It baits Roblox players, a largely young audience, with the promise of free in-game currency. PhishDestroy first flagged it on 2026-09-16. As of 2026-10-19 the site still responds, but its main page currently shows no content.

How the scam works

Free Robux pages follow a familiar script. Only Roblox itself issues Robux, so any page offering them for free is lying. The visitor is asked for a Roblox username, sometimes a password, and is then sent through a "human verification" step of surveys, app installs or offer sign-ups that never ends in a reward. The real payout goes to the operator: hijacked game accounts and their inventories, harvested personal details, affiliate commissions from the offers, and sometimes unwanted software on the victim's device.

Evidence

Six of 89 engines on VirusTotal flagged the page when it was checked on 2026-09-23: alphaMountain.ai, BitDefender, ESET, G-Data, Gridinsoft and Sophos. That count is modest, but it comes from several unrelated security vendors and matches PhishDestroy's own listing. PhishDestroy is currently the only blocklist that includes the domain.

Infrastructure

The page runs on a throwaway Blogspot subdomain with a random-looking keyboard-mash name. That setup costs nothing to create and is easy to abandon. It is served from Google LLC infrastructure in the US with a Google Trust Services certificate, which Blogspot issues automatically to every blog, so the padlock says nothing about whether the page is trustworthy.

What to do

If you typed your Roblox password on this page, change it at once and turn on 2-Step Verification. Then check your account for unfamiliar logins, trades or spending, and reset the password anywhere else you reuse it. If you installed an app or extension as part of a "verification" step, uninstall it and run a malware scan. Parents should explain that no site can give out free Robux. Defenders can block the hostname and report the blog to Google through Blogger's abuse channel.

Useful links

VirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Cloudflare Radar · 2026-09-23T03:39:07Z

Observed: · Retrieved:

Uuid
b1fe6027-1f38-433d-88ea-a7553027d349
Final url
https://jdbdkdbsosu.blogspot.com/
Status
200
History
[
    {
        "url": "https://jdbdkdbsosu.blogspot.com/",
        "status": 200
    }
]
DOM structure hash
4a758d1fdd551f05cbeed76f9f1383356fb8aee266c658de865c1ba4f0f3b919
Document hash
0ae1735326fef4389efbb701462e52a935804f5270613798e6c6f696fc670c93
Domain risks
[
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "jdbdkdbsosu.blogspot.com",
        "type": "CNAME",
        "value": "blogspot.l.googleusercontent.com"
    },
    {
        "name": "jdbdkdbsosu.blogspot.com",
        "type": "CNAME",
        "value": "blogspot.l.googleusercontent.com"
    }
]
Dnssec valid
false
Ip
142.251.33.193
Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
Registration record
{
    "registrar": "MarkMonitor Inc.",
    "created": "2000-07-31T21:38:58Z",
    "updated": "2026-06-29T10:34:06Z",
    "expires": "2027-07-31T21:38:58Z",
    "nameservers": [
        "ns1.google.com",
        "ns2.google.com",
        "ns3.google.com",
        "ns4.google.com"
    ]
}
VirusTotal · 2026-10-17T03:38:47Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 46,
    "malicious": 16,
    "suspicious": 0,
    "undetected": 30
}
Vendor labels
{
    "ESET": "phishing",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "URLQuery": "malicious",
    "Kaspersky": "phishing",
    "Gridinsoft": "phishing",
    "MalwareURL": "phishing",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
Registrar
MarkMonitor Inc.
Created
2000-07-31T21:38:58Z
Expires
2027-07-31T21:38:58Z
Updated
2026-06-29T10:34:06Z
First seen
2026-09-16T11:31:04Z
DNS records
[
    {
        "ttl": 300,
        "type": "CNAME",
        "value": "blogspot.l.googleusercontent.com"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2607:f8b0:4001:c56::84"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "142.250.152.132"
    }
]
Dns at
2026-10-17T03:55:04Z
Jarm
27d40d40d29d40d1dc42d43d00041ded961c16c68658e95145597cf992c36c
Certificate
{
    "san": [
        "misc-sni.blogspot.com",
        "blogspot.ae",
        "*.blogspot.ae",
        "blogspot.al",
        "*.blogspot.al",
        "blogspot.am",
        "*.blogspot.am",
        "blogspot.ba",
        "*.blogspot.ba",
        "blogspot.be"
    ],
    "issuer": "Google Trust Services / WE2",
    "serial": "9d5a60aa1a77b2e30ad083111463b97f",
    "sha256": "96af029a35a29461434960b48ba2154af0c39c2d7eb0c4b553a22552f01a76ff",
    "subject": "misc-sni.blogspot.com",
    "valid_to": "2026-12-11T20:01:30Z",
    "valid_from": "2026-09-18T20:01:31Z"
}
Registration record
{
    "registrar": "MarkMonitor Inc.",
    "registrar_iana_id": "292",
    "registrar_url": "http://www.markmonitor.com",
    "created": "2000-07-31T07:00:00Z",
    "updated": "2026-06-29T10:34:06Z",
    "expires": "2027-07-31T00:00:00Z",
    "status": [
        "clientDeleteProhibited",
        "clientTransferProhibited",
        "clientUpdateProhibited",
        "serverDeleteProhibited",
        "serverTransferProhibited",
        "serverUpdateProhibited"
    ],
    "nameservers": [
        "ns1.google.com",
        "ns2.google.com",
        "ns3.google.com",
        "ns4.google.com"
    ],
    "dnssec": "unsigned"
}

Questions about jdbdkdbsosu.blogspot.com

Is jdbdkdbsosu.blogspot.com legit?

No. PhishDestroy classifies jdbdkdbsosu.blogspot.com as a Google impersonation page (risk: critical, 83/100); it was first detected on 2026-09-16. VirusTotal: 6/89 engines flag it. Treat the site as unsafe.

Is jdbdkdbsosu.blogspot.com safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on jdbdkdbsosu.blogspot.com. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used jdbdkdbsosu.blogspot.com?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 7 captures

Cloudflare Radar 1 / 7
SourceCloudflare Radar
Recorded2026-09-23 03:39 UTC
StateStored capture
Position1 / 7
Open capture Source Report Wayback Download

Domain details

Domain
IP Reputation abuse score 0/100 7 reports Email SpamPort ScanHackingBrute-Force checked Oct 21, 2026
Platform provider MarkMonitor
Abuse contact["abusecomplaints@markmonitor.com", "72d89d094faaef2es@"]
HTTP Status404 Not Found
Technical detailsProvenance & timestamps
First DetectedSep 16, 2026
Favicon Hash
Observed page title
GET FREE ROBUX
Automated brand references
Google
TLS Certificate
Issued by Google Trust Services / WE2 · stored validity ends in 35 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
142.251.127.132
Network ASN
AS15169
Organization
Google LLC
Observed location
Mountain View, US
Server header
GSE

Nameservers 4

  • ns1.google.com
  • ns2.google.com
  • ns3.google.com
  • ns4.google.com

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE2
Valid from
2026-09-04 08:05:57
Valid until
2026-11-27 08:05:56
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-21 10:02:08 UTC
Collection source
PhishDestroy collector
Certificate fingerprintbae5c6fbbbc165668f5bb3bd72ca83c821e993d218ebbef8483371d5863e2614
Certificate names · 70 SANs
  • blogspot.ae
  • blogspot.al
  • blogspot.am
  • blogspot.ba
  • blogspot.be
  • blogspot.bg
  • blogspot.ca
  • blogspot.ch
  • blogspot.cl
  • blogspot.co.at
  • blogspot.co.id
  • blogspot.co.il
  • blogspot.co.ke
  • blogspot.co.nz
  • blogspot.co.uk
  • blogspot.co.za
  • blogspot.com
  • blogspot.com.ar
  • blogspot.com.au
  • blogspot.com.br
  • blogspot.com.by
  • blogspot.com.co
  • blogspot.com.cy
  • blogspot.com.ee
  • blogspot.com.eg
  • blogspot.com.es
  • blogspot.com.mt
  • blogspot.com.ng
  • blogspot.com.tr
  • blogspot.com.uy
  • blogspot.cz
  • blogspot.de
  • blogspot.dk
  • blogspot.fi
  • blogspot.fr
  • blogspot.gr
  • blogspot.hk
  • blogspot.hr
  • blogspot.hu
  • blogspot.ie
  • blogspot.in
  • blogspot.is
  • blogspot.it
  • blogspot.jp
  • blogspot.kr
  • blogspot.li
  • blogspot.lt
  • blogspot.lu
  • blogspot.md
  • blogspot.mk
  • blogspot.mx
  • blogspot.my
  • blogspot.nl
  • blogspot.no
  • blogspot.pe
  • blogspot.pt
  • blogspot.qa
  • blogspot.ro
  • blogspot.rs
  • blogspot.ru
  • blogspot.se
  • blogspot.sg
  • blogspot.si
  • blogspot.sk
  • blogspot.sn
  • blogspot.tw
  • blogspot.ug
  • blogspot.vn
  • bp.blogspot.com
  • misc-sni.blogspot.com

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 142.251.127.132rapiddns.io

Latest Classified Outcome 2026-10-22 10:07:17 UTC

Primary outcome Inactive reason: Http No Content 70% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Root path has no content Content: Absent At Root DNS: Resolved Registration: Unknown
Latest HTTP observation Inactive Http No Content 70% 2026-10-22 10:07:17 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-16 10:07:59 UTC last content: 2026-10-16 10:07:59 UTC current episode first observed: 2026-10-16 22:07:33 UTC observed RIP window: 2026-10-16 10:07:59 UTC → 2026-10-16 22:07:33 UTC · 11.99h midpoint estimate ≈ 2026-10-16 16:07:46 UTC · precision medium · basis bounded
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.
Technologies · 12 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

6 / 89 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 6 detections
alphaMountain.ai
BitDefender
ESET
G-Data
Gridinsoft
Sophos
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of jdbdkdbsosu.blogspot.com · checked Sep 23, 2026

70
Needs Work
Performance
FCP
3.65s
First Contentful Paint
LCP
5.15s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
5.28s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details9

Availability observations

Last reachable observation
Last content observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
11.99
Estimate basis
Bounded by observations
Estimate precision
Medium

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

Page titles differ

http_other: raw=http_404; http=404; via=http_proxy; server=GSE

Browser
GET FREE ROBUX
Crawler
Blog niet gevonden
jdbdkdbsosu.blogspot.com
Stored observation history19

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  2. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  3. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  4. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  5. Availability monitor · Recorded state

    live_content→inactive

    http_no_content

Earlier observations 14
  1. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  6. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  7. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  8. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  9. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  10. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  11. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  12. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  13. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  14. Availability monitor · First collection record

    Reachable

Recorded activity

3 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    6/89 engine detections

    View source
  3. Added to PhishDestroy

    jdbdkdbsosu.blogspot.com

    View source

Evidence & External Reports

Security Analysis
VirusTotal 6 det. ChainPatrol URLQuery Scamadviser 80 trust SSL Labs Certificate hostname mismatch CF Radar Malicious WOT Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked 0 stored notification records Content unavailable

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Immediate steps Find reporting contacts

Official reporting routes

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including jdbdkdbsosu.blogspot.com)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
About this reportSources, observation dates and corrections

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.

Request a correction or appeal How PhishDestroy works
Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/jdbdkdbsosu.blogspot.com"
  title="PhishDestroy threat report for jdbdkdbsosu.blogspot.com"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>