Skip to security report
This domain has been flagged as malicious
Security engines reporting a detection: 18. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
menschliche-verifikation.firebaseapp.com favicon

menschliche-verifikation.firebaseapp.com

In short

PhishDestroy records that menschliche-verifikation.firebaseapp.com returned a 404 Not Found error page with no interactive content.

Registrar
MarkMonitor
Resolved IP
United States199.36.158.100Fastly, Inc. · CDN
First observed
Oct 31, 2026
PhishDestroy assessment Critical
95/100
Evidence score
Availability Last known active Latest stored reachability observation
VirusTotal detections: 18/92
VirusTotal
engine detections ·
URLScan
engine verdict · score 94
Cloudflare Radar
Page captures
open gallery
Oct 31, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy records that menschliche-verifikation.firebaseapp.com returned a 404 Not Found error page with no interactive content.

Critical
Status
Last known active
VirusTotal
18 / 92
Hosting
United States199.36.158.100Fastly, Inc. · CDN
Registrar
MarkMonitor
Page captures
4

PhishDestroy analysis, reviewed version

The captured page at menschliche-verifikation.firebaseapp.com is a server-generated 404 error, displaying a large "404" heading, the message "Not Found," and the line "The resource requested could not be found on this server!" There is no form, login prompt, or other interaction to complete; the only additional visible text is a LiteSpeed Web Server footer noting that LiteSpeed Technologies Inc. has no control over content found on the site.

The stored VirusTotal domain result reports 18 detections out of 92 engines. DNS8 reported "phishing"; ESET reported "phishing".

Source evidenceVirusTotal 18 / 92 8 sources

VirusTotal

18 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
45
Malicious
18
Suspicious
0
Undetected
29

Vendor labels

DNS8
phishing
ESET
phishing
VIPRE
phishing
G-Data
phishing
Lionic
malicious
Sophos
phishing
CyRadar
phishing
Webroot
malicious
Fortinet
phishing
SOCRadar
phishing
LevelBlue
phishing
Seclookup
malicious
Gridinsoft
phishing
BitDefender
phishing
Criminal IP
phishing
SCUMWARE.org
malware
alphaMountain.ai
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Categories

alphaMountain.ai
Phishing (alphaMountain.ai)

Registrar

MarkMonitor Inc.

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    TXT
    Value
    v=DKIM1; k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDPtW5iwpXVPiH5FzJ7Nrl8USzuY9zqqzjE0D1r04xDN6qwziDnmgcFNNfMewVKN2D1O+2J9N14hRprzByFwfQW76yojh54Xu3uSbQ3JP0A7k8o8GutRF8zbFUA8n0ZH2y0cIEjMliXY4W4LwPA7m4q0ObmvSjhd63O9d8z1XkUBwIDAQAB
  • TTL, seconds
    300
    Type
    A
    Value
    199.36.158.100
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2620:0:890::100
  • TTL, seconds
    300
    Type
    TXT
    Value
    v=spf1 redirect=_spf.google.com

DNS records observed

JARM fingerprint

29d3fd00029d29d00041d41d00041d6b5eefa2404a56c2ced79a0d16afe36c

Certificate

Subject alternative names
  • firebaseapp.com
  • *.firebaseapp.com
