Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 2. Public blocklists reporting a match: 1. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
lb-bayern-sys.github.io favicon

lb-bayern-sys.github.io

In short

PhishDestroy stores a record for lb-bayern-sys.github.io. Source observations are dated separately; missing checks do not establish safety.

“BayernLB - Online-Banking Portal”

Review the evidence
Registrar
GitHub
Resolved IP
United States185.199.108.153GitHub, Inc · CDN
First observed
Oct 23, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Content unavailable Content was unavailable in the latest observation Observed HTTP probe
Risk signals
VirusTotal detections: 2/92 Stored blocklist matches: 1 Google Safe Browsing: threat flag recorded
VirusTotal
2 / 92
engine detections ·
Google Safe Browsing
Flagged
Blocklist matches
1
PhishFeed
URLQuery
3
detections
URLScan
Malicious
engine verdict · score 98
Page captures
9
open gallery
Oct 23, 2026 CDN
X Telegram API

Questions about lb-bayern-sys.github.io

Is lb-bayern-sys.github.io legit?

PhishDestroy stores a record for lb-bayern-sys.github.io. Source observations are dated separately; missing checks do not establish safety.

Is lb-bayern-sys.github.io safe to connect a wallet?

This report does not record which wallet requests lb-bayern-sys.github.io 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 lb-bayern-sys.github.io?

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

Source evidenceVirusTotal 2 / 92 · Google Safe Browsing: flagged 7 sources

VirusTotal

2 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
56
Malicious
1
Suspicious
1
Undetected
34

Vendor labels

DNS8
suspicious
SafeToOpen
phishing

Reputation score

0

Registrar

MarkMonitor Inc.

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    3600
    Type
    AAAA
    Value
    2606:50c0:8000::153
  • TTL, seconds
    3600
    Type
    AAAA
    Value
    2606:50c0:8002::153
  • TTL, seconds
    3600
    Type
    CAA
    Value
    sectigo.com
  • TTL, seconds
    3600
    Type
    AAAA
    Value
    2606:50c0:8001::153
  • TTL, seconds
    3600
    Type
    CAA
    Value
    letsencrypt.org
  • TTL, seconds
    3600
    Type
    CAA
    Value
    letsencrypt.org
  • TTL, seconds
    3600
    Type
    CAA
    Value
    sectigo.com
  • TTL, seconds
    3600
    Type
    AAAA
    Value
    2606:50c0:8003::153
  • TTL, seconds
    3600
    Type
    CAA
    Value
    digicert.com
  • TTL, seconds
    3600
    Type
    CAA
    Value
    digicert.com
  • TTL, seconds
    3600
    Type
    A
    Value
    185.199.110.153
  • TTL, seconds
    3600
    Type
    A
    Value
    185.199.111.153
  • TTL, seconds
    3600
    Type
    A
    Value
    185.199.109.153
  • TTL, seconds
    3600
    Type
    A
    Value
    185.199.108.153

DNS records observed

JARM fingerprint

29d3fd00029d29d00041d41d00041d6b5eefa2404a56c2ced79a0d16afe36c

Certificate

Subject alternative names
  • *.github.com
  • *.github.io
  • *.githubusercontent.com
  • github.com
  • github.io
  • githubusercontent.com
Issuer
Let's Encrypt / YR1
Serial
59e7c420f8943f524ab370807c836bb57fe
SHA-256
71f1077db377fd7b8d68380da66fa68238a303b2911bcb770b3b2a426693cf84
Subject
*.github.io
Valid until
Valid from

Registration record

Registrar
MarkMonitor Inc.
Registrar IANA ID
292
Registrar URL
http://www.markmonitor.com
Registered
Updated
Expires
Status
  • clientDeleteProhibited
  • clientTransferProhibited
  • clientUpdateProhibited
