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

customer-p.firebaseapp.com

In short

PhishDestroy stores a record for customer-p.firebaseapp.com. Source observations are dated separately; missing checks do not establish safety.

“Background”

Review the evidence
Registrar
United StatesGoogle Domains
Resolved IP
United States199.36.158.100Fastly, Inc. · CDN
First observed
Oct 25, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 12/92
VirusTotal
12 / 92
engine detections ·
URLQuery
4
detections
URLScan
Malicious
engine verdict · score 93
Page captures
7
open gallery
Oct 25, 2026 CDN
X Telegram API

Questions about customer-p.firebaseapp.com

Is customer-p.firebaseapp.com legit?

PhishDestroy stores a record for customer-p.firebaseapp.com. Source observations are dated separately; missing checks do not establish safety.

Is customer-p.firebaseapp.com safe to connect a wallet?

This report does not record which wallet requests customer-p.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 customer-p.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

Source evidenceVirusTotal 12 / 92 7 sources

VirusTotal

12 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
47
Malicious
12
Suspicious
0
Undetected
33

Vendor labels

ESET
phishing
G-Data
phishing
Lionic
phishing
Sophos
phishing
CyRadar
phishing
Webroot
malicious
Seclookup
malicious
Gridinsoft
phishing
BitDefender
phishing
Chong Lua Dao
malicious
alphaMountain.ai
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Categories

Sophos
phishing and fraud
Webroot
Phishing and Other Frauds
PREBYTES
phishing
alphaMountain.ai
Phishing (alphaMountain.ai)
Forcepoint ThreatSeeker
phishing and other frauds

Registrar

MarkMonitor Inc.

Created

Expires

Updated

First seen

