metlifetakealongdentalinsurance.test.ciapps-sandbox.com is a blocklisted domain detected by PhishDestroy on 2026-09-04. Risk: critical (78/100). Registrar: DNC Holdings. Status: Reachable · access restricted. Hosting: Microsoft Corporation. VirusTotal: 5/92 engines flag it. Do not enter credentials or connect a wallet.
This domain carries the page title "MetLife" and a hostname built around a MetLife dental insurance product. It sits on a sandbox-style subdomain with no visible connection to the insurer's own web presence. PhishDestroy first saw it on 2026-09-04 and added it to the blocklist as a suspicious domain. As of 2026-10-19 the site was still online, with its content behind access protection.
How the scam works
The page presents itself as MetLife, and the hostname reads like a dental coverage offer. That makes it a plausible trap for anyone shopping for or managing a dental plan. Pages that borrow an insurer's name usually ask for personal details, policy or member numbers, account logins or a card payment for a supposed premium. Whatever is typed in goes to whoever runs the site, not to MetLife. The hostname uses a "test" label on a sandbox domain, while PhishDestroy lists it as a suspicious brand lookalike.
Evidence
On 2026-10-19, VirusTotal showed 5 of 92 engines flagging the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft and SOCRadar. That is a small share of engines. Still, it comes from five unrelated vendors, so the domain is drawing independent attention rather than a single outlier verdict. Apart from PhishDestroy's own listing, no other blocklist carries it yet.
Infrastructure
The parent domain was registered through DNC Holdings, Inc. on 2026-05-19, about 108 days before PhishDestroy flagged this hostname. It resolves to Microsoft Corporation cloud address space geolocated in South Africa. A valid GeoTrust certificate issued through DigiCert means visitors see a normal padlock. That says nothing about whether the site is legitimate.
What to do
If you entered a MetLife or other insurance login here, change that password, plus any account reusing it, and turn on two-factor authentication. If you entered card details or paid anything, contact your bank to dispute the charge and replace the card. If you shared a policy number, date of birth or ID details, call MetLife through the number on your card or official documents to report possible misuse. Security teams should block the hostname at the proxy and DNS layer, search mail logs for messages linking to it, and report it to the hosting provider and registrar.
Questions about metlifetakealongdentalinsurance.test.ciapps-sandbox.com
Is metlifetakealongdentalinsurance.test.ciapps-sandbox.com legit?
No. PhishDestroy classifies metlifetakealongdentalinsurance.test.ciapps-sandbox.com as a blocklisted domain (risk: critical, 78/100); it was first detected on 2026-09-04. VirusTotal: 5/92 engines flag it. Treat the site as unsafe.
Is metlifetakealongdentalinsurance.test.ciapps-sandbox.com safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on metlifetakealongdentalinsurance.test.ciapps-sandbox.com. 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 metlifetakealongdentalinsurance.test.ciapps-sandbox.com?
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.
IP Reputationabuse score 1/1001 reportDDoS AttackFTP Brute-ForcePing of DeathPort ScanHackingSQL InjectionSpoofingBrute-ForceBad Web BotExploited HostWeb App AttackSSHIoT Targetedchecked Oct 15, 2026
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeReachable but protectedreason: HTTP access restricted50% confidence
Attributionmechanism: Access Restrictionsource: Current Http Probe
Evidence layersAvailability: Reachable but protectedContent: UnknownDNS: ResolvedRegistration: Unknown
Latest HTTP observationReachable but protectedHTTP access restrictedAccess Restriction50%2026-10-22 10:29:50 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-22 10:29:50 UTClast content: 2026-10-21 10:31:02 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.
Technologies · 3 identified
A
Azure Front Door
Load balancers
Azure Front Door is a scalable and secure entry point for fast delivery of your global web applications.
2 evidence signal groups linked0 stored notification recordsReachable · access restricted
Listed domains receive at least one abuse report; this entry has no retained notification history.
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.
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 →
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 metlifetakealongdentalinsurance.test.ciapps-sandbox.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)
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
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.
