Skip to security report
Analytics Dashboard
Books A Million Gift Card Phishing — Listed on PhishDestroy
Stored PhishDestroy threat listing. VirusTotal analysis stored; no vendor detections were recorded at check time. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
bamkart.shop favicon

bamkart.shop

In short

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

“$750 Books A Million Gift Card”

Review the evidence
Registrar
GoDaddy.com
Resolved IP
United Kingdom188.114.97.3CloudFLARENET-EU · CDN
Registered
Oct 6, 2026
First observed
Oct 23, 2026
PhishDestroy assessment Critical
83/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
Stored PhishDestroy threat listing Young domain: 25 days old
VirusTotal
0 / 92
engine detections ·
URLScan
Malicious
engine verdict · score 99
Page captures
4
open gallery
Domain age
25 days
registered 2026-10-06 according to WHOIS
Oct 23, 2026 CDN
X Telegram API
Source evidenceVirusTotal 0 / 92 8 sources

Cloudflare Radar

Suspicious

Open report
Cloudflare RadarOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Report ID

f267f6d2-1be6-45ed-a990-ceed4e6d3b7c

Final URL

https://bamkart.shop/

HTTP response

200

Navigation history

  • URL
    https://bamkart.shop/
    Status
    200

DOM structure hash

f01683f6222273eebfeb8d54fd7cc182f09bdcf794d3f5db6719b73fa306f617

Document hash

4e6ca92208060d1c269aa0607ee27c721ecbbd0c31edff09c755aa9100ff6ea8

Domain risk categories

  • Newly Seen Domains
  • Security Risks

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    bamkart.shop
    Type
    A
    Value
    104.21.20.140
  • Name
    bamkart.shop
    Type
    A
    Value
    172.67.192.243
  • Name
    bamkart.shop
    Type
    AAAA
    Value
    2606:4700:3030::ac43:c0f3
  • Name
    bamkart.shop
    Type
    AAAA
    Value
    2606:4700:3031::6815:148c

DNSSEC valid

No

IP address

104.21.20.140
Original source fields · JSON
Uuid
f267f6d2-1be6-45ed-a990-ceed4e6d3b7c
Final url
https://bamkart.shop/
Status
200
History
[
    {
        "url": "https://bamkart.shop/",
        "status": 200
    }
]
DOM structure hash
f01683f6222273eebfeb8d54fd7cc182f09bdcf794d3f5db6719b73fa306f617
Document hash
4e6ca92208060d1c269aa0607ee27c721ecbbd0c31edff09c755aa9100ff6ea8
Domain risks
[
    "Newly Seen Domains",
    "Security Risks"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "bamkart.shop",
        "type": "A",
        "value": "104.21.20.140"
    },
    {
        "name": "bamkart.shop",
        "type": "A",
        "value": "172.67.192.243"
    },
    {
        "name": "bamkart.shop",
        "type": "AAAA",
        "value": "2606:4700:3030::ac43:c0f3"
    },
    {
        "name": "bamkart.shop",
        "type": "AAAA",
        "value": "2606:4700:3031::6815:148c"
    }
]
Dnssec valid
false
Ip
104.21.20.140

URLScan

Malicious · engine verdict · score 99

SHA-256 4a51e7485eeecc291836ee110e2c4e4b08aca7da151307bc3112f893173e2f26

Open report
URLScanOriginal source recordObserved: 18 fields

Observed: · Retrieved:

Report ID

01a16947-9f69-756b-934e-2ec2ab319adf

Final URL

https://bamkart.shop/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://bamkart.shop/
    From
    http://bamkart.shop/
    Status
    307

IP address

188.114.96.3

Contacted IP addresses

  • 188.114.96.3

Autonomous systems (ASN)

  • 13335

Linked domains

  • linkthem.net

Document hash

83e2e3b2111da2113e78d12693b129259378c9b43cd1a65efc4c2ae37b064bd9

TLS session and certificate