Nameservers
  • dns1.p05.nsone.net
  • dns2.p05.nsone.net
  • dns3.p05.nsone.net
  • ns-1622.awsdns-10.co.uk
  • ns-692.awsdns-22.net
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 56,
    "malicious": 1,
    "suspicious": 1,
    "undetected": 34
}
Vendor labels
{
    "DNS8": "suspicious",
    "SafeToOpen": "phishing"
}
Reputation
0
Registrar
MarkMonitor Inc.
Created
2013-03-08T19:41:10Z
Expires
2027-03-08T19:12:48Z
Updated
2026-08-12T09:08:04Z
First seen
2026-10-08T15:30:40Z
DNS records
[
    {
        "ttl": 3600,
        "type": "AAAA",
        "value": "2606:50c0:8000::153"
    },
    {
        "ttl": 3600,
        "type": "AAAA",
        "value": "2606:50c0:8002::153"
    },
    {
        "ttl": 3600,
        "type": "CAA",
        "value": "sectigo.com"
    },
    {
        "ttl": 3600,
        "type": "AAAA",
        "value": "2606:50c0:8001::153"
    },
    {
        "ttl": 3600,
        "type": "CAA",
        "value": "letsencrypt.org"
    },
    {
        "ttl": 3600,
        "type": "CAA",
        "value": "letsencrypt.org"
    },
    {
        "ttl": 3600,
        "type": "CAA",
        "value": "sectigo.com"
    },
    {
        "ttl": 3600,
        "type": "AAAA",
        "value": "2606:50c0:8003::153"
    },
    {
        "ttl": 3600,
        "type": "CAA",
        "value": "digicert.com"
    },
    {
        "ttl": 3600,
        "type": "CAA",
        "value": "digicert.com"
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "185.199.110.153"
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "185.199.111.153"
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "185.199.109.153"
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "185.199.108.153"
    }
]
Dns at
2026-10-11T16:23:48Z
Jarm
29d3fd00029d29d00041d41d00041d6b5eefa2404a56c2ced79a0d16afe36c
Certificate
{
    "san": [
        "*.github.com",
        "*.github.io",
        "*.githubusercontent.com",
        "github.com",
        "github.io",
        "githubusercontent.com"
    ],
    "issuer": "Let's Encrypt / YR1",
    "serial": "59e7c420f8943f524ab370807c836bb57fe",
    "sha256": "71f1077db377fd7b8d68380da66fa68238a303b2911bcb770b3b2a426693cf84",
    "subject": "*.github.io",
    "valid_to": "2026-10-31T23:38:01Z",
    "valid_from": "2026-08-02T23:38:02Z"
}
Registration record
{
    "registrar": "MarkMonitor Inc.",
    "registrar_iana_id": "292",
    "registrar_url": "http://www.markmonitor.com",
    "created": "2013-03-08T19:12:48Z",
    "updated": "2025-02-25T20:53:31Z",
    "expires": "2027-03-08T00:00:00Z",
    "status": [
        "clientDeleteProhibited",
        "clientTransferProhibited",
        "clientUpdateProhibited"
    ],
    "nameservers": [
        "dns1.p05.nsone.net",
        "dns2.p05.nsone.net",
        "dns3.p05.nsone.net",
        "ns-1622.awsdns-10.co.uk",
        "ns-692.awsdns-22.net"
    ],
    "dnssec": "unsigned"
}
Separate source record · 1 malicious + 1 suspicious / 92 · 2026-10-11 16:18:33 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-11T16:18:33Z
fetched_at
2026-10-23T00:55:00Z
stats
{"timeout":0,"harmless":56,"malicious":1,"suspicious":1,"undetected":34}

Google Safe Browsing

Threat flag recorded

Open report

URLScan

Malicious · engine verdict · score 98

SHA-256 2fd8814f9254e847de33a2f634e22784a7f329c65c78081930c84d3f996c11e1

Open report
URLScanOriginal source recordObserved: 21 fields

Observed: · Retrieved:

Report ID

01a16623-15bd-752a-820e-e7be964e7fd1

Final URL

https://lb-bayern-sys.github.io/9842351/

HTTP response

200

Redirect type

same-domain

