Skip to security report
Recorded security signals
Stored VirusTotal result: 18/92 engines flagged. malicious: 15. suspicious: 3. Analysis time (as stored): 2026-11-04T13:55:42Z. Retrieved (as stored): 2026-11-08T02:30:39Z. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
budzdablab.com favicon

budzdablab.com

In short

PhishDestroy first recorded budzdablab.com on 2026-11-07. Stored VirusTotal result: 18/92 engines flagged. malicious: 15. suspicious: 3. Analysis time (as stored): 2026-11-04T13:55:42Z. Retrieved (as stored): 2026-11-08T02:30:39Z.

Registrar
United StatesGoDaddy
Resolved IP
Germany207.154.218.72DigitalOcean, LLC
Registered
Aug 25, 2023
First observed
Nov 7, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
VirusTotal detections: 18/92
VirusTotal
engine detections ·
OTX
community references
URLScan
engine verdict · score 92
Page captures
open gallery
Domain age
registered 2023-08-25 according to WHOIS
OTX: 4 refs Nov 7, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded budzdablab.com on 2026-11-07. Stored VirusTotal result: 18/92 engines flagged. malicious: 15. suspicious: 3. Analysis time (as stored): 2026-11-04T13:55:42Z. Retrieved (as stored): 2026-11-08T02:30:39Z. Risk: critical (100/100). Registrar: GoDaddy. Status: Last known active. Hosting: DigitalOcean, LLC. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
18 / 92
Hosting
Germany207.154.218.72DigitalOcean, LLC
Registrar
United StatesGoDaddy
Registered
Aug 25, 2023
OTX
4 community refs
Page captures
2

Recorded source summary

PhishDestroy stores a record for budzdablab.com. Source observations are dated separately; missing checks do not establish safety.

A reviewed analysis is not available for this text revision. Consult the dated source records below.

Source evidenceVirusTotal 18 / 92 · OTX 4 references 6 sources

VirusTotal

18 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 15 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
44
Malicious
15
Suspicious
3
Undetected
30

Vendor labels

DNS8
suspicious
ESET
suspicious
VIPRE
phishing
G-Data
phishing
Lionic
phishing
Sophos
phishing
CyRadar
phishing
Webroot
malicious
Fortinet
phishing
SOCRadar
phishing
Kaspersky
phishing
Seclookup
malicious
Gridinsoft
suspicious
SafeToOpen
phishing
ADMINUSLabs
malicious
BitDefender
phishing
alphaMountain.ai
malicious
Forcepoint ThreatSeeker
phishing

Reputation score

0

Tags

  • dga

Registrar

GoDaddy.com, LLC

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    9576
    Type
    TXT
    Value
    v=spf1 +a +mx +ip4:23.106.55.197 include:spf.greengeeks.net ~all
  • TTL, seconds
    14400
    Type
    A
    Value
    207.154.218.72
  • TTL, seconds
    21600
    Type
    NS
    Value
    ns2.greengeeks.net
  • TTL, seconds
    21600
    Type
    SOA
    Responsible mailbox
    root.sgp200.greengeeks.net
    Value
    ns1.greengeeks.net
  • TTL, seconds
    21600
    Type
    NS
    Value
    ns1.greengeeks.net
  • TTL, seconds
    14400
    Type
    MX
    Value
    budzdablab.com
    Priority
    0

DNS records observed

JARM fingerprint

27d40d40d00040d00042d43d000000b5ce48eb9aaa95d750e8df42b900e12b

Certificate

Subject alternative names
  • hotelpulse.pliroforikiaigaiou.com
Issuer
Let's Encrypt / YE2
Serial
542526ae428c897414fdd3715e3b5bf9805
SHA-256
5c1febbdfeb787923da64d935680411c823efbf51c7c3bc8549e9d0e9084dbbc
Subject
hotelpulse.pliroforikiaigaiou.com
Valid until
Valid from

Registration record