Subject alternative names
  • bamkart.shop
  • *.bamkart.shop
Cipher
AES_128_GCM
Issuer
WE1
Subject
bamkart.shop
Protocol
QUIC
Valid until
Valid from

Domain age, days

16

Registered domain age, days

16

Certificate age, days

16

Certificate validity, days

90

Page requests

5

Provider verdicts

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

HTTP headers

Server
cloudflare
Content-type
text/html
Original source fields · JSON
Uuid
01a16947-9f69-756b-934e-2ec2ab319adf
Final url
https://bamkart.shop/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://bamkart.shop/",
        "from": "http://bamkart.shop/",
        "status": 307
    }
]
Ip
188.114.96.3
Contacted IP addresses
[
    "188.114.96.3"
]
Asns
[
    "13335"
]
Linked domains
[
    "linkthem.net"
]
Document hash
83e2e3b2111da2113e78d12693b129259378c9b43cd1a65efc4c2ae37b064bd9
Tls
{
    "san": [
        "bamkart.shop",
        "*.bamkart.shop"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WE1",
    "subject": "bamkart.shop",
    "protocol": "QUIC",
    "valid_to": "2027-01-04T16:59:08Z",
    "valid_from": "2026-10-06T15:59:21Z"
}
Domain age days
16
Apex age days
16
Tls age days
16
Tls valid days
90
Requests
5
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 99,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html"
}
Separate monitor record · date not recorded

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

record_source
domain_monitor.urlscan
uuid
01a16576-859c-77cb-8796-715d2c5bc2fc
score
null
malicious
null
result_at
null
enriched_at
2026-10-24T08:14:31Z
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":"2026-10-24 10:14:31"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

VirusTotal

0 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 7 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
55
Malicious
0
Suspicious
0
Undetected
37

Reputation score

0

First seen

DNS records

  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3031::6815:148c
  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    emerson.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    104.21.20.140
  • TTL, seconds
    21600
    Type
    NS
    Value
    emerson.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3030::ac43:c0f3
  • TTL, seconds
    300
    Type
    A
    Value
    172.67.192.243
  • TTL, seconds
    21600
    Type
    NS
    Value
    imani.ns.cloudflare.com

DNS records observed

JARM fingerprint

27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c

Certificate

Subject alternative names
  • bamkart.shop
  • *.bamkart.shop
Issuer
Google Trust Services / WE1
Serial
2cb3bdd686fc41e013ca522695c04ccb
SHA-256
5b04a8bc126dbab484393ba8517afaf8093e2a1b28fde8a3037083ad038d09de
Subject
bamkart.shop
Valid until
Valid from
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 55,
    "malicious": 0,
    "suspicious": 0,
    "undetected": 37
}
Reputation
0
First seen
2026-10-06T17:36:46Z
DNS records
[
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3031::6815:148c"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "emerson.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.20.140"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "emerson.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3030::ac43:c0f3"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.192.243"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "imani.ns.cloudflare.com"
    }
]
Dns at
2026-10-23T07:13:32Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "bamkart.shop",
        "*.bamkart.shop"
    ],
    "issuer": "Google Trust Services / WE1",
    "serial": "2cb3bdd686fc41e013ca522695c04ccb",
    "sha256": "5b04a8bc126dbab484393ba8517afaf8093e2a1b28fde8a3037083ad038d09de",
    "subject": "bamkart.shop",
    "valid_to": "2027-01-04T16:59:08Z",
    "valid_from": "2026-10-06T15:59:21Z"
}
Separate source record · 0 malicious + 0 suspicious / 92 · 2026-10-23 06:55:50 UTC

The summary above and this provider record were collected at different times. Both remain available; malicious and suspicious classifications are shown separately.

record_source
collected_observations.vt
analysis_at
2026-10-23T06:55:50Z
fetched_at
2026-10-23T14:50:31Z
stats
{"timeout":0,"harmless":55,"malicious":0,"suspicious":0,"undetected":37}

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