Redirects

  • To
    https://lb-bayern-sys.github.io/9842351
    From
    http://lb-bayern-sys.github.io/9842351
    Status
    307
  • To
    http://lb-bayern-sys.github.io/9842351
    From
    https://lb-bayern-sys.github.io/9842351
    Status
    307
  • To
    https://lb-bayern-sys.github.io/9842351
    From
    http://lb-bayern-sys.github.io/9842351
    Status
    301
  • To
    https://lb-bayern-sys.github.io/9842351/
    From
    https://lb-bayern-sys.github.io/9842351
    Status
    301

IP address

185.199.110.153

Reverse DNS (PTR)

cdn-185-199-110-153.github.com

Contacted domains

  • images.unsplash.com

Contacted IP addresses

  • 151.101.66.208
  • 185.199.110.153

Autonomous systems (ASN)

  • 54113

Server countries

  • US

Document hash

0518c76264423f30e5871b31e48ef6fd541629dd75647eb7d309f0e9b101f167

JavaScript globals

  • setLanguage
  • showSection
  • attemptLogin
  • navigateTo
  • triggerVirementError
  • langData

TLS session and certificate

Subject alternative names
  • *.github.com
  • *.github.io
  • *.githubusercontent.com
  • github.com
  • github.io
  • githubusercontent.com
Cipher
AES_128_GCM
Issuer
YR1
Subject
*.github.io
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

108

Registered domain age, days

108

Certificate age, days

22

Certificate validity, days

89

Page requests

3

Provider verdicts

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

HTTP headers