DNS records

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

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": 47,
    "malicious": 12,
    "suspicious": 0,
    "undetected": 33
}
Vendor labels
{
    "ESET": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Seclookup": "malicious",
    "Gridinsoft": "phishing",
    "BitDefender": "phishing",
    "Chong Lua Dao": "malicious",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Categories
{
    "Sophos": "phishing and fraud",
    "Webroot": "Phishing and Other Frauds",
    "PREBYTES": "phishing",
    "alphaMountain.ai": "Phishing (alphaMountain.ai)",
    "Forcepoint ThreatSeeker": "phishing and other frauds"
}
Registrar
MarkMonitor Inc.
Created
2012-10-15T18:12:22Z
Expires
2027-10-15T18:12:22Z
Updated
2026-09-13T10:18:21Z
First seen
2023-09-28T19:45:03Z
DNS records
[
    {
        "ttl": 300,
        "type": "TXT",
        "value": "v=spf1 redirect=_spf.google.com"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2620:0:890::100"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "199.36.158.100"
    },
    {
        "ttl": 300,
        "type": "TXT",
        "value": "v=DKIM1; k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDPtW5iwpXVPiH5FzJ7Nrl8USzuY9zqqzjE0D1r04xDN6qwziDnmgcFNNfMewVKN2D1O+2J9N14hRprzByFwfQW76yojh54Xu3uSbQ3JP0A7k8o8GutRF8zbFUA8n0ZH2y0cIEjMliXY4W4LwPA7m4q0ObmvSjhd63O9d8z1XkUBwIDAQAB"
    }
]
Dns at
2026-10-20T23:31:14Z
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 · 12 malicious + 0 suspicious / 92 · 2026-10-20 23:31:03 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-20T23:31:03Z
fetched_at
2026-10-25T04:37:05Z
stats
{"timeout":0,"harmless":47,"malicious":12,"suspicious":0,"undetected":33}

URLScan

Malicious · engine verdict · score 93

SHA-256 b4e877afd60b43eddae60b71cad6cb0d46d710384ba77769c726cbba7cb1dea1

Open report
URLScanOriginal source recordObserved: 20 fields

Observed: · Retrieved:

Report ID

01a17146-c2bf-712d-94ff-efeab4497c6e

Final URL

https://customer-p.firebaseapp.com/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://customer-p.firebaseapp.com/
    From
    http://customer-p.firebaseapp.com/
    Status
    307
  • To
    http://customer-p.firebaseapp.com/
    From
    https://customer-p.firebaseapp.com/
    Status
    307
  • To
    https://customer-p.firebaseapp.com/
    From
    http://customer-p.firebaseapp.com/
    Status
    301

IP address

199.36.158.100

Contacted domains

  • app42.host

Contacted IP addresses

  • 199.36.158.100

Autonomous systems (ASN)

  • 54113

Server countries

  • US

Document hash

b4e877afd60b43eddae60b71cad6cb0d46d710384ba77769c726cbba7cb1dea1

JavaScript globals

  • LIB_phrase
  • LIB_view
  • ____media
  • ____b
  • ____rdr
  • d
  • s

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

1640

Registered domain age, days

1640

Certificate age, days

31

Certificate validity, days

89

Page requests

7

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
93
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
01a17146-c2bf-712d-94ff-efeab4497c6e
Final url
https://customer-p.firebaseapp.com/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://customer-p.firebaseapp.com/",
        "from": "http://customer-p.firebaseapp.com/",
        "status": 307
    },
    {
        "to": "http://customer-p.firebaseapp.com/",
        "from": "https://customer-p.firebaseapp.com/",
        "status": 307
    },
    {
        "to": "https://customer-p.firebaseapp.com/",
        "from": "http://customer-p.firebaseapp.com/",
        "status": 301
    }
]
Ip
199.36.158.100
Contacted domains
[
    "app42.host"
]
Contacted IP addresses
[
    "199.36.158.100"
]
Asns
[
    "54113"
]
Countries
[
    "US"
]
Document hash
b4e877afd60b43eddae60b71cad6cb0d46d710384ba77769c726cbba7cb1dea1
Globals
[
    "LIB_phrase",
    "LIB_view",
    "____media",
    "____b",
    "____rdr",
    "d",
    "s"
]
Tls
{
    "san": [
        "firebaseapp.com",
        "*.firebaseapp.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WR4",
    "subject": "firebaseapp.com",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-22T18:00:28Z",
    "valid_from": "2026-09-23T18:00:29Z"
}
Domain age days
1640
Apex age days
1640
Tls age days
31
Tls valid days
89
Requests
7
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 93,
        "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 · 2026-10-25 04:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a17146-c2bf-712d-94ff-efeab4497c6e
score
0
malicious
false
result_at
2026-10-25T04:30:42Z
enriched_at
2026-10-25T09:11:42Z
source_timestamps
{"urlscan_result_at":"2026-10-25 05:30:42","urlscan_enriched_at":"2026-10-25 10:11:42"}
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

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

Open report
Separate monitor score · 0 / 100 · 2026-10-25T07:20:23Z

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-25T07:20:23Z
source_timestamp
2026-10-25 08:20:23
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: 22 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
165437

Page title and metadata

Page title
Background
Indexing directives
index, follow
Open Graph image
https://www.ovh.com/fr/images/logos/logo-ovh-twitter.jpg
Open Graph title
Webmail : Solution de messagerie professionnelle - OVHcloud
Keywords
OVH, domain names, dedicated server, web hosting, cloud computing, Dedicated Cloud, emails, exchange, VPS, NOC, network operating center, burst, bandwidth, Linux, Redhat, Debian, PHP, Perl, MySQL, Bind, Qmail, Webalizer, Webmin, backup, weekly backup, high availability, server hosting, dedicated hos
Description
Log in to Webmail
Twitter card
summary
Twitter account
@ovh
Open Graph description
Log in to Webmail

Trackers

Requests
6

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
7
TLS
113
Waiting
17
Connection
16
Download
87
Response time, ms
240

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
385844
CO₂, grams
0.0141
Cleaner than, %
1

DNS servers

Nameservers
  • IP address
    216.239.36.108
    Host
    ns-cloud-c3.googledomains.com
  • IP address
    216.239.38.108
    Host
    ns-cloud-c4.googledomains.com
  • IP address
    216.239.32.108
    Host
    ns-cloud-c1.googledomains.com
  • IP address
    216.239.34.108
    Host
    ns-cloud-c2.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 / WR4
Subject
firebaseapp.com

DNS records

A
  • 199.36.158.100
TXT
  • v=spf1 redirect=_spf.google.com
  • v=DKIM1; k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDPtW5iwpXVPiH5FzJ7Nrl8USzuY9zqqzjE0D1r04xDN6qwziDnmgcFNNfMewVKN2D1O+2J9N14hRprzByFwfQW76yojh54Xu3uSbQ3JP0A7k8o8GutRF8zbFUA8n0ZH2y0cIEjMliXY4W4LwPA7m4q0ObmvSjhd63O9d8z1XkUBwIDAQAB
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://customer-p.firebaseapp.com

Social profiles

Profiles
  • https://x.com/ovh
  • https://x.com/ovhcloud_uk

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-25T04:01:44Z",
    "first": "2026-10-25T04:01:44Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 165437
}
Page title and metadata
{
    "title": "Background",
    "robots": "index, follow",
    "ogImage": "https://www.ovh.com/fr/images/logos/logo-ovh-twitter.jpg",
    "ogTitle": "Webmail : Solution de messagerie professionnelle - OVHcloud",
    "keywords": "OVH, domain names, dedicated server, web hosting, cloud computing, Dedicated Cloud, emails, exchange, VPS, NOC, network operating center, burst, bandwidth, Linux, Redhat, Debian, PHP, Perl, MySQL, Bind, Qmail, Webalizer, Webmin, backup, weekly backup, high availability, server hosting, dedicated hos",
    "description": "Log in to Webmail",
    "twitterCard": "summary",
    "twitterSite": "@ovh",
    "ogDescription": "Log in to Webmail"
}
Trackers
{
    "requests": 6
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 7,
        "tls": 113,
        "wait": 17,
        "connect": 16,
        "download": 87
    },
    "response_ms": 240
}
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": 385844,
    "co2_grams": 0.0141,
    "cleaner_than": 1
}
Dns server
{
    "ns": [
        {
            "ip": "216.239.36.108",
            "host": "ns-cloud-c3.googledomains.com"
        },
        {
            "ip": "216.239.38.108",
            "host": "ns-cloud-c4.googledomains.com"
        },
        {
            "ip": "216.239.32.108",
            "host": "ns-cloud-c1.googledomains.com"
        },
        {
            "ip": "216.239.34.108",
            "host": "ns-cloud-c2.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 / WR4",
    "subject": "firebaseapp.com"
}
DNS records
{
    "A": [
        "199.36.158.100"
    ],
    "TXT": [
        "v=spf1 redirect=_spf.google.com",
        "v=DKIM1; k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDPtW5iwpXVPiH5FzJ7Nrl8USzuY9zqqzjE0D1r04xDN6qwziDnmgcFNNfMewVKN2D1O+2J9N14hRprzByFwfQW76yojh54Xu3uSbQ3JP0A7k8o8GutRF8zbFUA8n0ZH2y0cIEjMliXY4W4LwPA7m4q0ObmvSjhd63O9d8z1XkUBwIDAQAB"
    ],
    "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://customer-p.firebaseapp.com"
    ]
}
Social profiles
{
    "profiles": [
        "https://x.com/ovh",
        "https://x.com/ovhcloud_uk"
    ]
}
HTTP headers
{
    "headers": {
        "content-type": "text/html; charset=utf-8",
        "strict-transport-security": "max-age=31556926; includeSubDomains; preload"
    }
}
Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 7 captures

Primary capture 1 / 7
SourcePrimary capture
Recorded
StateStored capture
Position1 / 7
Open capture Wayback Download
All capture links and hashes (7)
customer-p.firebaseapp.com: caution — 15/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical).
Social preview card customer-p.firebaseapp.com: caution — 15/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical). v 02e1b793d764

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 93 report ↗
IP Context United States199.36.158.100 Fastly shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider Google Domains US(US)
Abuse contactnetwork-abuse@google.com, cloud-abuse@google.com
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 25, 2026
DOM Analysisanalyzed Oct 25, 2026score 93/100
Submitted URLhttp://customer-p.firebaseapp.com/
Observed page title
Background
TLS Certificate
Issued by WR4 · stored validity ends in 51 days