Issuer
Google Trust Services / WR4
Serial
6739a2897e2a0d3b0ae167cf7c0ccf9f
SHA-256
044f879fc66c5b0ffe5f059867a14d1245a8f289de612e1dadc662f7cfbf44a6
Subject
firebaseapp.com
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
  • ns-cloud-c1.googledomains.com
  • ns-cloud-c2.googledomains.com
  • ns-cloud-c3.googledomains.com
  • ns-cloud-c4.googledomains.com
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 45,
    "malicious": 18,
    "suspicious": 0,
    "undetected": 29
}
Vendor labels
{
    "DNS8": "phishing",
    "ESET": "phishing",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "malicious",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "LevelBlue": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "phishing",
    "BitDefender": "phishing",
    "Criminal IP": "phishing",
    "SCUMWARE.org": "malware",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
Registrar
MarkMonitor Inc.
Created
2012-10-15T18:12:22Z
Expires
2027-10-15T18:12:22Z
Updated
2026-09-13T10:18:21Z
First seen
2023-12-03T15:34:23Z
DNS records
[
    {
        "ttl": 300,
        "type": "TXT",
        "value": "v=DKIM1; k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDPtW5iwpXVPiH5FzJ7Nrl8USzuY9zqqzjE0D1r04xDN6qwziDnmgcFNNfMewVKN2D1O+2J9N14hRprzByFwfQW76yojh54Xu3uSbQ3JP0A7k8o8GutRF8zbFUA8n0ZH2y0cIEjMliXY4W4LwPA7m4q0ObmvSjhd63O9d8z1XkUBwIDAQAB"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "199.36.158.100"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2620:0:890::100"
    },
    {
        "ttl": 300,
        "type": "TXT",
        "value": "v=spf1 redirect=_spf.google.com"
    }
]
Dns at
2026-10-23T06:41:15Z
Jarm
29d3fd00029d29d00041d41d00041d6b5eefa2404a56c2ced79a0d16afe36c
Certificate
{
    "san": [
        "firebaseapp.com",
        "*.firebaseapp.com"
    ],
    "issuer": "Google Trust Services / WR4",
    "serial": "6739a2897e2a0d3b0ae167cf7c0ccf9f",
    "sha256": "044f879fc66c5b0ffe5f059867a14d1245a8f289de612e1dadc662f7cfbf44a6",
    "subject": "firebaseapp.com",
    "valid_to": "2026-12-22T18:00:28Z",
    "valid_from": "2026-09-23T18:00:29Z"
}
Registration record
{
    "registrar": "MarkMonitor Inc.",
    "registrar_iana_id": "292",
    "registrar_url": "http://www.markmonitor.com",
    "created": "2012-10-15T18:12:22Z",
    "updated": "2026-09-13T10:18:21Z",
    "expires": "2027-10-15T00:00:00Z",
    "status": [
        "clientDeleteProhibited",
        "clientTransferProhibited",
        "clientUpdateProhibited"
    ],
    "nameservers": [
        "ns-cloud-c1.googledomains.com",
        "ns-cloud-c2.googledomains.com",
        "ns-cloud-c3.googledomains.com",
        "ns-cloud-c4.googledomains.com"
    ],
    "dnssec": "unsigned"
}
Separate source record · 18 malicious + 0 suspicious / 92 · 2026-10-23 06:34:04 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:34:04Z
fetched_at
2026-10-31T15:19:05Z
stats
{"timeout":0,"harmless":45,"malicious":18,"suspicious":0,"undetected":29}

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Report ID

6b040233-4f4d-4793-81d0-15b902f58fde

Final URL

https://menschliche-verifikation.firebaseapp.com/

HTTP response

200

Navigation history

  • URL
    https://menschliche-verifikation.firebaseapp.com/
    Status
    200

DOM structure hash

9596aa4cad867e9f475638a9c6ada8b7eb7782b28ba888b954fc585234b303ac

Document hash

5713516664bc3e03281c03c693c5001788a22dc8dd3264a596f14b54ad992e75

Phishing classifier result

  • phishing

Domain risk categories

  • Phishing
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    menschliche-verifikation.firebaseapp.com
    Type
    A
    Value
    199.36.158.100
  • Name
    menschliche-verifikation.firebaseapp.com
    Type
    AAAA
    Value
    2620:0:890::100

DNSSEC valid

No

IP address

127.0.1.1

127.0.1.1 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Verdict

Tags
  • phishing
Malicious
Yes
Categories
  • phishing

Registration record

Registrar
MarkMonitor Inc.
Registered
Updated
Expires
Nameservers
  • ns-cloud-c1.googledomains.com
  • ns-cloud-c2.googledomains.com
  • ns-cloud-c3.googledomains.com
  • ns-cloud-c4.googledomains.com
Original source fields · JSON
Uuid
6b040233-4f4d-4793-81d0-15b902f58fde
Final url
https://menschliche-verifikation.firebaseapp.com/
Status
200
History
[
    {
        "url": "https://menschliche-verifikation.firebaseapp.com/",
        "status": 200
    }
]
DOM structure hash
9596aa4cad867e9f475638a9c6ada8b7eb7782b28ba888b954fc585234b303ac
Document hash
5713516664bc3e03281c03c693c5001788a22dc8dd3264a596f14b54ad992e75
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "menschliche-verifikation.firebaseapp.com",
        "type": "A",
        "value": "199.36.158.100"
    },
    {
        "name": "menschliche-verifikation.firebaseapp.com",
        "type": "AAAA",
        "value": "2620:0:890::100"
    }
]
Dnssec valid
false
Ip
127.0.1.1