Server
GitHub.com
Content-type
text/html; charset=utf-8
Strict-transport-security
max-age=31556952
Original source fields · JSON
Uuid
01a16623-15bd-752a-820e-e7be964e7fd1
Final url
https://lb-bayern-sys.github.io/9842351/
Status
200
Redirected
same-domain
Redirects
[
    {
        "to": "https://lb-bayern-sys.github.io/9842351",
        "from": "http://lb-bayern-sys.github.io/9842351",
        "status": 307
    },
    {
        "to": "http://lb-bayern-sys.github.io/9842351",
        "from": "https://lb-bayern-sys.github.io/9842351",
        "status": 307
    },
    {
        "to": "https://lb-bayern-sys.github.io/9842351",
        "from": "http://lb-bayern-sys.github.io/9842351",
        "status": 301
    },
    {
        "to": "https://lb-bayern-sys.github.io/9842351/",
        "from": "https://lb-bayern-sys.github.io/9842351",
        "status": 301
    }
]
Ip
185.199.110.153
Ptr
cdn-185-199-110-153.github.com
Contacted domains
[
    "images.unsplash.com"
]
Contacted IP addresses
[
    "151.101.66.208",
    "185.199.110.153"
]
Asns
[
    "54113"
]
Countries
[
    "US"
]
Document hash
0518c76264423f30e5871b31e48ef6fd541629dd75647eb7d309f0e9b101f167
Globals
[
    "setLanguage",
    "showSection",
    "attemptLogin",
    "navigateTo",
    "triggerVirementError",
    "langData"
]
Tls
{
    "san": [
        "*.github.com",
        "*.github.io",
        "*.githubusercontent.com",
        "github.com",
        "github.io",
        "githubusercontent.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YR1",
    "subject": "*.github.io",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-29T23:44:45Z",
    "valid_from": "2026-09-30T23:44:46Z"
}
Domain age days
108
Apex age days
108
Tls age days
22
Tls valid days
89
Requests
3
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 98,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "GitHub.com",
    "content-type": "text/html; charset=utf-8",
    "strict-transport-security": "max-age=31556952"
}
Separate monitor record · 2026-10-23 03:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a16623-15bd-752a-820e-e7be964e7fd1
score
0
malicious
false
result_at
2026-10-23T03:30:22Z
enriched_at
2026-10-23T08:16:08Z
source_timestamps
{"urlscan_result_at":"2026-10-23 05:30:22","urlscan_enriched_at":"2026-10-23 10:16:08"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

no community references

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

10 / 100 · heuristic score · 1 brand reference · 1 classification

Open report
Separate monitor score · 10 / 100 · 2026-10-23T02:20:34Z

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

record_source
domain_monitor.dom_analysis
heuristic_score
10
analyzed_at
2026-10-23T02:20:34Z
source_timestamp
2026-10-23 04:20:34
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

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

Mail configuration

SPF lookups
0

CAA records

Count
6
Domain
lb-bayern-sys.github.io
Allowed issuers
  • digicert.com
  • letsencrypt.org
  • sectigo.com

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

Last observation
First observation
Recorded changes
0
Archived days
1
Average page size, bytes
5010

TLS connection

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

Ports

Open ports
  • 80
  • 443

DNS servers

Nameservers
  • IP address
    205.251.198.86
    Host
    ns-1622.awsdns-10.co.uk
  • IP address
    198.51.44.5
    Host
    dns1.p05.nsone.net
  • IP address
    198.51.45.5
    Host
    dns2.p05.nsone.net
  • IP address
    198.51.44.69
    Host
    dns3.p05.nsone.net
  • IP address
    198.51.45.69
    Host
    dns4.p05.nsone.net
  • IP address
    205.251.193.137
    Host
    ns-393.awsdns-49.com
  • IP address
    205.251.197.59
    Host
    ns-1339.awsdns-39.org
  • IP address
    205.251.194.180
    Host
    ns-692.awsdns-22.net
DNS zone
github.io

Location

IP address
2606:50c0:8003::153
ASN
54113
Organization
Fastly, Inc.
City
San Francisco
Country
US

TLS certificate

Issuer
Let's Encrypt / YR1
Subject
*.github.io

DNS records

A
  • 185.199.108.153
  • 185.199.111.153
  • 185.199.110.153
  • 185.199.109.153
AAAA
  • 2606:50c0:8000::153
  • 2606:50c0:8003::153
  • 2606:50c0:8002::153
  • 2606:50c0:8001::153

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
default-src 'none'; style-src 'unsafe-inline'; img-src data:; connect-src 'self'
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
2606:50c0:8000::153
IP version
6

HTTP headers

Response headers
Server
GitHub.com
Content-type
text/html; charset=utf-8
Content-security-policy
default-src 'none'; style-src 'unsafe-inline'; img-src data:; connect-src 'self'
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "count": 6,
    "domain": "lb-bayern-sys.github.io",
    "issuers": [
        "digicert.com",
        "letsencrypt.org",
        "sectigo.com"
    ]
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-09T21:12:33Z",
    "first": "2026-10-09T21:12:33Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 5010
}
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
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "205.251.198.86",
            "host": "ns-1622.awsdns-10.co.uk"
        },
        {
            "ip": "198.51.44.5",
            "host": "dns1.p05.nsone.net"
        },
        {
            "ip": "198.51.45.5",
            "host": "dns2.p05.nsone.net"
        },
        {
            "ip": "198.51.44.69",
            "host": "dns3.p05.nsone.net"
        },
        {
            "ip": "198.51.45.69",
            "host": "dns4.p05.nsone.net"
        },
        {
            "ip": "205.251.193.137",
            "host": "ns-393.awsdns-49.com"
        },
        {
            "ip": "205.251.197.59",
            "host": "ns-1339.awsdns-39.org"
        },
        {
            "ip": "205.251.194.180",
            "host": "ns-692.awsdns-22.net"
        }
    ],
    "zone": "github.io"
}
Location
{
    "ip": "2606:50c0:8003::153",
    "asn": "54113",
    "org": "Fastly, Inc.",
    "city": "San Francisco",
    "country": "US"
}
Ssl
{
    "issuer": "Let's Encrypt / YR1",
    "subject": "*.github.io"
}
DNS records
{
    "A": [
        "185.199.108.153",
        "185.199.111.153",
        "185.199.110.153",
        "185.199.109.153"
    ],
    "AAAA": [
        "2606:50c0:8000::153",
        "2606:50c0:8003::153",
        "2606:50c0:8002::153",
        "2606:50c0:8001::153"
    ]
}
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": "default-src 'none'; style-src 'unsafe-inline'; img-src data:; connect-src 'self'",
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "2606:50c0:8000::153",
    "family": 6
}
HTTP headers
{
    "headers": {
        "server": "GitHub.com",
        "content-type": "text/html; charset=utf-8",
        "content-security-policy": "default-src 'none'; style-src 'unsafe-inline'; img-src data:; connect-src 'self'"
    }
}
Blocklist matchesPhishDestroy · PhishFeed · no match in the other 10 2
PhishDestroy PhishDestroy list View source
PhishFeed Listed View source