83 / 100 · heuristic score · 0 brand references · 0 classifications

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: 24 fields

Mail configuration

SPF lookups
0

CAA records

Domain
bamkart.shop

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
1
Archived days
2
Snapshots per day
0.06
Average page size, bytes
5278

Page title and metadata

Page title
$750 Books A Million Gift Card

Trackers

Requests
3

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
2
TLS
23
Waiting
54
Connection
6
Download
0
Response time, ms
85

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1
  • TLSv1.1
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443
  • 8080

Carbon estimate

Bytes
7411
CO₂, grams
0.0003
Cleaner than, %
78

DNS servers

Nameservers
  • IP address
    172.64.35.96
    Host
    emerson.ns.cloudflare.com
  • IP address
    162.159.38.62
    Host
    imani.ns.cloudflare.com
DNS zone
bamkart.shop

Location

IP address
2a06:98c1:3120::3
ASN
13335
Organization
CloudFLARENET-EU
City
London
Country
GB

TLS certificate

Issuer
Google Trust Services / WE1
Subject
bamkart.shop

DNS records

A
  • 188.114.96.3
  • 188.114.97.3
NS
  • emerson.ns.cloudflare.com
  • imani.ns.cloudflare.com
SOA
Primary nameserver
emerson.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2416797920
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800
AAAA
  • 2a06:98c1:3120::3
  • 2a06:98c1:3121::3

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
2a06:98c1:3121::3
IP version
6

Redirects

Redirect chain
  • https://bamkart.shop

Technology stack

Technologies
  • Cloudflare
  • HTTP/3

Page links

External link addresses
  • https://linkthem.net/aff_c
External links
1

HTTP headers

Response headers
Server
cloudflare
Content-type
text/html
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "bamkart.shop"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-10-23T14:49:12Z",
    "first": "2026-10-07T20:01:40Z",
    "changes": 1,
    "days_archived": 2,
    "scans_per_day": 0.06,
    "avg_page_bytes": 5278
}
Page title and metadata
{
    "title": "$750 Books A Million Gift Card"
}
Trackers
{
    "requests": 3
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 2,
        "tls": 23,
        "wait": 54,
        "connect": 6,
        "download": 0
    },
    "response_ms": 85
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1",
        "TLSv1.1",
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443,
        8080
    ]
}
Carbon
{
    "bytes": 7411,
    "co2_grams": 0.0003,
    "cleaner_than": 78
}
Dns server
{
    "ns": [
        {
            "ip": "172.64.35.96",
            "host": "emerson.ns.cloudflare.com"
        },
        {
            "ip": "162.159.38.62",
            "host": "imani.ns.cloudflare.com"
        }
    ],
    "zone": "bamkart.shop"
}
Location
{
    "ip": "2a06:98c1:3120::3",
    "asn": "13335",
    "org": "CloudFLARENET-EU",
    "city": "London",
    "country": "GB"
}
Ssl
{
    "issuer": "Google Trust Services / WE1",
    "subject": "bamkart.shop"
}
DNS records
{
    "A": [
        "188.114.96.3",
        "188.114.97.3"
    ],
    "NS": [
        "emerson.ns.cloudflare.com",
        "imani.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"emerson.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2416797920, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}",
    "AAAA": [
        "2a06:98c1:3120::3",
        "2a06:98c1:3121::3"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "2a06:98c1:3121::3",
    "family": 6
}
Redirects
{
    "chain": [
        "https://bamkart.shop"
    ]
}
Tech stack
{
    "technologies": [
        "Cloudflare",
        "HTTP/3"
    ]
}
Page links
{
    "external": [
        "https://linkthem.net/aff_c"
    ],
    "external_count": 1
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html"
    }
}
Security Signals
SA Scamadviser Warnings 95/100
This website does not have many visitors
According to the SSL check the certificate is valid DNSFilter considers this website safe

Explore

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

Checked, no match

Last checked

Stored Capture · 4 captures