127.0.1.1 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
Registration record
{
    "registrar": "MarkMonitor Inc.",
    "created": "2012-10-15T18:12:22Z",
    "updated": "2026-09-13T10:18:21Z",
    "expires": "2027-10-15T18:12:22Z",
    "nameservers": [
        "ns-cloud-c1.googledomains.com",
        "ns-cloud-c2.googledomains.com",
        "ns-cloud-c3.googledomains.com",
        "ns-cloud-c4.googledomains.com"
    ]
}
Separate stored summary: Not recorded · observation date not recorded

This summary differs from the dated scan above. It is retained for provenance and does not override the selected source observation.

verdict
null
categories
[]
observed_at
null
source_path
phishdestroy.technologies.cf_radar
scope
Separate stored summary; an absent observation date is not evidence of a clean scan.

URLScan

Malicious · engine verdict · score 94

SHA-256 5713516664bc3e03281c03c693c5001788a22dc8dd3264a596f14b54ad992e75

Open report
URLScanOriginal source recordObserved: 18 fields

Observed: · Retrieved:

Report ID

019d0f0c-6793-7006-9a8c-a1868794e500

Final URL

https://menschliche-verifikation.firebaseapp.com/

HTTP response

200

IP address

2620:0:890::100

Contacted domains

  • abreai.link

Contacted IP addresses

  • 2620:0:890::100

Autonomous systems (ASN)

  • 54113

Server countries

  • US

Document hash

5713516664bc3e03281c03c693c5001788a22dc8dd3264a596f14b54ad992e75

JavaScript globals

  • h
  • a
  • j
  • m
  • k
  • f
  • c
  • b
  • n

TLS session and certificate

Subject alternative names
  • firebaseapp.com
  • *.firebaseapp.com
Cipher
AES_128_GCM
Issuer
WR4
Subject
firebaseapp.com
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

986

Registered domain age, days

986

Certificate age, days

0

Certificate validity, days

89

Page requests

6

Provider verdicts

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

HTTP headers

Content-type
text/html; charset=utf-8
Strict-transport-security
max-age=31556926; includeSubDomains; preload
Original source fields · JSON
Uuid
019d0f0c-6793-7006-9a8c-a1868794e500
Final url
https://menschliche-verifikation.firebaseapp.com/
Status
200
Ip
2620:0:890::100
Contacted domains
[
    "abreai.link"
]
Contacted IP addresses
[
    "2620:0:890::100"
]
Asns
[
    "54113"
]
Countries
[
    "US"
]
Document hash
5713516664bc3e03281c03c693c5001788a22dc8dd3264a596f14b54ad992e75
Globals
[
    "h",
    "a",
    "j",
    "m",
    "k",
    "f",
    "c",
    "b",
    "n"
]
Tls
{
    "san": [
        "firebaseapp.com",
        "*.firebaseapp.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WR4",
    "subject": "firebaseapp.com",
    "protocol": "TLS 1.3",
    "valid_to": "2026-06-18T16:24:30Z",
    "valid_from": "2026-03-20T16:24:31Z"
}
Domain age days
986
Apex age days
986
Tls age days
0
Tls valid days
89
Requests
6
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 94,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "content-type": "text/html; charset=utf-8",
    "strict-transport-security": "max-age=31556926; includeSubDomains; preload"
}
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
019d0f0c-6793-7006-9a8c-a1868794e500
score
null
malicious
null
result_at
null
enriched_at
null
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":null}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

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

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