Checked, no match

Last checked

Stored Capture · 9 captures

Primary capture 1 / 9
SourcePrimary capture
Recorded
StateStored capture
Position1 / 9
Open capture Wayback Download
All capture links and hashes (9)
lb-bayern-sys.github.io: Phishing site — Flagged by Google Safe Browsing, 10/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical).
Social preview card lb-bayern-sys.github.io: Phishing site — Flagged by Google Safe Browsing, 10/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical). v fb08036d44b9

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 98 report ↗
Google Safe Browsing Flagged Social engineering checked Oct 30, 2026
IP Context United States185.199.108.153 Fastly shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider GitHub
Abuse contactabuse@github.com
HTTP Status404 Not Found
Technical detailsProvenance & timestamps
First DetectedOct 23, 2026
DOM Analysisanalyzed Oct 23, 2026score 10/1001 brand signal
Submitted URLhttp://lb-bayern-sys.github.io/9842351
Favicon Hash
Observed page title
BayernLB - Online-Banking Portal
Automated brand references
Barclays
TLS Certificate
Issued by YR1 · stored validity ends in 59 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
United States185.199.108.153
Network ASN
AS54113
AS name
FASTLY - Fastly, Inc., US
Organization
GitHub, Inc
Observed location
United StatesSan Francisco, US
Server header
GitHub.com

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

TLS certificate

Issuer
YR1
Valid from
2026-09-30 23:44:46
Valid until
2026-12-29 23:44:45
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint71f1077db377fd7b8d68380da66fa68238a303b2911bcb770b3b2a426693cf84
Certificate names · 6 SANs
  • *.github.com
  • *.github.io
  • *.githubusercontent.com
  • github.com
  • github.io
  • githubusercontent.com

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

viewdns.info · 185.199.108.153rapiddns.io

Latest Classified Outcome 2026-10-31 02:34:14 UTC

No phishing content was served at the latest check.

Technical details
Primary outcome Inactive reason: Http No Content 70% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Root path has no content Content: Absent At Root DNS: Stale Registration: Unknown
Latest HTTP observation Inactive Http No Content 70% 2026-10-31 02:34:14 UTC
RDAP registration
Observed timeline last reachable: 2026-10-23 00:23:08 UTC current episode first observed: 2026-10-23 10:00:52 UTC observed RIP window: 2026-10-23 00:23:08 UTC → 2026-10-23 10:00:52 UTC · 9.63h midpoint estimate ≈ 2026-10-23 05:12:00 UTC · precision medium · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

2 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
alphaMountain.ai
BitDefender
ESET
Forcepoint ThreatSeeker
G-Data
Lionic
MalwareURL
SafeToOpen
SOCRadar
URLQuery
Registration & observation details8

Availability observations

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

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

Captured network requests

Network requests: 3 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 02:01 UTC.

Open this scan on URLScan 01a16623-15bd-752a-820e-e7be964e7fd1 ↗

Check for cloaking

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

Page titles differ

Our scanner could not complete this check.

Browser
BayernLB - Online-Banking Portal
Crawler
Site not found · GitHub Pages
lb-bayern-sys.github.io
Stored observation history3

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

    inactive

    http_no_content

  2. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

  3. Domain monitor · First collection record

    Reachable

