Skip to main content
Sandfish

MetLife Core Life Insurance — Enterprise Architecture Schematic

https://metlife-core-architecture.vercel.app/

Group1de859bb-b5b3-483c-aba3-fdf9b299de55submitted urlMember 1

Results

Rules engine

AI review

AI case description

The Vercel-hosted page presents a MetLife-branded enterprise architecture schematic, with no credential forms, submissions, or observed authentication traffic. The evidence does not establish whether the page is authorized or intended to impersonate MetLife.

Findings

Analyzed page

Language
Detecting...

Infrastructure

Domain registration
vercel.appMore than 90 days oldRegistered 2020-01-28 · Registrar Tucows Domains Inc
Hosting
Loading...

Capture activity

Interaction
3 actions · 0 submissions · stopped: repeated state · download stage: no payload control
  1. 1. clicksucceeded🔐 Ping Server / Central IAM Platform Central SSO Engine SYS-ID: PING-IAM • SSO Login Gateway for CLiCS, Lifeline Plus, One By MetLife & MyLife SSO: CLiCS SSO: Lifeline Plus
  2. 2. clicksucceeded💳 OPS Payment Suite OPS-CORE-SUITE Inbound Cash-In WPS (Web 7 Types) APS (API bKash/City) EFT (BFTN Auto-Debit) RTP (Real-Time) ZERO CLiCS Link [dispatched]
  3. 3. clicksucceeded⭐ Lifeline Core PAS & Admin LIFELINE-CORE-SSOT Core SSOT STRICT ARCHITECTURAL RULE: Holds INDIVIDUAL Policy Master Data ONLY . Group corporate master records NEVER reside here. [dispatched]
Kit source work

Loading related source work…

Discover or upload kit source

Analysis metadata

How and when the analysis ran.

Processing status
Evidence coverage
Input kind
url
Execution kind
capture
Duration
46.0s
Navigation
1 navigation
Engine version
0.4.2
Created
2026-11-21 01:30:08Z
Started
2026-11-21 01:30:08Z
Finished
2026-11-21 01:30:54Z
Archive
31.7 KB
Analysis ID
9d780e33-68ec...

Document-source diagnostics

These records identify rejected document reads. A current epoch does not prove that a replacement read succeeded. Later success does not erase an earlier evidence limit.

No rejected document reads were recorded.

Browser-observed navigation status

The browser status can differ from the normalized origin response, including during a proxy failure. Inspect the recorded document request for origin response evidence.

NavigationBrowser-observed HTTP statusRecorded requests
0200Inspect navigation 0 requests
Showing 0–0 of 0

Signals by severity

Detected findings grouped by risk

Request activity

Network requests grouped by resource type

Behavior

Recorded actions grouped by type

Network contacts

Requests to the most active hosts

Request ownership

First-party and third-party requests

Response MIME types

Network responses grouped by MIME type