Registrar
GoDaddy.com, LLC
Registrar IANA ID
146
Registrar URL
http://www.godaddy.com
Registered
Updated
Expires
Status
  • clientDeleteProhibited
  • clientRenewProhibited
  • clientTransferProhibited
  • clientUpdateProhibited
Nameservers
  • ns1.greengeeks.net
  • ns2.greengeeks.net
DNSSEC
unsigned

Registry data (RDAP)

Status
  • client delete prohibited
  • client renew prohibited
  • client transfer prohibited
  • client update prohibited
Registry events
Expiration
Last changed
Registration
Last RDAP database update
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 44,
    "malicious": 15,
    "suspicious": 3,
    "undetected": 30
}
Vendor labels
{
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "SafeToOpen": "phishing",
    "ADMINUSLabs": "malicious",
    "BitDefender": "phishing",
    "alphaMountain.ai": "malicious",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
Registrar
GoDaddy.com, LLC
Created
2023-08-25T15:23:07Z
Expires
2027-08-25T15:23:07Z
Updated
2026-08-26T14:36:15Z
First seen
2024-03-05T07:40:33Z
DNS records
[
    {
        "ttl": 9576,
        "type": "TXT",
        "value": "v=spf1 +a +mx +ip4:23.106.55.197 include:spf.greengeeks.net ~all"
    },
    {
        "ttl": 14400,
        "type": "A",
        "value": "207.154.218.72"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns2.greengeeks.net"
    },
    {
        "ttl": 21600,
        "type": "SOA",
        "rname": "root.sgp200.greengeeks.net",
        "value": "ns1.greengeeks.net"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns1.greengeeks.net"
    },
    {
        "ttl": 14400,
        "type": "MX",
        "value": "budzdablab.com",
        "priority": 0
    }
]
Dns at
2026-11-04T14:01:13Z
Jarm
27d40d40d00040d00042d43d000000b5ce48eb9aaa95d750e8df42b900e12b
Certificate
{
    "san": [
        "hotelpulse.pliroforikiaigaiou.com"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "542526ae428c897414fdd3715e3b5bf9805",
    "sha256": "5c1febbdfeb787923da64d935680411c823efbf51c7c3bc8549e9d0e9084dbbc",
    "subject": "hotelpulse.pliroforikiaigaiou.com",
    "valid_to": "2026-09-14T10:35:01Z",
    "valid_from": "2026-06-16T10:35:02Z"
}
Registration record
{
    "registrar": "GoDaddy.com, LLC",
    "registrar_iana_id": "146",
    "registrar_url": "http://www.godaddy.com",
    "created": "2023-08-25T15:23:07Z",
    "updated": "2026-08-26T14:36:15Z",
    "expires": "2027-08-25T15:23:07Z",
    "status": [
        "clientDeleteProhibited",
        "clientRenewProhibited",
        "clientTransferProhibited",
        "clientUpdateProhibited"
    ],
    "nameservers": [
        "ns1.greengeeks.net",
        "ns2.greengeeks.net"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "client delete prohibited",
        "client renew prohibited",
        "client transfer prohibited",
        "client update prohibited"
    ],
    "events": {
        "expiration": "2027-08-25T15:23:07Z",
        "last changed": "2026-08-26T14:36:15Z",
        "registration": "2023-08-25T15:23:07Z",
        "last update of RDAP database": "2026-11-01T13:24:00Z"
    }
}
Separate collector summary

This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.

source
VirusTotal
scope
unknown
result_state
observed
numerator
18
denominator
92
malicious
null
suspicious
null
vendors
["ADMINUSLabs","alphaMountain.ai","BitDefender","CyRadar","DNS8","ESET","Forcepoint ThreatSeeker","Fortinet","G-Data","Gridinsoft","Kaspersky","Lionic","SafeToOpen","Seclookup","SOCRadar","Sophos","VIPRE","Webroot"]
observed_at
2026-11-04 13:55:42
checked_at
2026-11-08 03:30:39
fetched_at
2026-11-08 02:30:40
time_basis
as stored; legacy timezone not established

URLScan

Malicious · engine verdict · score 92

SHA-256 ef871e2655eb0d0817da661e5a1ca7aba65c1bd222013a207fd096b3160aa6a9

Open report
URLScanOriginal source recordObserved: 18 fields

Observed: · Retrieved:

Report ID

019e2ab9-b68c-7338-a5d7-1d39b38b59f1

Final URL

https://budzdablab.com/

HTTP response

404

Redirect type

https-only

Redirects

  • To
    https://budzdablab.com/
    From
    http://budzdablab.com/
    Status
    307

IP address

207.154.218.72

Contacted IP addresses

  • 207.154.218.72

Autonomous systems (ASN)

  • 14061

Server countries

  • DE

Document hash

ecf14b9ebe7061cddc7e2097a66c90692cc9c1d70d96b5f7ebdd14a0dbb61f54

TLS session and certificate

Subject alternative names
  • budzdablab.com
Cipher
AES_256_GCM
Issuer
E7
Subject
budzdablab.com
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

992

Registered domain age, days

992

Certificate age, days

0

Certificate validity, days

89

Page requests

2

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
92
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP headers

Server
nginx/1.26.3
Content-type
text/html; charset=utf-8
Original source fields · JSON
Uuid
019e2ab9-b68c-7338-a5d7-1d39b38b59f1
Final url
https://budzdablab.com/
Status
404
Redirected
https-only
Redirects
[
    {
        "to": "https://budzdablab.com/",
        "from": "http://budzdablab.com/",
        "status": 307
    }
]
Ip
207.154.218.72
Contacted IP addresses
[
    "207.154.218.72"
]
Asns
[
    "14061"
]
Countries
[
    "DE"
]
Document hash
ecf14b9ebe7061cddc7e2097a66c90692cc9c1d70d96b5f7ebdd14a0dbb61f54
Tls
{
    "san": [
        "budzdablab.com"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "E7",
    "subject": "budzdablab.com",
    "protocol": "TLS 1.3",
    "valid_to": "2026-08-12T11:12:12Z",
    "valid_from": "2026-05-14T11:12:13Z"
}
Domain age days
992
Apex age days
992
Tls age days
0
Tls valid days
89
Requests
2
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 92,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "nginx/1.26.3",
    "content-type": "text/html; charset=utf-8"
}

OTX

4 community references

Open report

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

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

Collected source details

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

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 9 fields

Mail configuration

MX records
  • budzdablab.com
SPF record
v=spf1 +a +mx +ip4:23.106.55.197 include:spf.greengeeks.net ~all
DKIM
  • default
DMARC
Yes
DKIM key size, bits
2048
SPF lookups
4

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Ports

Open ports
  • 22
  • 80
  • 443

DNS servers

Nameservers
  • IP address
    75.2.69.7
    Host
    ns1.greengeeks.net
  • IP address
    99.83.188.187
    Host
    ns2.greengeeks.net
DNS zone
budzdablab.com

Location

IP address
207.154.218.72
ASN
14061
Organization
DigitalOcean, LLC
City
Frankfurt am Main
Country
DE

DNS records

A
  • 207.154.218.72
MX
  • Mail server
    budzdablab.com
    Priority
    0
NS
  • ns2.greengeeks.net
  • ns1.greengeeks.net
SOA
Primary nameserver
ns1.greengeeks.net
Hostmaster
root.sgp200.greengeeks.net
Serial
2026051406
Refresh, seconds
3600
Retry, seconds
1800
Expiry, seconds
1209600
Minimum TTL, seconds
86400
TXT
  • v=spf1 +a +mx +ip4:23.106.55.197 include:spf.greengeeks.net ~all

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

IP lookup

IP address
207.154.218.72
IP version
4

Registration record

Registrar
GoDaddy.com, LLC
Registered
Updated
Expires
Status
  • clientDeleteProhibited https://icann.org/epp
  • clientRenewProhibited https://icann.org/epp
  • clientTransferProhibited https://icann.org/epp
  • clientUpdateProhibited https://icann.org/epp
Nameservers
  • ns1.greengeeks.net
  • ns2.greengeeks.net
Original source fields · JSON
Mail configuration
{
    "mx": [
        "budzdablab.com"
    ],
    "spf": "v=spf1 +a +mx +ip4:23.106.55.197 include:spf.greengeeks.net ~all",
    "dkim": [
        "default"
    ],
    "dmarc": true,
    "dkim_bits": 2048,
    "spf_lookups": 4
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Ports
{
    "open": [
        22,
        80,
        443
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "75.2.69.7",
            "host": "ns1.greengeeks.net"
        },
        {
            "ip": "99.83.188.187",
            "host": "ns2.greengeeks.net"
        }
    ],
    "zone": "budzdablab.com"
}
Location
{
    "ip": "207.154.218.72",
    "asn": "14061",
    "org": "DigitalOcean, LLC",
    "city": "Frankfurt am Main",
    "country": "DE"
}
DNS records
{
    "A": [
        "207.154.218.72"
    ],
    "MX": [
        "{\"exchange\": \"budzdablab.com\", \"priority\": 0}"
    ],
    "NS": [
        "ns2.greengeeks.net",
        "ns1.greengeeks.net"
    ],
    "SOA": "{\"nsname\": \"ns1.greengeeks.net\", \"hostmaster\": \"root.sgp200.greengeeks.net\", \"serial\": 2026051406, \"refresh\": 3600, \"retry\": 1800, \"expire\": 1209600, \"minttl\": 86400}",
    "TXT": [
        "v=spf1 +a +mx +ip4:23.106.55.197 include:spf.greengeeks.net ~all"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Get ip
{
    "ip": "207.154.218.72",
    "family": 4
}
Registration record
{
    "registrar": "GoDaddy.com, LLC",
    "created": "2023-08-25T15:23:07Z",
    "updated": "2026-08-26T14:36:15Z",
    "expires": "2027-08-25T15:23:07Z",
    "status": [
        "clientDeleteProhibited https://icann.org/epp",
        "clientRenewProhibited https://icann.org/epp",
        "clientTransferProhibited https://icann.org/epp",
        "clientUpdateProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "ns1.greengeeks.net",
        "ns2.greengeeks.net"
    ]
}

Questions about budzdablab.com

Is budzdablab.com legit?

PhishDestroy rates budzdablab.com as critical risk (100/100) from the recorded evidence; it was first recorded on 2026-11-07. Stored VirusTotal result: 18/92 engines flagged. malicious: 15. suspicious: 3. Analysis time (as stored): 2026-11-04T13:55:42Z. Retrieved (as stored): 2026-11-08T02:30:39Z. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is budzdablab.com safe to connect a wallet?

This report does not record which wallet requests budzdablab.com makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.

What should I do if I used budzdablab.com?

It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority; a report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Last checked

Stored Capture · 2 captures

All capture links and hashes (2)

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 92 report ↗
IP Reputation Germany207.154.218.72 abuse score 0/100 0 reports checked Nov 7, 2026 last reported
OTX tags 2026-11activeall-domainsblocklistcontentcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
Registrar GoDaddy US(US)
RegistrationCreated Aug 25, 2023 — Expires Aug 25, 2027
HTTP Status308 Permanent Redirect
Technical detailsProvenance & timestamps
First DetectedNov 7, 2026
Submitted URLhttp://budzdablab.com/
Favicon Hash
Observed page title
404 Not Found
TLS Certificate
Issued by E7

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Germany207.154.218.72
Network ASN
AS14061
Organization
DigitalOcean, LLC
Observed location
GermanyFrankfurt am Main, DE
Server header
nginx/1.26.3

Nameservers 2

  • ns2.greengeeks.net
  • ns1.greengeeks.net

SOA

  • nsname: ns1.greengeeks.net
  • hostmaster: root.sgp200.greengeeks.net
  • serial: 2026051406
  • refresh: 3600
  • retry: 1800
  • expire: 1209600
  • minttl: 86400

Registrar abuse contact VirusTotal WHOIS

Mail routing 1 MX record

  • budzdablab.com

Location describes the IP network.

TLS certificate

Issuer
E7
Valid from
2026-05-14 11:12:13
Valid until
2026-08-12 11:12:12
Hostname coverage
Stored certificate expired or unverified
Validity
Stored certificate expired
Collection source
PhishDestroy collector
Certificate fingerprint5c1febbdfeb787923da64d935680411c823efbf51c7c3bc8549e9d0e9084dbbc
Certificate names · 1 SAN
  • budzdablab.com

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

Latest Classified Outcome 2026-11-08 00:36:00 UTC

The site was redirecting visitors elsewhere at the latest check.

Technical details
Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Unreachable Content: Unknown DNS: Stale Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-11-08 00:36:00 UTC
RDAP registration
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.
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

18 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
DNS8
ESET
VIPRE
G-Data
Lionic
Sophos
CyRadar
Webroot
Fortinet
SOCRadar
Kaspersky
Seclookup
Gridinsoft
SafeToOpen
ADMINUSLabs
BitDefender
alphaMountain.ai
Forcepoint ThreatSeeker

Captured network requests

Network requests: 2 SHA-256 hashes: 2 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-07 13:13 UTC.

Open this scan on URLScan 019e2ab9-b68c-7338-a5d7-1d39b38b59f1 ↗

Stored observation history1

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

    redirected

    http_redirect

All retained availability observations5

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

  1. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    308
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-08 01:36:00.000000
    Evidence SHA-256
    fe8f907932671b9ae196955311798bc97153dbff288e790b26700be29254a79e
    HTTP probe value as recorded
    308
    Evidence timestamp as recorded
    2026-11-08 01:36:00
    Evidence reason
    redirect
  2. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    308
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-08 01:36:00.000000
    Evidence SHA-256
    fe8f907932671b9ae196955311798bc97153dbff288e790b26700be29254a79e
    HTTP probe value as recorded
    308
    Evidence timestamp as recorded
    2026-11-08 01:36:00
    Evidence reason
    redirect
  3. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-07 23:22:04.326583
    Evidence SHA-256
    19ed99e260d67463304cd035997394a09991119b8c1f635f2967c41ae291fdce
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-07 23:22:04.326583
    Evidence reason
  4. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-07 14:08:06.000000
    Evidence SHA-256
    385bdb9c3430947d68e909ee9d4fee7eb06e1c8f95313a7e56c5c772269c0cee
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-07 14:08:06
    Evidence reason
  5. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-07 14:08:06.000000
    Evidence SHA-256
    385bdb9c3430947d68e909ee9d4fee7eb06e1c8f95313a7e56c5c772269c0cee
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-07 14:08:06
    Evidence reason

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · in progress

Recorded events: 8. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested Recorded: 1 of 1
  • Threat Ingested
    budzdablab.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · OTX Community References · Forensic Evidence Collected Recorded: 6 of 6
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 92
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • VirusTotal
    Detections recorded on VirusTotal: 18/92
  • OTX Community References
    Community publication references on AlienVault OTX: 4. References are not vendor verdicts and are excluded from the evidence score.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

4 entries
  1. AlienVault OTX

    4 community references

    View source
  2. Added to PhishDestroy

    budzdablab.com

    View source
  3. VirusTotal

    18/92 engine detections

    View source
  4. URLScan

    Malicious · engine verdict · score 92

    View source
How we investigate & report

Public scans, evidence and abuse channels

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
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. 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.

All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Check for cloaking

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

budzdablab.com

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

4 evidence signal groups linked Last known active
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Official reporting routes

More official reporting routes
FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

Report to Your Local Authorities

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

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

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.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website

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 budzdablab.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

Stay Informed, Stay Safe

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

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 →
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.

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.

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/budzdablab.com"
  title="PhishDestroy threat report for budzdablab.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>