Open report
Separate monitor score · 0 / 100 · 2026-10-31T15:38:35Z

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
0
analyzed_at
2026-10-31T15:38:35Z
source_timestamp
2026-10-31 16:38:35
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

ai_title
menschliche-verifikation.firebaseapp.com – 404 Not Found page
ai_description
PhishDestroy records that menschliche-verifikation.firebaseapp.com returned a 404 Not Found error page with no interactive content.
ai_summary
The captured page at menschliche-verifikation.firebaseapp.com is a server-generated 404 error, displaying a large "404" heading, the message "Not Found," and the line "The resource requested could not be found on this server!" There is no form, login prompt, or other interaction to complete; the only additional visible text is a LiteSpeed Web Server footer noting that LiteSpeed Technologies Inc. has no control over content found on the site. The stored VirusTotal domain result reports 18 detections out of 92 engines. DNS8 reported "phishing"; ESET reported "phishing".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-10-31 16:23:55
revision
cfbf1813ccc8ebdcfa3c72c9a76d335deb6d634afd8df5cb1b41839c03b32ea2
mode
reviewed
interpretation
Selected public package; text generation time is separate from source observation dates.

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

Mail configuration

SPF record
v=spf1 redirect=_spf.google.com
DKIM
  • default
  • google
  • selector1
  • selector2
  • k1
  • k2
  • k3
  • s1
DKIM key size, bits
1024
SPF lookups
1

CAA records

Count
1
Domain
firebaseapp.com
Allowed issuers
  • pki.goog

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
1523

Security contact file (security.txt)

Present
Yes
Found at
/.well-known/security.txt

Trackers

Requests
2

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
75
TLS
47
Waiting
45
Connection
17
Download
1
Response time, ms
185

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

Carbon estimate

Bytes
898
CO₂, grams
0
Cleaner than, %
95

DNS servers

Nameservers
  • IP address
    216.239.34.108
    Host
    ns-cloud-c2.googledomains.com
  • IP address
    216.239.36.108
    Host
    ns-cloud-c3.googledomains.com
  • IP address
    216.239.32.108
    Host
    ns-cloud-c1.googledomains.com
  • IP address
    216.239.38.108
    Host
    ns-cloud-c4.googledomains.com
DNS zone
firebaseapp.com

Location

IP address
2620:0:890::100
ASN
54113
Organization
Fastly, Inc.
City
Mountain View
Country
US

TLS certificate

Issuer
Google Trust Services / WR3
Subject
firebaseapp.com

DNS records

A
  • 199.36.158.100
TXT
  • v=DKIM1; k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDPtW5iwpXVPiH5FzJ7Nrl8USzuY9zqqzjE0D1r04xDN6qwziDnmgcFNNfMewVKN2D1O+2J9N14hRprzByFwfQW76yojh54Xu3uSbQ3JP0A7k8o8GutRF8zbFUA8n0ZH2y0cIEjMliXY4W4LwPA7m4q0ObmvSjhd63O9d8z1XkUBwIDAQAB
  • v=spf1 redirect=_spf.google.com
AAAA
  • 2620:0:890::100

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Header value
max-age=31556926; includeSubDomains; preload
Observation
Site is compatible with the HSTS preload list!
Preload compatible
Yes

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
max-age=31556926; includeSubDomains; preload
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
2620:0:890::100
IP version
6

Redirects

Redirect chain
  • https://menschliche-verifikation.firebaseapp.com

HTTP headers

