Skip to security report
Domain security and threat intelligence
correosdecr.web.app favicon

correosdecr.web.app

“Correos”

Registrar
Google Domains
Resolved IP
199.36.158.100
PhishDestroy assessment High
First observed Oct 24, 2026 21:49 UTC · PhishDestroy
Record details & risk signals
Oct 24, 2026 CDN
Stored PhishDestroy threat listing
Page captures
open gallery
API
Suspicious Domain — Listed on PhishDestroy
Stored PhishDestroy threat listing. Exercise extreme caution — do not enter credentials or personal information.
Source evidence 1 sources
SourceResultRecorded · UTCEvidence

URLScan

No malicious flag

Open report

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

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 3 captures

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context Fastly shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider Google Domains US(US)
Technical detailsProvenance & timestamps
First DetectedOct 24, 2026
DOM Analysisanalyzed Oct 25, 2026score 68/100
Submitted URLhttp://correosdecr.web.app/
Favicon Hash
Observed page title
Correos
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, Inc.
Observed location
Mountain View, US

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-24 22:02:05 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
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.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
URLScan · 2026-10-24T21:47:51Z

Observed: · Retrieved:

Uuid
01a16fe2-4424-7525-a46b-1c666c2b4f05
Final url
https://correosdecr.web.app/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://correosdecr.web.app/",
        "from": "http://correosdecr.web.app/",
        "status": 307
    }
]
Ip
199.36.158.100
Contacted domains
[
    "pro.ip-api.com",
    "rivelpas.online"
]
Contacted IP addresses
[
    "51.195.5.58",
    "199.36.158.100"
]
Asns
[
    "16276",
    "54113"
]
Countries
[
    "DE",
    "US"
]
Document hash
77409a79691b60360d62ef1143f775728402f3d11c95b61a5e18ef4f98a041e2
Script hashes
[
    "d6781562aad708b49ff968baace9b30da2e6748fb20b8dccdbcf7a7977ded0df",
    "f27100d0c2de21ef8782ee7e47c424d032e54d13425854c68b6507e8b9004e69",
    "689e91b00ada17ee72ee39cfb64479a45eef0d4445e379c50a0b5b0449377dae"
]
Globals
[
    "addSlashes",
    "formats",
    "numberValidation",
    "webpackChunkcorreos",
    "Zone",
    "__zone_symbol__Promise",
    "__zone_symbol__fetch",
    "__zone_symbol__setTimeout",
    "__zone_symbol__clearTimeout",
    "__zone_symbol__setInterval",
    "__zone_symbol__clearInterval",
    "__zone_symbol__requestAnimationFrame",
    "__zone_symbol__cancelAnimationFrame",
    "__zone_symbol__webkitRequestAnimationFrame",
    "__zone_symbol__webkitCancelAnimationFrame",
    "__zone_symbol__alert",
    "__zone_symbol__prompt",
    "__zone_symbol__confirm",
    "__zone_symbol__MutationObserver",
    "__zone_symbol__WebKitMutationObserver",
    "__zone_symbol__IntersectionObserver",
    "__zone_symbol__FileReader",
    "__zone_symbol__ononpagerevealpatched",
    "__zone_symbol__ononsearchpatched",
    "__zone_symbol__ononappinstalledpatched",
    "__zone_symbol__ononbeforeinstallpromptpatched",
    "__zone_symbol__ononabortpatched",
    "__zone_symbol__ononbeforeinputpatched",
    "__zone_symbol__ononbeforematchpatched",
    "__zone_symbol__ononbeforetogglepatched",
    "__zone_symbol__ononblurpatched",
    "__zone_symbol__ononcancelpatched",
    "__zone_symbol__ononcanplaypatched",
    "__zone_symbol__ononcanplaythroughpatched",
    "__zone_symbol__ononchangepatched",
    "__zone_symbol__ononclickpatched",
    "__zone_symbol__ononclosepatched",
    "__zone_symbol__ononcommandpatched",
    "__zone_symbol__ononcontentvisibilityautostatechangepatched",
    "__zone_symbol__ononcontextlostpatched"
]
Tls
{
    "san": [
        "web.app",
        "*.web.app"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WR4",
    "subject": "web.app",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-22T17:59:57Z",
    "valid_from": "2026-09-23T17:59:58Z"
}
Domain age days
815
Apex age days
815
Tls age days
31
Tls valid days
89
Requests
16
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"
}
VirusTotal · 2026-10-14T23:30:47Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 47,
    "malicious": 16,
    "suspicious": 0,
    "undetected": 29
}
Vendor labels
{
    "DNS8": "phishing",
    "ESET": "phishing",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Gridinsoft": "phishing",
    "BitDefender": "phishing",
    "Criminal IP": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
Registrar
MarkMonitor Inc.
Created
2019-01-08T22:05:04Z
Expires
2026-01-08T22:05:04Z
Updated
2024-12-12T10:14:49Z
First seen
2024-07-29T22:10:41Z
DNS records
[
    {
        "ttl": 21600,
        "type": "AAAA",
        "value": "2620:0:890::100"
    },
    {
        "ttl": 21600,
        "type": "A",
        "value": "199.36.158.100"
    }
]
Dns at
2026-10-14T23:30:57Z
Jarm
29d3fd00029d29d00041d41d00041d6b5eefa2404a56c2ced79a0d16afe36c
Certificate
{
    "san": [
        "web.app",
        "*.web.app"
    ],
    "issuer": "Google Trust Services / WR4",
    "serial": "e26d762a101120cd12a8f68d86c31d05",
    "sha256": "7175912cef4e9b3d3f320d60e4e926f7cb6a2f624028de25218038a3f679e095",
    "subject": "web.app",
    "valid_to": "2026-12-22T17:59:57Z",
    "valid_from": "2026-09-23T17:59:58Z"
}
Registration record
{
    "registrar": "MarkMonitor Inc.",
    "registrar_iana_id": "292",
    "registrar_url": "http://www.markmonitor.com",
    "created": "2019-01-08T22:05:04Z",
    "updated": "2024-12-12T10:14:49Z",
    "expires": "2026-01-08T22:05:04Z",
    "status": [
        "clientDeleteProhibited",
        "clientTransferProhibited",
        "clientUpdateProhibited"
    ],
    "nameservers": [
        "ns1.googledomains.com",
        "ns2.googledomains.com",
        "ns3.googledomains.com",
        "ns4.googledomains.com"
    ],
    "dnssec": "unsigned"
}
Stored observation history1

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

  1. Availability monitor · First collection record

    Reachable

Recorded activity

2 entries
  1. Added to PhishDestroy

    correosdecr.web.app

    View source
  2. URLScan

    Page captured

    View source

Check for cloaking

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

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

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 →

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

Live Threat Feed Appeal This Listing
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/correosdecr.web.app"
  title="PhishDestroy threat report for correosdecr.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>