Network & certificates

Stored technical evidence

Network & DNS

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

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

TLS certificate

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

viewdns.info · 199.36.158.100rapiddns.io

Latest Classified Outcome 2026-10-31 23:08:55 UTC

The site was serving its pages at the latest check.

Technical details
Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Stale Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-31 23:08:55 UTC
RDAP registration
Observed timeline last reachable: 2026-10-31 23:08:55 UTC last content: 2026-10-31 23:08:55 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

12 / 92 security vendors flagged this domain
View on VT
Last analyzed
alphaMountain.ai
BitDefender
Chong Lua Dao
CyRadar
DNS8
ESET
Forcepoint ThreatSeeker
G-Data
Gridinsoft
Lionic
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://customer-p.firebaseapp.com/
Final URL: https://customer-p.firebaseapp.com/
Background
Log in to Webmail
Response
HTTP 200
HTML body
376.8 KB
Compressed
160.6 KB
Links
0 internal · 0 external
Detected technologies
vue
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
Open Graph title: Webmail : Solution de messagerie professionnelle - OVHcloud
Open Graph description: Log in to Webmail
Twitter card: summary
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
164424
Content-Type
text/html; charset=utf-8
Date
Sun, 25 Oct 2026 04:01:45 GMT
Etag
"87cdcde9d49cb26168eecc0d29f4e209fa559276757f7dbfd9a3cb0ae09f20fd"
Last-Modified
Thu, 28 Apr 2022 08:34:48 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-yyz-cyyz770074-YYZ
X-Timer
S1792900905.102695,VS0,VE3

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