Primary capture 1 / 4
SourcePrimary capture
Recorded
StateStored capture
Position1 / 4
Open capture Wayback Download
All capture links and hashes (4)
Observed page title
$750 Books A Million Gift Card
TLS Certificate
Issued by Google Trust Services / WE1 · stored validity ends in 64 days
bamkart.shop: caution — 6/92 VirusTotal engines. PhishDestroy risk score 83/100 (critical).
Social preview card bamkart.shop: caution — 6/92 VirusTotal engines. PhishDestroy risk score 83/100 (critical). v c9ef1d1d9a50

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 99 report ↗
IP Context United Kingdom188.114.97.3 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar GoDaddy.com
Abuse contact["abuse@godaddy.com"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for bamkart.shop →
RegistrationCreated Oct 6, 2026 (25d · Very New!) — Expires Oct 6, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 23, 2026
DOM Analysisanalyzed Oct 23, 2026score 83/100
Submitted URLhttp://bamkart.shop/
Favicon Hash
ICANN OVERSIGHT

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

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.

Accreditation is a contract, not a safety seal. Verify ICANN fees Read RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
United Kingdom188.114.97.3
Network ASN
AS13335
AS name
CLOUDFLARENET - Cloudflare, Inc., US
Organization
CloudFLARENET-EU
Observed location
United KingdomLondon, GB
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • emerson.ns.cloudflare.com
  • imani.ns.cloudflare.com

SOA

  • nsname: emerson.ns.cloudflare.com
  • hostmaster: dns.cloudflare.com
  • serial: 2416797920
  • refresh: 10000
  • retry: 2400
  • expire: 604800
  • minttl: 1800

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-10-06 15:59:21
Valid until
2027-01-04 16:59:08
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint5b04a8bc126dbab484393ba8517afaf8093e2a1b28fde8a3037083ad038d09de
Certificate names · 2 SANs
  • bamkart.shop
  • *.bamkart.shop

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

viewdns.info · 188.114.97.3rapiddns.io

Latest Classified Outcome 2026-11-01 03:23:10 UTC

The site was serving its pages at the latest check.

Technical details
Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-11-01 03:23:10 UTC
RDAP registration
Observed timeline last reachable: 2026-11-01 03:23:10 UTC last content: 2026-11-01 03:23:10 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.
Threat Intel Cross-Reference · source references
ScamAdviser Public lookup
A public ScamAdviser lookup is available. Review its current score and warnings at the source; the existence of a lookup page is not itself a malicious verdict.
View on ScamAdviser
Fetched directly from the site by PhishDestroy · cached up to 24 h
Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of bamkart.shop · checked Oct 23, 2026

100
Good
Performance
FCP
0.77 s
First Contentful Paint
LCP
0.77 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
0.86 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
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://bamkart.shop/
$750 Books A Million Gift Card
Response
HTTP 200
HTML body
7.2 KB
Compressed
3.8 KB
Links
0 internal · 1 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html
CF-Cache-Status: HIT
Cache-Control: public, max-age=0, must-revalidate
Content-Encoding: gzip
Server: cloudflare
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 12
alt-svc
h3=":443"; ma=86400
Cache-Control
public, max-age=0, must-revalidate
CF-Cache-Status
HIT
CF-RAY
a4f18b8059dc7b02-FRA
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html
Date
Fri, 23 Oct 2026 14:48:50 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=Da95x3ETmbwfMe5qFKqqwT%2F36bVM0aY%2FvlCOSPYf14UM1h7JoorqHkeSjqGS0KPttE7rqg%2FYsVlwtnDjffxXqPbVUh5yZW9vfGYIYV8Kn9hc7U%2Fa1Yddx1H9L6A%2FYec%3D"}]
Server
cloudflare
Transfer-Encoding
chunked

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

Archived
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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

Captured network requests

Network requests: 5 SHA-256 hashes: 3 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-10-29 01:59 UTC.

Open this scan on URLScan 01a16947-9f69-756b-934e-2ec2ab319adf ↗

Stored observation history8

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

    live_content

    content_served

  2. Availability monitor · Recorded state

    live_content

    content_served

  3. Availability monitor · Recorded state

    live_content

    content_served

  4. Availability monitor · Recorded state

    live_content

    content_served

  5. Availability monitor · Recorded state

    live_content

    content_served

Earlier observations 3
  1. Availability monitor · Recorded state

    live_content

    content_served

  2. Availability monitor · Recorded state

    live_content

    content_served

  3. Availability monitor · Recorded state

    live_content

    content_served

All retained availability observations47

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_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 04:23:10.000000
    Evidence SHA-256
    4d5c50a59ce50b9dd1a3cf5b32e765bede96e42759c399b0faf289bd9a52b91e
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 04:23:10
    Evidence reason
    alive_content
  2. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 04:23:10.000000
    Evidence SHA-256
    4d5c50a59ce50b9dd1a3cf5b32e765bede96e42759c399b0faf289bd9a52b91e
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 04:23:10
    Evidence reason
    alive_content
  3. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:35:24.000000
    Evidence SHA-256
    e16c422eafbc5d45e7949ac25cf284409ea24879a3ccf68ef3ce2d5cd6c5b187
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:35:24
    Evidence reason
    alive_content
  4. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:35:24.000000
    Evidence SHA-256
    e16c422eafbc5d45e7949ac25cf284409ea24879a3ccf68ef3ce2d5cd6c5b187
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:35:24
    Evidence reason
    alive_content
  5. 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-10-31 11:20:09.112163
    Evidence SHA-256
    b5c6551e799cfe4d3cb298004536f14652a7bd27158039d9a8bde93b0611124a
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 11:20:09.112163
    Evidence reason
  6. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 03:55:39.000000
    Evidence SHA-256
    dcc28a0ab04fe5bb6b0004b838d028c8d1667bb3bcf7ef73aeef78337416a5b9
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 03:55:39
    Evidence reason
    alive_content
  7. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 03:55:39.000000
    Evidence SHA-256
    dcc28a0ab04fe5bb6b0004b838d028c8d1667bb3bcf7ef73aeef78337416a5b9
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 03:55:39
    Evidence reason
    alive_content
  8. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 00:02:40.000000
    Evidence SHA-256
    275689a99b61157e36355dca87b2004296911b2b46abd10f5cfd2a6586d777ed
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 00:02:40
    Evidence reason
    alive_content
  9. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 00:02:40.000000
    Evidence SHA-256
    275689a99b61157e36355dca87b2004296911b2b46abd10f5cfd2a6586d777ed
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 00:02:40
    Evidence reason
    alive_content
  10. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:03:23.000000
    Evidence SHA-256
    c143617b43f6ef6b5a452e872cf962b671710ab08bec6f90cc2b9805457f31b4
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 12:03:23
    Evidence reason
    alive_content
  11. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:03:23.000000
    Evidence SHA-256
    c143617b43f6ef6b5a452e872cf962b671710ab08bec6f90cc2b9805457f31b4
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 12:03:23
    Evidence reason
    alive_content
  12. 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-10-30 05:03:05.462458
    Evidence SHA-256
    bbc8a7612fad967fe6394ef6e3533c42adb354b0403e4f596ca1b553348f1852
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 05:03:05.462458
    Evidence reason
  13. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:03:52.000000
    Evidence SHA-256
    100eba9a5e5d8e2845c8792fc0025dbded50ad17c77c3171277d986b1b8e9a14
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:03:52
    Evidence reason
    alive_content
  14. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:03:52.000000
    Evidence SHA-256
    100eba9a5e5d8e2845c8792fc0025dbded50ad17c77c3171277d986b1b8e9a14
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:03:52
    Evidence reason
    alive_content
  15. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 12:04:19.000000
    Evidence SHA-256
    30c6e99ebb1354278b4d975442ae15de23b55099cab186a8208bc65a4f3cbebc
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:04:19
    Evidence reason
    alive_content
  16. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 12:04:19.000000
    Evidence SHA-256
    30c6e99ebb1354278b4d975442ae15de23b55099cab186a8208bc65a4f3cbebc
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:04:19
    Evidence reason
    alive_content
  17. 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-10-29 05:03:05.313035
    Evidence SHA-256
    e8d7330e223cce20a4540e7f3ccd4cc0f3b8c1f41fa08898b82c337408eae933
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-29 05:03:05.313035
    Evidence reason
  18. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 01:03:48.000000
    Evidence SHA-256
    f99f08f05d4f2881ce13e261e9d5563d17af92ee1b72aaa2dac08b68e2cc6fcd
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 01:03:48
    Evidence reason
    alive_content
  19. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 01:03:48.000000
    Evidence SHA-256
    f99f08f05d4f2881ce13e261e9d5563d17af92ee1b72aaa2dac08b68e2cc6fcd
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 01:03:48
    Evidence reason
    alive_content
  20. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 13:11:27.000000
    Evidence SHA-256
    dbe3a03e3b7a84699763cd8bcd72f52552248b7111fa6f59678ff9c2ff453242
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 13:11:27
    Evidence reason
    alive_content
  21. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 13:11:27.000000
    Evidence SHA-256
    dbe3a03e3b7a84699763cd8bcd72f52552248b7111fa6f59678ff9c2ff453242
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 13:11:27
    Evidence reason
    alive_content
  22. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 01:13:35.000000
    Evidence SHA-256
    bb7118714816a2f1a67f0e58bdd7f037294ccac4fa7e33cfb78cc82ab73f226d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 01:13:35
    Evidence reason
    alive_content
  23. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 01:13:35.000000
    Evidence SHA-256
    bb7118714816a2f1a67f0e58bdd7f037294ccac4fa7e33cfb78cc82ab73f226d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 01:13:35
    Evidence reason
    alive_content
  24. 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-10-27 21:55:09.758880
    Evidence SHA-256
    1e2e9cb047b90a10a64bb7fbd9aed4b8679f79a2b39e38a653713ebcccbeeec6
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-27 21:55:09.758880
    Evidence reason
  25. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 13:11:15.000000
    Evidence SHA-256
    dd113448a89b121a1fbb30bb8e278c6dbf0c663e55e9459454da0815dde71f9b
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 13:11:15
    Evidence reason
    alive_content
  26. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 13:11:15.000000
    Evidence SHA-256
    dd113448a89b121a1fbb30bb8e278c6dbf0c663e55e9459454da0815dde71f9b
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 13:11:15
    Evidence reason
    alive_content
  27. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 05:03:52.000000
    Evidence SHA-256
    7de97847c9164b2a1f7fe3dd45b6f368bbab96f7bacad403ffb1efa09a72c530
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 05:03:52
    Evidence reason
    alive_content
  28. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 05:03:52.000000
    Evidence SHA-256
    7de97847c9164b2a1f7fe3dd45b6f368bbab96f7bacad403ffb1efa09a72c530
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 05:03:52
    Evidence reason
    alive_content
  29. 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-10-26 21:55:09.041159
    Evidence SHA-256
    9364d16752bb56ab1a07deaf5402c56950e2c8b359744c1506357d864927fa66
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-26 21:55:09.041159
    Evidence reason
  30. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 13:00:23.000000
    Evidence SHA-256
    db5a49e07695c60d7085f5a61a083e2298c3fa8b5723c5cba3f0ad94d2ca185a
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 13:00:23
    Evidence reason
    alive_content
  31. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 13:00:23.000000
    Evidence SHA-256
    db5a49e07695c60d7085f5a61a083e2298c3fa8b5723c5cba3f0ad94d2ca185a
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 13:00:23
    Evidence reason
    alive_content
  32. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 01:03:15.000000
    Evidence SHA-256
    1aa9acc81672528832af24b1c40e163baee7c39866f453dde76a8aa05e167f40
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 01:03:15
    Evidence reason
    alive_content
  33. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 01:03:15.000000
    Evidence SHA-256
    1aa9acc81672528832af24b1c40e163baee7c39866f453dde76a8aa05e167f40
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 01:03:15
    Evidence reason
    alive_content
  34. 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-10-25 21:55:07.813656
    Evidence SHA-256
    c03dbd2dcd7c6f08fd7189e78b7cd4e699f4a81ddbfb248f4d57c8431243efdd
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 21:55:07.813656
    Evidence reason
  35. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 13:05:26.000000
    Evidence SHA-256
    36a74ae52eb29bc1a5c09bb9742cfad978a2d1bcbd1a88373afb3f23f5e43f55
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 13:05:26
    Evidence reason
    alive_content
  36. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 13:05:26.000000
    Evidence SHA-256
    36a74ae52eb29bc1a5c09bb9742cfad978a2d1bcbd1a88373afb3f23f5e43f55
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 13:05:26
    Evidence reason
    alive_content
  37. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 04:53:53.000000
    Evidence SHA-256
    84c039755f12550ff25d3997fb17ddade69e2470a80328d2156ab97c8bf0d0a4
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 04:53:53
    Evidence reason
    alive_content
  38. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 04:53:53.000000
    Evidence SHA-256
    84c039755f12550ff25d3997fb17ddade69e2470a80328d2156ab97c8bf0d0a4
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 04:53:53
    Evidence reason
    alive_content
  39. 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-10-24 22:55:07.425478
    Evidence SHA-256
    db407a17211d6cfcb77d163e1a7001bdf0972c8f223c354514bcb9984da64451
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-24 22:55:07.425478
    Evidence reason
  40. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 12:56:34.000000
    Evidence SHA-256
    83eca4e566dbff059787027960c9bfd0a6d4b56d7a41df734fddd7475f171c8c
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-24 12:56:34
    Evidence reason
    alive_content
  41. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 12:56:34.000000
    Evidence SHA-256
    83eca4e566dbff059787027960c9bfd0a6d4b56d7a41df734fddd7475f171c8c
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-24 12:56:34
    Evidence reason
    alive_content
  42. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 01:14:32.000000
    Evidence SHA-256
    b624c8770a8847341b0963663cff9f4045eb30621a8fc232680999a01976c6f1
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-24 01:14:32
    Evidence reason
    alive_content
  43. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 01:14:32.000000
    Evidence SHA-256
    b624c8770a8847341b0963663cff9f4045eb30621a8fc232680999a01976c6f1
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-24 01:14:32
    Evidence reason
    alive_content
  44. 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-10-23 22:55:04.214160
    Evidence SHA-256
    a129b1779475e3f54f7d56c6645a7ea341611511053771d19f279461ea93b9a6
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-23 22:55:04.214160
    Evidence reason
  45. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 17:02:32.000000
    Evidence SHA-256
    8e401a5faddb33633d08f0259322133e377de6320fba6abe901986d5529793d9
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-23 17:02:32
    Evidence reason
  46. http_observationunknown
    Observation source
    http_observation
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 17:02:32.000000
    Evidence SHA-256
    8e401a5faddb33633d08f0259322133e377de6320fba6abe901986d5529793d9
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-23 17:02:32
    Evidence reason
  47. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 16:53:57.115680
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

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
    bamkart.shop detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · Forensic Evidence Collected · Technical Analysis Recorded 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: 99
  • 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.
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
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. URLScan

    Page captured

    View source
  2. Wayback Machine

    Page archived

    View source
  3. Added to PhishDestroy

    bamkart.shop

    View source
  4. VirusTotal

    0/92 engine detections

    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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Check for cloaking

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

bamkart.shop

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal ChainPatrol URLQuery Scamadviser 95 trust SSL Labs Stored certificate dates valid CF Radar Open report 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 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.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
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.

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

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 bamkart.shop)
  • 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

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.

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