All retained availability observations32

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_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 03:34:14.000000
    Evidence SHA-256
    4591a42031875e0df54cafcef5a30869e3ebfedebecd2d8aa147f59209724216
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-31 03:34:14
    Evidence reason
    http_other
  2. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 03:34:14.000000
    Evidence SHA-256
    4591a42031875e0df54cafcef5a30869e3ebfedebecd2d8aa147f59209724216
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-31 03:34:14
    Evidence reason
    http_other
  3. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:10:54.000000
    Evidence SHA-256
    b18f5123baf9ba7886cb006417359da892ec7478b7b4ada60199b3ce89916750
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-30 12:10:54
    Evidence reason
    http_other
  4. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:10:54.000000
    Evidence SHA-256
    b18f5123baf9ba7886cb006417359da892ec7478b7b4ada60199b3ce89916750
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-30 12:10:54
    Evidence reason
    http_other
  5. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:10:59.000000
    Evidence SHA-256
    ab9de0170dbb2140905a6d8981fe821350ea651a738366d1ae770c1f6b9c2cbd
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-30 00:10:59
    Evidence reason
    http_other
  6. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:10:59.000000
    Evidence SHA-256
    ab9de0170dbb2140905a6d8981fe821350ea651a738366d1ae770c1f6b9c2cbd
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-30 00:10:59
    Evidence reason
    http_other
  7. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 12:11:25.000000
    Evidence SHA-256
    83e9b85962ed1b75356faba4a7c26524f33de2a8a990e37fb5d490acaca5fcde
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-29 12:11:25
    Evidence reason
    http_other
  8. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 12:11:25.000000
    Evidence SHA-256
    83e9b85962ed1b75356faba4a7c26524f33de2a8a990e37fb5d490acaca5fcde
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-29 12:11:25
    Evidence reason
    http_other
  9. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 03:40:08.000000
    Evidence SHA-256
    f304ed54b5559ba2cdfbc691c6e576b1b0f9ac4e0d2d2636acc443f48da03fa0
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-29 03:40:08
    Evidence reason
    http_other
  10. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 03:40:08.000000
    Evidence SHA-256
    f304ed54b5559ba2cdfbc691c6e576b1b0f9ac4e0d2d2636acc443f48da03fa0
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-29 03:40:08
    Evidence reason
    http_other
  11. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 12:06:32.000000
    Evidence SHA-256
    6dc9bfedc7ab00b2d0af4ec2f3cd9a88ef206aea2b707998dd4a163642ef55a0
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-28 12:06:32
    Evidence reason
    http_other
  12. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 12:06:32.000000
    Evidence SHA-256
    6dc9bfedc7ab00b2d0af4ec2f3cd9a88ef206aea2b707998dd4a163642ef55a0
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-28 12:06:32
    Evidence reason
    http_other
  13. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 00:07:00.000000
    Evidence SHA-256
    31fcfef22793527194d91ce70d84bd64ab3c2603e9cc106f2deae37a4e072e18
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-28 00:07:00
    Evidence reason
    http_other
  14. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 00:07:00.000000
    Evidence SHA-256
    31fcfef22793527194d91ce70d84bd64ab3c2603e9cc106f2deae37a4e072e18
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-28 00:07:00
    Evidence reason
    http_other
  15. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:06:44.000000
    Evidence SHA-256
    0b934b45970597f5da9468bb550c14ceeefe2688fe84db6bb98c107801e2c162
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-27 12:06:44
    Evidence reason
    http_other
  16. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:06:44.000000
    Evidence SHA-256
    0b934b45970597f5da9468bb550c14ceeefe2688fe84db6bb98c107801e2c162
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-27 12:06:44
    Evidence reason
    http_other
  17. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 12:01:47.000000
    Evidence SHA-256
    0cf9b3ab016bedf17ba44818a0e1cc6334984420fed337198520932bfbe8cec5
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-26 12:01:47
    Evidence reason
    http_other
  18. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 12:01:47.000000
    Evidence SHA-256
    0cf9b3ab016bedf17ba44818a0e1cc6334984420fed337198520932bfbe8cec5
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-26 12:01:47
    Evidence reason
    http_other
  19. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 00:02:05.000000
    Evidence SHA-256
    c3bba3ff38c9622d73f0412dc71f1bd9d7578982799b740db1e6486d19b09900
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-26 00:02:05
    Evidence reason
    http_other
  20. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 00:02:05.000000
    Evidence SHA-256
    c3bba3ff38c9622d73f0412dc71f1bd9d7578982799b740db1e6486d19b09900
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-26 00:02:05
    Evidence reason
    http_other
  21. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 12:02:21.000000
    Evidence SHA-256
    c3cc1fa56ec85573c31e9a5d4724ba120e21e67795d595650b41bad130feb109
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-25 12:02:21
    Evidence reason
    http_other
  22. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 12:02:21.000000
    Evidence SHA-256
    c3cc1fa56ec85573c31e9a5d4724ba120e21e67795d595650b41bad130feb109
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-25 12:02:21
    Evidence reason
    http_other
  23. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 03:54:52.000000
    Evidence SHA-256
    ce78201d0102f3325b19eb03ac171907482ae0324e1d8d85e7aafce8563faabd
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-25 03:54:52
    Evidence reason
    http_other
  24. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 03:54:52.000000
    Evidence SHA-256
    ce78201d0102f3325b19eb03ac171907482ae0324e1d8d85e7aafce8563faabd
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-25 03:54:52
    Evidence reason
    http_other
  25. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 12:00:53.000000
    Evidence SHA-256
    32f11dd8984f773cbdb2dacdcb761992701322bb82683945c1b442b2beedf1b8
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-24 12:00:53
    Evidence reason
    http_other
  26. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 12:00:53.000000
    Evidence SHA-256
    32f11dd8984f773cbdb2dacdcb761992701322bb82683945c1b442b2beedf1b8
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-24 12:00:53
    Evidence reason
    http_other
  27. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 00:01:02.000000
    Evidence SHA-256
    dbea1134a2d795d68b6d4e10c0bb557c042fe08c1ae14cefa825e8592da70ba7
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-24 00:01:02
    Evidence reason
    http_other
  28. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 00:01:02.000000
    Evidence SHA-256
    dbea1134a2d795d68b6d4e10c0bb557c042fe08c1ae14cefa825e8592da70ba7
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-24 00:01:02
    Evidence reason
    http_other
  29. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 12:00:52.000000
    Evidence SHA-256
    1cd7504192c90626e6530c9b5f276e03544f24f9adca399f6705ee4323c27923
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-23 12:00:52
    Evidence reason
    http_other
  30. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 12:00:52.000000
    Evidence SHA-256
    1cd7504192c90626e6530c9b5f276e03544f24f9adca399f6705ee4323c27923
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-23 12:00:52
    Evidence reason
    http_other
  31. 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-10-23 02:23:08.000000
    Evidence SHA-256
    39893f7f1ae7f60691494b2e5a6a5b143a476da53d95113a3d33b7d787458755
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-23 02:23:08
    Evidence reason
  32. 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-10-23 02:23:08.000000
    Evidence SHA-256
    39893f7f1ae7f60691494b2e5a6a5b143a476da53d95113a3d33b7d787458755
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-23 02:23:08
    Evidence reason