Archived
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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

Captured network requests

Network requests: 7 SHA-256 hashes: 1 URLScan scan:

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

Open this scan on URLScan 01a17146-c2bf-712d-94ff-efeab4497c6e ↗

Stored observation history2

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    live_content

    content_served

  2. Domain monitor · First collection record

    Reachable

All retained availability observations28

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

  1. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 00:08:55.000000
    Evidence SHA-256
    1a1d09a8f432839e9b8b4d67caad277634bbb38912b1b22472789d979233672a
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 00:08:55
    Evidence reason
    alive_content
  2. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 00:08:55.000000
    Evidence SHA-256
    1a1d09a8f432839e9b8b4d67caad277634bbb38912b1b22472789d979233672a
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 00:08:55
    Evidence reason
    alive_content
  3. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:09:34.000000
    Evidence SHA-256
    341b1842f82d414c6c7325bbc1aa22a0891042da81e224bf8ff94ec2d2cd9400
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:09:34
    Evidence reason
    alive_content
  4. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:09:34.000000
    Evidence SHA-256
    341b1842f82d414c6c7325bbc1aa22a0891042da81e224bf8ff94ec2d2cd9400
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:09:34
    Evidence reason
    alive_content
  5. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 03:30:41.000000
    Evidence SHA-256
    dd2275c137e50abeeb891af8a0fd208695d0cfa7c429b601896d1162877c36a9
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 03:30:41
    Evidence reason
    alive_content
  6. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 03:30:41.000000
    Evidence SHA-256
    dd2275c137e50abeeb891af8a0fd208695d0cfa7c429b601896d1162877c36a9
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 03:30:41
    Evidence reason
    alive_content
  7. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:06:58.000000
    Evidence SHA-256
    14f95462dd7c97b3d0612e6ac298224c0c7b25a930ad74eb2c6136568a3f14e7
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 12:06:58
    Evidence reason
    alive_content
  8. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:06:58.000000
    Evidence SHA-256
    14f95462dd7c97b3d0612e6ac298224c0c7b25a930ad74eb2c6136568a3f14e7
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 12:06:58
    Evidence reason
    alive_content
  9. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:07:16.000000
    Evidence SHA-256
    3e15c2c5bb404d9e4c9bf68bc759e5dfc4756e0199748b1f4d5bfbde9feb4fb1
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:07:16
    Evidence reason
    alive_content
  10. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:07:16.000000
    Evidence SHA-256
    3e15c2c5bb404d9e4c9bf68bc759e5dfc4756e0199748b1f4d5bfbde9feb4fb1
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:07:16
    Evidence reason
    alive_content
  11. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 12:07:35.000000
    Evidence SHA-256
    1a4b811479309133174f1705e7fcdaf80a1792f990c9a59fe0e138dea0affdf9
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:07:35
    Evidence reason
    alive_content
  12. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 12:07:35.000000
    Evidence SHA-256
    1a4b811479309133174f1705e7fcdaf80a1792f990c9a59fe0e138dea0affdf9
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:07:35
    Evidence reason
    alive_content
  13. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 03:35:45.000000
    Evidence SHA-256
    86ea42d208d53dcb1507fba2214425f1236ebc011a96696e6569f301623cbb90
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 03:35:45
    Evidence reason
    alive_content
  14. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 03:35:45.000000
    Evidence SHA-256
    86ea42d208d53dcb1507fba2214425f1236ebc011a96696e6569f301623cbb90
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 03:35:45
    Evidence reason
    alive_content
  15. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 12:01:41.000000
    Evidence SHA-256
    22617f5c11c41925a2cc1d8d8970eeaa6ad410ba00bb57fea5137a8c7ab8e424
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 12:01:41
    Evidence reason
    alive_content
  16. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 12:01:41.000000
    Evidence SHA-256
    22617f5c11c41925a2cc1d8d8970eeaa6ad410ba00bb57fea5137a8c7ab8e424
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 12:01:41
    Evidence reason
    alive_content
  17. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 00:02:14.000000
    Evidence SHA-256
    9ff7c53ff9f120c58a501be0fff1a7e8240b0230a335df13ff30bd5f7103854f
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 00:02:14
    Evidence reason
    alive_content
  18. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 00:02:14.000000
    Evidence SHA-256
    9ff7c53ff9f120c58a501be0fff1a7e8240b0230a335df13ff30bd5f7103854f
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 00:02:14
    Evidence reason
    alive_content
  19. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:02:21.000000
    Evidence SHA-256
    340d87e8f1641eec355e969f2079aecaa7fd84d4a625e4bffe9611dc7d1b38a0
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 12:02:21
    Evidence reason
    alive_content
  20. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:02:21.000000
    Evidence SHA-256
    340d87e8f1641eec355e969f2079aecaa7fd84d4a625e4bffe9611dc7d1b38a0
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 12:02:21
    Evidence reason
    alive_content
  21. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 13:02:18.000000
    Evidence SHA-256
    2ac92f9fc9607458650587714b0feae8f495b3cd4aa0d8963351fcb74e0a2495
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 13:02:18
    Evidence reason
    alive_content
  22. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 13:02:18.000000
    Evidence SHA-256
    2ac92f9fc9607458650587714b0feae8f495b3cd4aa0d8963351fcb74e0a2495
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 13:02:18
    Evidence reason
    alive_content
  23. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 01:19:17.000000
    Evidence SHA-256
    38e4b6b76cd9a004b30c5ab4d59a49dc89bfa4c6f1f3421ccf608a74a4befa79
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 01:19:17
    Evidence reason
    alive_content
  24. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 01:19:17.000000
    Evidence SHA-256
    38e4b6b76cd9a004b30c5ab4d59a49dc89bfa4c6f1f3421ccf608a74a4befa79
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 01:19:17
    Evidence reason
    alive_content
  25. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 13:22:46.000000
    Evidence SHA-256
    410a27afd2af3ce654241e5d2be12c458f36ec0e8545c039a3bccb21b9677f07
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 13:22:46
    Evidence reason
    alive_content
  26. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 13:22:46.000000
    Evidence SHA-256
    410a27afd2af3ce654241e5d2be12c458f36ec0e8545c039a3bccb21b9677f07
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 13:22:46
    Evidence reason
    alive_content
  27. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 05:18:46.000000
    Evidence SHA-256
    b46d89d3221b541332f82c13784b5901f0e68d105d3f069bc3087d4be3c7dd26
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 05:18:46
    Evidence reason
  28. http_observationunknown
    Observation source
    http_observation
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 05:18:46.000000
    Evidence SHA-256
    b46d89d3221b541332f82c13784b5901f0e68d105d3f069bc3087d4be3c7dd26
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 05:18:46
    Evidence reason

Threat Response Pipeline

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

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

Pre-emptive Discovery & IngestionThreat Ingested Recorded: 1 of 1
  • Threat Ingested
    customer-p.firebaseapp.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Web Archive · VirusTotal · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 6 of 6
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 93
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 12/92
  • 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 · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

4 entries
  1. Added to PhishDestroy

    customer-p.firebaseapp.com

    View source
  2. URLScan

    Page captured

    View source
  3. Wayback Machine

    Page archived

    View source
  4. VirusTotal

    12/92 engine detections

    View source
How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

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

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

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

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

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

Check for cloaking

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

customer-p.firebaseapp.com

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 12 det. ChainPatrol URLQuery 4 det. 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 Last known active
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
If credentials were compromised, report immediately. Do not engage with recovery scammers.

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

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
More official reporting routes
FTC ReportFraud United States

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

IdentityTheft.gov United States

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

CISA United States

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

CSIRTs Network European Union

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

FIRST Worldwide

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

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

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

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

Report to Your Local Authorities

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

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

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

97-country directory

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

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

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

What should I do immediately?

Urgent

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

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

What information should I collect for my report?

FBI guidelines

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

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including customer-p.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

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