Response headers
Content-type
text/html; charset=utf-8
Strict-transport-security
max-age=31556926; includeSubDomains; preload
Original source fields · JSON
Mail configuration
{
    "spf": "v=spf1 redirect=_spf.google.com",
    "dkim": [
        "default",
        "google",
        "selector1",
        "selector2",
        "k1",
        "k2",
        "k3",
        "s1"
    ],
    "dkim_bits": 1024,
    "spf_lookups": 1
}
Caa records
{
    "count": 1,
    "domain": "firebaseapp.com",
    "issuers": [
        "pki.goog"
    ]
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-31T15:11:48Z",
    "first": "2026-10-31T15:11:48Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 1523
}
Security contact file
{
    "present": true,
    "found_in": "/.well-known/security.txt"
}
Trackers
{
    "requests": 2
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 75,
        "tls": 47,
        "wait": 45,
        "connect": 17,
        "download": 1
    },
    "response_ms": 185
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_128_GCM_SHA256",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Carbon
{
    "bytes": 898,
    "co2_grams": 0,
    "cleaner_than": 95
}
Dns server
{
    "ns": [
        {
            "ip": "216.239.34.108",
            "host": "ns-cloud-c2.googledomains.com"
        },
        {
            "ip": "216.239.36.108",
            "host": "ns-cloud-c3.googledomains.com"
        },
        {
            "ip": "216.239.32.108",
            "host": "ns-cloud-c1.googledomains.com"
        },
        {
            "ip": "216.239.38.108",
            "host": "ns-cloud-c4.googledomains.com"
        }
    ],
    "zone": "firebaseapp.com"
}
Location
{
    "ip": "2620:0:890::100",
    "asn": "54113",
    "org": "Fastly, Inc.",
    "city": "Mountain View",
    "country": "US"
}
Ssl
{
    "issuer": "Google Trust Services / WR3",
    "subject": "firebaseapp.com"
}
DNS records
{
    "A": [
        "199.36.158.100"
    ],
    "TXT": [
        "v=DKIM1; k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDPtW5iwpXVPiH5FzJ7Nrl8USzuY9zqqzjE0D1r04xDN6qwziDnmgcFNNfMewVKN2D1O+2J9N14hRprzByFwfQW76yojh54Xu3uSbQ3JP0A7k8o8GutRF8zbFUA8n0ZH2y0cIEjMliXY4W4LwPA7m4q0ObmvSjhd63O9d8z1XkUBwIDAQAB",
        "v=spf1 redirect=_spf.google.com"
    ],
    "AAAA": [
        "2620:0:890::100"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=31556926; includeSubDomains; preload",
    "message": "Site is compatible with the HSTS preload list!",
    "compatible": true
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": "max-age=31556926; includeSubDomains; preload",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "2620:0:890::100",
    "family": 6
}
Redirects
{
    "chain": [
        "https://menschliche-verifikation.firebaseapp.com"
    ]
}
HTTP headers
{
    "headers": {
        "content-type": "text/html; charset=utf-8",
        "strict-transport-security": "max-age=31556926; includeSubDomains; preload"
    }
}

Questions about menschliche-verifikation.firebaseapp.com

Is menschliche-verifikation.firebaseapp.com legit?

PhishDestroy records that menschliche-verifikation.firebaseapp.com returned a 404 Not Found error page with no interactive content.

Is menschliche-verifikation.firebaseapp.com safe to connect a wallet?

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

What should I do if I used menschliche-verifikation.firebaseapp.com?

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

Explore

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

Last checked

Stored Capture · 4 captures

All capture links and hashes (4)

Domain details

Domain
IP Context United States199.36.158.100 Fastly shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider MarkMonitor
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 31, 2026
DOM Analysisanalyzed Oct 31, 2026score 0/100
Submitted URLhttp://menschliche-verifikation.firebaseapp.com/
TLS Certificate
Issued by Google Trust Services / WR4 · stored validity ends in 52 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
United States199.36.158.100
Network ASN
AS54113
Organization
Fastly, Inc.
Observed location
United StatesMountain View, US

Edge-IP reputation is not attributed to this domain.

Nameservers 4

  • ns-cloud-c1.googledomains.com
  • ns-cloud-c2.googledomains.com
  • ns-cloud-c3.googledomains.com
  • ns-cloud-c4.googledomains.com

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WR4
Valid from
2026-09-23 18:00:29
Valid until
2026-12-22 18:00:28
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint044f879fc66c5b0ffe5f059867a14d1245a8f289de612e1dadc662f7cfbf44a6
Certificate names · 2 SANs
  • firebaseapp.com
  • *.firebaseapp.com

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

Report This Domain Submit evidence & help protect others

VirusTotal Analysis

18 / 92 security vendors flagged this domain
View on VT
Last analyzed
Criminal IP
alphaMountain.ai
BitDefender
CyRadar
DNS8
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
LevelBlue
Lionic
SCUMWARE.org
Seclookup
SOCRadar
Sophos
VIPRE
Webroot

Archived Evidence

Wayback Machine Snapshot
View Archive
Stored Capture Evidence 1 snapshot

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

Archived HTTP response HTTP 200
Requested URL: http://menschliche-verifikation.firebaseapp.com/
Final URL: https://menschliche-verifikation.firebaseapp.com/
Response
HTTP 200
HTML body
898 B
Compressed
626 B
Links
0 internal · 0 external
Selected response headers
Cache-Control: max-age=3600
Content-Encoding: gzip
Content-Type: text/html; charset=utf-8
Security headers present
Strict-Transport-Security
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 16
Accept-Ranges
bytes
alt-svc
h3=":443";ma=86400,h3-29=":443";ma=86400,h3-27=":443";ma=86400
Cache-Control
max-age=3600
Connection
keep-alive
Content-Encoding
gzip
Content-Length
626
Content-Type
text/html; charset=utf-8
Date
Sat, 31 Oct 2026 15:15:06 GMT
Etag
"cd9574134d54bbf031b79cccaab10eaa79318e17d8535319b840ec155b563032"
Last-Modified
Sun, 07 Jan 2024 22:06:07 GMT
Strict-Transport-Security
max-age=31556926; includeSubDomains; preload
Vary
x-fh-requested-host, accept-encoding
X-Cache
HIT
X-Cache-Hits
0
X-Served-By
cache-iad-kiad7000142-IAD
X-Timer
S1793459707.735139,VS0,VE2

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

Captured network requests

Network requests: 6 SHA-256 hashes: 5 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-31 15:22 UTC.

Open this scan on URLScan 019d0f0c-6793-7006-9a8c-a1868794e500 ↗

All retained availability observations1

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_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-31 16:23:15.282508
    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: 9. 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
    menschliche-verifikation.firebaseapp.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 7 of 7
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 94
  • 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
  • VirusTotal
    Detections recorded on VirusTotal: 18/92
  • 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

5 entries
  1. Cloudflare Radar

    Phishing

    View source
  2. Wayback Machine

    Page archived

    View source
  3. Added to PhishDestroy

    menschliche-verifikation.firebaseapp.com

    View source
  4. VirusTotal

    18/92 engine detections

    View source
  5. URLScan

    Malicious · engine verdict · score 94

    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.

Check for cloaking

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

menschliche-verifikation.firebaseapp.com

Evidence & External Reports

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.

Official reporting routes

More official reporting routes
FTC ReportFraud United States

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

IdentityTheft.gov United States

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

CISA United States

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

CSIRTs Network European Union

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

FIRST Worldwide

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

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

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

Report to Your Local Authorities

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

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

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

97-country directory

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

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

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

What should I do immediately?

Urgent

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

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

What information should I collect for my report?

FBI guidelines

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

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

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

Where should I report the scam?

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

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

How do phishing scams typically work?

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

How can I protect myself in the future?

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

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

Stay Informed, Stay Safe

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

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

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/menschliche-verifikation.firebaseapp.com"
  title="PhishDestroy threat report for menschliche-verifikation.firebaseapp.com"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>