Threat Response Pipeline

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

Recorded events: 11. 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
    lb-bayern-sys.github.io detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · VirusTotal · Google Safe Browsing · Blocklist Detection · Automated brand label: Barclays · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 8 of 8
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 98
  • VirusTotal
    Detections recorded on VirusTotal: 2/92
  • Google Safe Browsing
    Listed as unsafe by Google Safe Browsing (Google Transparency Report)
  • Blocklist Detection
    Found in blocklists: PhishFeed
  • Automated brand label: Barclays
    Collector label, not confirmed by a page check.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, URLQuery, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published · Content Observed Unavailable Recorded: 2 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Content Observed Unavailable
    The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.

Recorded activity

4 entries
  1. Google Safe Browsing

    Threat flag recorded

    View source
  2. Added to PhishDestroy

    lb-bayern-sys.github.io

    View source
  3. URLScan

    Page captured

    View source
  4. VirusTotal

    2/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

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 2 det. ChainPatrol URLQuery 3 det. Google SB Flagged SSL Labs Stored certificate dates valid WOT ScamAdviser 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?

4 evidence signal groups linked Content unavailable
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 lb-bayern-sys.github.io)
  • 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/lb-bayern-sys.github.io"
  title="PhishDestroy threat report for lb-bayern-sys.github.io"
  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>