Skip to security report
Domain security and threat intelligence
customer-iam-test-4a9cc.web.app favicon

customer-iam-test-4a9cc.web.app

In short

customer-iam-test-4a9cc.web.app is a credential phishing page detected by PhishDestroy on 2026-10-25. Risk: critical (80/100). Registrar: Google Domains. Hosting: FASTLY - Fastly, Inc., US. Google Safe Browsing flags it. Do not enter credentials or connect a wallet.

“Login NEW”

Registrar
Google Domains
Resolved IP
199.36.158.100
PhishDestroy assessment Critical
First observed Oct 25, 2026 04:18 UTC · PhishDestroy
Scam type: Credential Phishing Google Safe Browsing: threat flag recorded
VirusTotal
Not recorded
OTX
community references
Cloudflare Radar
Not recorded
Page captures
open gallery
Domain age
Not recorded
Reports sent
No sent record
Oct 25, 2026 CDN
API
This domain has been flagged as malicious
PhishDestroy forensic analysis flagged this domain. Exercise extreme caution — do not enter credentials or personal information.
Source evidenceGoogle Safe Browsing: flagged 3 sources

Google Safe Browsing

Threat flag recorded

Open report

OTX

no community references

Open report

URLScan

No malicious flag

Open report

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Questions about customer-iam-test-4a9cc.web.app

Is customer-iam-test-4a9cc.web.app legit?

No. PhishDestroy classifies customer-iam-test-4a9cc.web.app as a credential phishing page (risk: critical, 80/100); it was first detected on 2026-10-25. Google Safe Browsing flags it. Treat the site as unsafe.

Is customer-iam-test-4a9cc.web.app safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on customer-iam-test-4a9cc.web.app. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used customer-iam-test-4a9cc.web.app?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 3 captures

All capture links and hashes (3)

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
Google Safe Browsing Flagged Social engineering checked Oct 25, 2026
IP Context Fastly shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider Google Domains US(US)
Abuse contactcloud-abuse@google.com
Technical detailsProvenance & timestamps
First DetectedOct 25, 2026
DOM Analysisanalyzed Oct 25, 2026score 10/1004 brand signals
Submitted URLhttp://customer-iam-test-4a9cc.web.app/
Favicon Hash
Observed page title
Login NEW
Automated brand references
Apple Facebook Google Microsoft
TLS Certificate
Issued by Google Trust Services / WR4 · stored validity ends in 58 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
199.36.158.100
Network ASN
AS54113
Organization
FASTLY - Fastly, Inc., US
Observed location
US
Server header
Google Tag Manager

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WR4
Valid from
2026-09-23 17:59:58
Valid until
2026-12-22 17:59:57
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-25 05:02:12 UTC
Collection source
PhishDestroy collector
Certificate fingerprint7175912cef4e9b3d3f320d60e4e926f7cb6a2f624028de25218038a3f679e095
Certificate names · 1 SAN
  • web.app

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

Report This Domain Submit evidence & help protect others

Archived Evidence

Wayback Machine Snapshot
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-iam-test-4a9cc.web.app/
Final URL: https://customer-iam-test-4a9cc.web.app/
Login NEW
Zentraler Authentifizierungsdienst der NEW Gruppe - Ihr starker Partner
Response
HTTP 200
HTML body
7.0 KB
Compressed
1.9 KB
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
1902
Content-Type
text/html; charset=utf-8
Date
Sun, 25 Oct 2026 04:01:45 GMT
Etag
"34c5472c75aac456338b63470d415d4e3feb7943ca8594cb4086a9a50ce2577c"
Last-Modified
Tue, 13 Oct 2026 11:50:15 GMT
Strict-Transport-Security
max-age=31556926; includeSubDomains; preload
Vary
x-fh-requested-host, accept-encoding
X-Cache
MISS
X-Cache-Hits
0
X-Served-By
cache-ber1080020-BER
X-Timer
S1792900905.285363,VS0,VE51

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

Registration & observation details1

Availability observations

Last reachable observation

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

Stored observation history2

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

  1. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

  2. Availability monitor · First collection record

    Reachable

All retained availability observations1

Source: availability monitor. This journal includes earlier observations and repeated states with distinct dates or evidence. Identical records appear once; an unknown state is not proof that the site is offline.

  1. unknown
    Cause
    probe_inconclusive
    Monitor confidence
    20
    Original source timestamp
    2026-10-25 05:18:15.000000
    Evidence SHA-256
    f2bc2978ac54f63a89d9610438bde49669ce03cf8f03b7091b1b2e7626560229

Recorded activity

4 entries
  1. Google Safe Browsing

    Threat flag recorded

    View source
  2. Added to PhishDestroy

    customer-iam-test-4a9cc.web.app

    View source
  3. URLScan

    Page captured

    View source
  4. Wayback Machine

    Page archived

    View source

Check for cloaking

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

customer-iam-test-4a9cc.web.app

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked Unverified
If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Report to Your Local Authorities

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

97-country directory

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

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

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

What should I do immediately?

Urgent

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

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

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

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

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

Where should I report the scam?

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

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

How do phishing scams typically work?

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

How can I protect myself in the future?

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

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

Stay Informed, Stay Safe

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

Official reporting routes

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

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

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

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/customer-iam-test-4a9cc.web.app"
  title="PhishDestroy threat report for customer-iam-test-4a9cc.web.app"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>