Skip to security report
Domain security and threat intelligence
b5r4y-igr8u-t4h8b-bd24t-ug4ri-y4v8b.netlify.app favicon

b5r4y-igr8u-t4h8b-bd24t-ug4ri-y4v8b.netlify.app

In short

b5r4y-igr8u-t4h8b-bd24t-ug4ri-y4v8b.netlify.app is a blocklisted domain detected by PhishDestroy on 2026-10-23. Risk: critical (75/100). Registrar: Netlify. Status: Last known active. Hosting: Amazon.com, Inc. Do not enter credentials or connect a wallet.

“Bitbuy”

Registrar
Netlify
Resolved IP
63.176.8.218
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
Stored blocklist matches: 2
Oct 23, 2026 CDN
API
This domain has been flagged as malicious
Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
Google Safe Browsing
Page captures
open gallery
Source evidence 3 sources

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

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.

URLScan · 2026-10-23T01:55:57Z

Observed: · Retrieved:

Uuid
01a16678-bab9-77ba-abd9-7d1c526c8da6
Final url
https://b5r4y-igr8u-t4h8b-bd24t-ug4ri-y4v8b.netlify.app/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://b5r4y-igr8u-t4h8b-bd24t-ug4ri-y4v8b.netlify.app/",
        "from": "http://b5r4y-igr8u-t4h8b-bd24t-ug4ri-y4v8b.netlify.app/",
        "status": 307
    }
]
Ip
63.176.8.218
Ptr
ec2-63-176-8-218.eu-central-1.compute.amazonaws.com
Contacted domains
[
    "embed.tawk.to",
    "va.tawk.to",
    "fonts.googleapis.com"
]
Contacted IP addresses
[
    "104.20.42.169",
    "142.251.13.95",
    "63.176.8.218"
]
Asns
[
    "13335",
    "15169",
    "16509"
]
Countries
[
    "US",
    "DE"
]
Document hash
d1d01a0586ebab59c97843dad1e4176bd4b2c9b88f6ad3d04c681a06c0016f8c
Script hashes
[
    "f36844906ad2309877aae3121b87fb15b9e09803cb4c333adc7e1e35ac92e14b",
    "c38e8c5a40f00294b6ba95bea3c5bd346678b4845cc7eed1d67c70db1bb0d581",
    "52bb7446862e479f013494ba2cefb1105c68e66f5be24fb57173c81bb395f8e1"
]
Globals
[
    "$",
    "jQuery",
    "bootstrap",
    "Tawk_API",
    "Tawk_LoadStart",
    "$_Tawk_AccountKey",
    "$_Tawk_WidgetId",
    "$_Tawk_Unstable",
    "$_Tawk",
    "__VUE_INSTANCE_SETTERS__",
    "__VUE_SSR_SETTERS__",
    "$__TawkEngine",
    "EventEmitter",
    "$__TawkSocket",
    "__i18next_supportNoticeShown"
]
Cookies
[
    "twk_idm_key",
    "TawkConnectionTime"
]
Storage keys
[
    "exist_test"
]
Tls
{
    "san": [
        "*.netlify.app",
        "netlify.app"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "DigiCert Global G2 TLS RSA SHA256 2020 CA1",
    "subject": "*.netlify.app",
    "protocol": "TLS 1.3",
    "valid_to": "2027-03-19T23:59:59Z",
    "valid_from": "2026-02-16T00:00:00Z"
}
Domain age days
29
Apex age days
29
Tls age days
249
Tls valid days
396
Requests
17
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 100,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "Netlify",
    "content-type": "text/html; charset=UTF-8",
    "strict-transport-security": "max-age=31536000; includeSubDomains; preload"
}
VirusTotal · 2026-09-23T09:19:00Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 54,
    "malicious": 2,
    "suspicious": 0,
    "undetected": 36
}
Vendor labels
{
    "Fortinet": "phishing",
    "LevelBlue": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
Registrar
Name.com, Inc.
Created
2018-05-08T22:48:05Z
Expires
2025-05-08T22:48:05Z
Updated
2024-04-11T16:00:14Z
First seen
2026-09-23T09:19:13Z
DNS records
[
    {
        "ttl": 120,
        "type": "A",
        "value": "98.84.224.111"
    },
    {
        "ttl": 311,
        "type": "AAAA",
        "value": "2600:1f18:16e:df01::259"
    },
    {
        "ttl": 120,
        "type": "A",
        "value": "18.208.88.157"
    },
    {
        "ttl": 311,
        "type": "AAAA",
        "value": "2600:1f18:16e:df01::258"
    }
]
Dns at
2026-09-23T09:19:14Z
Jarm
40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319
Certificate
{
    "san": [
        "*.netlify.app",
        "netlify.app"
    ],
    "issuer": "DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1",
    "serial": "cd5d0afb0611b5bd9d692535c0ca7c4",
    "sha256": "bc3a8134c21a842e64ea34d488826dd2ba50f59a3bcbaed1e6b71a4242de1478",
    "subject": "*.netlify.app",
    "valid_to": "2027-03-19T23:59:59Z",
    "valid_from": "2026-02-16T00:00:00Z"
}
Registration record
{
    "registrar": "Name.com, Inc.",
    "registrar_iana_id": "625",
    "registrar_url": "http://www.name.com",
    "created": "2018-05-08T22:48:05Z",
    "updated": "2024-04-11T16:00:14Z",
    "expires": "2025-05-08T22:48:05Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "dns1.p01.nsone.net",
        "dns2.p01.nsone.net",
        "dns3.p01.nsone.net",
        "dns4.p01.nsone.net"
    ],
    "dnssec": "unsigned"
}
Website checks · 2026-10-23T07:05:37Z
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "count": 2,
    "domain": "netlify.app",
    "issuers": [
        "digicert.com;account=2d83e9ac9b6776c3f215150f6ebceea8cefe3bc2e1fb5efffb1d71e200575226"
    ]
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-10-23T01:37:06Z",
    "first": "2026-10-23T01:37:06Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 2742
}
Page title and metadata
{
    "title": "Bitbuy"
}
Trackers
{
    "requests": 10,
    "trackers": [
        {
            "name": "Tawk",
            "company": "Tawk",
            "country": "US",
            "category": "Customer Interaction",
            "requests": 1
        },
        {
            "name": "Google Fonts",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        }
    ]
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 2,
        "tls": 12,
        "wait": 10,
        "connect": 7,
        "download": 0
    },
    "response_ms": 31
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_128_GCM_SHA256",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Carbon
{
    "bytes": 4795,
    "co2_grams": 0.0002,
    "cleaner_than": 88
}
Dns server
{
    "ns": [
        {
            "ip": "198.51.44.1",
            "host": "dns1.p01.nsone.net"
        },
        {
            "ip": "198.51.45.1",
            "host": "dns2.p01.nsone.net"
        },
        {
            "ip": "198.51.44.65",
            "host": "dns3.p01.nsone.net"
        },
        {
            "ip": "198.51.45.65",
            "host": "dns4.p01.nsone.net"
        }
    ],
    "zone": "netlify.app"
}
Location
{
    "ip": "2a05:d014:58f:6200::259",
    "asn": "16509",
    "org": "Amazon.com, Inc.",
    "city": "Frankfurt",
    "country": "DE"
}
Ssl
{
    "issuer": "DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1",
    "subject": "*.netlify.app"
}
DNS records
{
    "A": [
        "63.176.8.218",
        "35.157.26.135"
    ],
    "AAAA": [
        "2a05:d014:58f:6200::259",
        "2a05:d014:58f:6200::258"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=31536000; includeSubDomains; preload",
    "message": "Site is compatible with the HSTS preload list!",
    "compatible": true
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": "max-age=31536000; includeSubDomains; preload",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "2a05:d014:58f:6200::259",
    "family": 6
}
Redirects
{
    "chain": [
        "https://b5r4y-igr8u-t4h8b-bd24t-ug4ri-y4v8b.netlify.app"
    ]
}
Tech stack
{
    "technologies": [
        "Bootstrap",
        "Tawk.to",
        "jQuery",
        "Netlify",
        "HSTS",
        "DigiCert",
        "Popper"
    ]
}
Page links
{
    "internal_count": 1
}
HTTP headers
{
    "headers": {
        "server": "Netlify",
        "content-type": "text/html; charset=UTF-8",
        "strict-transport-security": "max-age=31536000; includeSubDomains; preload"
    }
}

Questions about b5r4y-igr8u-t4h8b-bd24t-ug4ri-y4v8b.netlify.app

Is b5r4y-igr8u-t4h8b-bd24t-ug4ri-y4v8b.netlify.app legit?

No. PhishDestroy classifies b5r4y-igr8u-t4h8b-bd24t-ug4ri-y4v8b.netlify.app as a blocklisted domain (risk: critical, 75/100); it was first detected on 2026-10-23. Treat the site as unsafe.

Is b5r4y-igr8u-t4h8b-bd24t-ug4ri-y4v8b.netlify.app safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on b5r4y-igr8u-t4h8b-bd24t-ug4ri-y4v8b.netlify.app. 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 b5r4y-igr8u-t4h8b-bd24t-ug4ri-y4v8b.netlify.app?

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 matchesMetaMask · PhishDestroy · SEAL 3
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Stored Capture · 4 captures

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context Netlify shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider Netlify US(US)
Abuse contactabuse@netlify.com
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 23, 2026
DOM Analysisanalyzed Oct 23, 2026score 75/100
Submitted URLhttp://b5r4y-igr8u-t4h8b-bd24t-ug4ri-y4v8b.netlify.app/
Favicon Hash
Observed page title
Bitbuy
TLS Certificate
Issued by DigiCert Global G2 TLS RSA SHA256 2020 CA1 · stored validity ends in 147 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
63.176.8.218
Network ASN
AS16509
Organization
AWS EC2 (eu-central-1)
Observed location
Frankfurt, DE
Server header
Netlify

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

TLS certificate

Issuer
DigiCert Global G2 TLS RSA SHA256 2020 CA1
Valid from
2026-02-16 00:00:00
Valid until
2027-03-19 23:59:59
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintbc3a8134c21a842e64ea34d488826dd2ba50f59a3bcbaed1e6b71a4242de1478
Certificate names · 2 SANs
  • *.netlify.app
  • netlify.app

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

Report This Domain Submit evidence & help protect others

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://b5r4y-igr8u-t4h8b-bd24t-ug4ri-y4v8b.netlify.app/
Final URL: https://b5r4y-igr8u-t4h8b-bd24t-ug4ri-y4v8b.netlify.app/
Bitbuy
Response
HTTP 200
HTML body
4.7 KB
Compressed
1.7 KB
Links
2 internal · 0 external
Detected technologies
bootstrapjquery
Selected response headers
Cache-Control: public,max-age=0,must-revalidate
Content-Encoding: gzip
Content-Type: text/html; charset=UTF-8
Server: Netlify
Security headers present
Strict-Transport-Security
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 13
Accept-Ranges
bytes
Age
0
Cache-Control
public,max-age=0,must-revalidate
Cache-Status
"Netlify Edge"; fwd=miss; fwd-status=200; stored
Content-Encoding
gzip
Content-Type
text/html; charset=UTF-8
Date
Fri, 23 Oct 2026 01:38:32 GMT
Etag
"6a105a96dea9c96f0d96545c6ea86a80-ssl-df"
Server
Netlify
Strict-Transport-Security
max-age=31536000; includeSubDomains; preload
Transfer-Encoding
chunked
Vary
Accept-Encoding
X-Nf-Request-Id
01M5K6HRT9M740BZSZZQ64WY5D

Values retained by the collector; long values may be shortened during collection.

Registration & observation details1

Availability observations

Last reachable observation

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

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 · First collection record

    Reachable

Recorded activity

3 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. Added to PhishDestroy

    b5r4y-igr8u-t4h8b-bd24t-ug4ri-y4v8b.netlify.app

    View source
  3. URLScan

    Page captured

    View source

Check for cloaking

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

b5r4y-igr8u-t4h8b-bd24t-ug4ri-y4v8b.netlify.app

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked 0 stored notification records Last known active

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.

Official reporting routes

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 b5r4y-igr8u-t4h8b-bd24t-ug4ri-y4v8b.netlify.app)
  • 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

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.

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/b5r4y-igr8u-t4h8b-bd24t-ug4ri-y4v8b.netlify.app"
  title="PhishDestroy threat report for b5r4y-igr8u-t4h8b-bd24t-ug4ri-y4v8b.netlify.app"
  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>