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

mail-verifications.netlify.app

In short

PhishDestroy records that mail-verifications.netlify.app resolved to a Google search page at capture time, not the Polish verification page its title claims.

“Weryfikacja dwuetapowa Aby chronić Twoje konto, musimy mieć pewność, że to naprawdę Ty próbujesz się zalogować”

Review the evidence
Registrar
United StatesNetlify
Resolved IP
Germany35.157.26.135Amazon.com, Inc. · CDN
First observed
Oct 31, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 17/92
VirusTotal
17 / 92
engine detections ·
URLScan
Malicious
Cloudflare Radar
Phishing
Page captures
7
open gallery
Oct 31, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy records that mail-verifications.netlify.app resolved to a Google search page at capture time, not the Polish verification page its title claims.

Critical
Status
Last known active
VirusTotal
17 / 92
Hosting
Germany35.157.26.135Amazon.com, Inc. · CDN
Registrar
United StatesNetlify
Page captures
7
Page captures Source results Registration record

PhishDestroy analysis, reviewed version

The captured page for mail-verifications.netlify.app shows a Google search interface with a search box, quick-action chips and a "Happy Halloween!" note, while the recorded HTML title instead reads "Weryfikacja dwuetapowa Aby chronić Twoje konto, musimy mieć pewność, że to naprawdę Ty próbujesz się zalogować". The main interaction visible is entering a query into the search field, and the capture ended on www.google.com rather than on a verification form.

The stored VirusTotal domain result reports 17 detections out of 92 engines. DNS8 reported "suspicious"; ESET reported "suspicious".

Source evidenceVirusTotal 17 / 92 8 sources

VirusTotal

17 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
45
Malicious
14
Suspicious
3
Undetected
30

Vendor labels

DNS8
suspicious
ESET
suspicious
VIPRE
phishing
G-Data
phishing
Lionic
phishing
Sophos
phishing
Webroot
malicious
Emsisoft
phishing
Fortinet
phishing
Netcraft
malicious
SOCRadar
phishing
Kaspersky
phishing
Seclookup
malicious
Gridinsoft
suspicious
BitDefender
phishing
alphaMountain.ai
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Registrar

Name.com, Inc.

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    120
    Type
    A
    Value
    98.84.224.111
  • TTL, seconds
    311
    Type
    AAAA
    Value
    2600:1f18:16e:df01::259
  • TTL, seconds
    311
    Type
    AAAA
    Value
    2600:1f18:16e:df01::258
  • TTL, seconds
    120
    Type
    A
    Value
    18.208.88.157

DNS records observed

JARM fingerprint

40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319

Certificate

Subject alternative names
  • *.netlify.app
  • netlify.app
Issuer
DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1
Serial
cd5d0afb0611b5bd9d692535c0ca7c4
SHA-256
bc3a8134c21a842e64ea34d488826dd2ba50f59a3bcbaed1e6b71a4242de1478
Subject
*.netlify.app
Valid until
Valid from

Registration record

Registrar
Name.com, Inc.
Registrar IANA ID
625
Registrar URL
http://www.name.com
Registered
Updated
Expires
Status
  • clientTransferProhibited
Nameservers
  • dns1.p01.nsone.net
  • dns2.p01.nsone.net
  • dns3.p01.nsone.net
  • dns4.p01.nsone.net
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 45,
    "malicious": 14,
    "suspicious": 3,
    "undetected": 30
}
Vendor labels
{
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "Webroot": "malicious",
    "Emsisoft": "phishing",
    "Fortinet": "phishing",
    "Netcraft": "malicious",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Registrar
Name.com, Inc.
Created
2018-05-08T22:48:05Z
Expires
2025-05-08T22:48:05Z
Updated
2024-04-11T16:00:14Z
First seen
2026-06-09T13:09:52Z
DNS records
[
    {
        "ttl": 120,
        "type": "A",
        "value": "98.84.224.111"
    },
    {
        "ttl": 311,
        "type": "AAAA",
        "value": "2600:1f18:16e:df01::259"
    },
    {
        "ttl": 311,
        "type": "AAAA",
        "value": "2600:1f18:16e:df01::258"
    },
    {
        "ttl": 120,
        "type": "A",
        "value": "18.208.88.157"
    }
]
Dns at
2026-10-21T11:01:30Z
Jarm
40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319
Certificate
{
    "san": [
        "*.netlify.app",
        "netlify.app"
    ],
    "issuer": "DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1",
    "serial": "cd5d0afb0611b5bd9d692535c0ca7c4",
    "sha256": "bc3a8134c21a842e64ea34d488826dd2ba50f59a3bcbaed1e6b71a4242de1478",
    "subject": "*.netlify.app",
    "valid_to": "2027-03-19T23:59:59Z",
    "valid_from": "2026-02-16T00:00:00Z"
}
Registration record
{
    "registrar": "Name.com, Inc.",
    "registrar_iana_id": "625",
    "registrar_url": "http://www.name.com",
    "created": "2018-05-08T22:48:05Z",
    "updated": "2024-04-11T16:00:14Z",
    "expires": "2025-05-08T22:48:05Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "dns1.p01.nsone.net",
        "dns2.p01.nsone.net",
        "dns3.p01.nsone.net",
        "dns4.p01.nsone.net"
    ],
    "dnssec": "unsigned"
}
Separate source record · 14 malicious + 3 suspicious / 92 · 2026-10-21 10:56:15 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-21T10:56:15Z
fetched_at
2026-10-31T12:28:08Z
stats
{"timeout":0,"harmless":45,"malicious":14,"suspicious":3,"undetected":30}

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Report ID

da2882f5-2ce3-4a84-9a69-64b17e6ee959

Final URL

https://www.google.com/

HTTP response

200

Navigation history

  • URL
    https://mail-verifications.netlify.app/
    Status
    200
  • URL
    https://google.com/
    Status
    301
  • URL
    https://www.google.com/
    Status
    200

DOM structure hash

8142102f8e170f0af4ff33f1840d85ee3a01a25620967257f7847ef5aa1b33fc

Document hash

78c27c3142306e7507e00c106676b2032f75c6c328ad63cc2b05d8a696736af8

Phishing classifier result

  • phishing

Domain risk categories

  • Search Engines
  • Technology
  • News, Portal & Search

Cloudflare Radar rank

Rank
1
Rank range
200

DNS records

  • Name
    google.com
    Type
    A
    Value
    142.251.45.14
  • Name
    google.com
    Type
    AAAA
    Value
    2607:f8b0:4007:808::200e
  • Name
    ogads-pa.clients6.google.com
    Type
    A
    Value
    142.251.34.74
  • Name
    ogads-pa.clients6.google.com
    Type
    AAAA
    Value
    2607:f8b0:4007:808::200a
  • Name
    play.google.com
    Type
    A
    Value
    142.251.150.7
  • Name
    play.google.com
    Type
    A
    Value
    142.251.156.7
  • Name
    play.google.com
    Type
    A
    Value
    142.251.157.7
  • Name
    play.google.com
    Type
    A
    Value
    142.251.152.7
  • Name
    play.google.com
    Type
    A
    Value
    142.251.151.7
  • Name
    play.google.com
    Type
    A
    Value
    142.251.154.7
  • Name
    play.google.com
    Type
    A
    Value
    142.251.153.7
  • Name
    play.google.com
    Type
    A
    Value
    142.251.155.7
  • Name
    play.google.com
    Type
    AAAA
    Value
    2001:4860:482b:700::
  • Name
    play.google.com
    Type
    AAAA
    Value
    2001:4860:482a:700::
  • Name
    play.google.com
    Type
    AAAA
    Value
    2001:4860:4829:700::

DNSSEC valid

No

IP address

127.0.1.35

127.0.1.35 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Registration record

Registrar
MarkMonitor Inc.
Registered
Updated
Expires
Nameservers
  • ns1.google.com
  • ns2.google.com
  • ns3.google.com
  • ns4.google.com
Original source fields · JSON
Uuid
da2882f5-2ce3-4a84-9a69-64b17e6ee959
Final url
https://www.google.com/
Status
200
History
[
    {
        "url": "https://mail-verifications.netlify.app/",
        "status": 200
    },
    {
        "url": "https://google.com/",
        "status": 301
    },
    {
        "url": "https://www.google.com/",
        "status": 200
    }
]
DOM structure hash
8142102f8e170f0af4ff33f1840d85ee3a01a25620967257f7847ef5aa1b33fc
Document hash
78c27c3142306e7507e00c106676b2032f75c6c328ad63cc2b05d8a696736af8
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Search Engines",
    "Technology",
    "News, Portal & Search"
]
Radar rank
{
    "rank": 1,
    "bucket": "200"
}
DNS records
[
    {
        "name": "google.com",
        "type": "A",
        "value": "142.251.45.14"
    },
    {
        "name": "google.com",
        "type": "AAAA",
        "value": "2607:f8b0:4007:808::200e"
    },
    {
        "name": "ogads-pa.clients6.google.com",
        "type": "A",
        "value": "142.251.34.74"
    },
    {
        "name": "ogads-pa.clients6.google.com",
        "type": "AAAA",
        "value": "2607:f8b0:4007:808::200a"
    },
    {
        "name": "play.google.com",
        "type": "A",
        "value": "142.251.150.7"
    },
    {
        "name": "play.google.com",
        "type": "A",
        "value": "142.251.156.7"
    },
    {
        "name": "play.google.com",
        "type": "A",
        "value": "142.251.157.7"
    },
    {
        "name": "play.google.com",
        "type": "A",
        "value": "142.251.152.7"
    },
    {
        "name": "play.google.com",
        "type": "A",
        "value": "142.251.151.7"
    },
    {
        "name": "play.google.com",
        "type": "A",
        "value": "142.251.154.7"
    },
    {
        "name": "play.google.com",
        "type": "A",
        "value": "142.251.153.7"
    },
    {
        "name": "play.google.com",
        "type": "A",
        "value": "142.251.155.7"
    },
    {
        "name": "play.google.com",
        "type": "AAAA",
        "value": "2001:4860:482b:700::"
    },
    {
        "name": "play.google.com",
        "type": "AAAA",
        "value": "2001:4860:482a:700::"
    },
    {
        "name": "play.google.com",
        "type": "AAAA",
        "value": "2001:4860:4829:700::"
    }
]
Dnssec valid
false
Ip
127.0.1.35

127.0.1.35 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Registration record
{
    "registrar": "MarkMonitor Inc.",
    "created": "1997-09-15T04:00:00Z",
    "updated": "2019-09-09T15:39:04Z",
    "expires": "2028-09-14T04:00:00Z",
    "nameservers": [
        "ns1.google.com",
        "ns2.google.com",
        "ns3.google.com",
        "ns4.google.com"
    ]
}
Separate stored summary: clean · observation date not recorded

This summary differs from the dated scan above. It is retained for provenance and does not override the selected source observation.

verdict
clean
categories
[]
observed_at
null
source_path
phishdestroy.technologies.cf_radar
scope
Separate stored summary; an absent observation date is not evidence of a clean scan.

URLScan

Malicious

SHA-256 78c27c3142306e7507e00c106676b2032f75c6c328ad63cc2b05d8a696736af8

Open report
URLScanOriginal source recordObserved: 21 fields

Observed: · Retrieved:

Report ID

01a191f6-0134-75fd-a595-f2779ca87ad1

Final URL

https://mail-verifications.netlify.app/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://mail-verifications.netlify.app/
    From
    http://mail-verifications.netlify.app/
    Status
    307

IP address

2a05:d014:58f:6200::259

Contacted domains

  • miroslavka.nport.link

Contacted IP addresses

  • 2a05:d014:58f:6200::259

Autonomous systems (ASN)

  • 16509

Server countries

  • DE

Linked domains

  • support.google.com
  • accounts.google.com

Document hash

78c27c3142306e7507e00c106676b2032f75c6c328ad63cc2b05d8a696736af8

JavaScript globals

  • app
  • VPS_WS_URL
  • SimpleGoogleLogin

TLS session and certificate

Subject alternative names
  • *.netlify.app
  • netlify.app
Cipher
AES_128_GCM
Issuer
DigiCert Global G2 TLS RSA SHA256 2020 CA1
Subject
*.netlify.app
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

143

Registered domain age, days

143

Certificate age, days

257

Certificate validity, days

396

Page requests

3

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
93
Malicious
Yes
Overall verdict
Tags
  • phishing
Score
100
Brands
  • google
Malicious
Yes
Categories
  • phishing
URLScan verdict
Tags
  • phishing
Score
100
Brands
  • Google
Malicious
Yes
Categories
  • phishing

HTTP headers

Server
Netlify
Content-type
text/html; charset=UTF-8
Strict-transport-security
max-age=31536000; includeSubDomains; preload
Original source fields · JSON
Uuid
01a191f6-0134-75fd-a595-f2779ca87ad1
Final url
https://mail-verifications.netlify.app/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://mail-verifications.netlify.app/",
        "from": "http://mail-verifications.netlify.app/",
        "status": 307
    }
]
Ip
2a05:d014:58f:6200::259
Contacted domains
[
    "miroslavka.nport.link"
]
Contacted IP addresses
[
    "2a05:d014:58f:6200::259"
]
Asns
[
    "16509"
]
Countries
[
    "DE"
]
Linked domains
[
    "support.google.com",
    "accounts.google.com"
]
Document hash
78c27c3142306e7507e00c106676b2032f75c6c328ad63cc2b05d8a696736af8
Globals
[
    "app",
    "VPS_WS_URL",
    "SimpleGoogleLogin"
]
Tls
{
    "san": [
        "*.netlify.app",
        "netlify.app"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "DigiCert Global G2 TLS RSA SHA256 2020 CA1",
    "subject": "*.netlify.app",
    "protocol": "TLS 1.3",
    "valid_to": "2027-03-19T23:59:59Z",
    "valid_from": "2026-02-16T00:00:00Z"
}
Domain age days
143
Apex age days
143
Tls age days
257
Tls valid days
396
Requests
3
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 93,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "google"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "Google"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "Netlify",
    "content-type": "text/html; charset=UTF-8",
    "strict-transport-security": "max-age=31536000; includeSubDomains; preload"
}
Separate monitor record · date not recorded

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

record_source
domain_monitor.urlscan
uuid
01a01f48-e590-760c-840c-754f3c60046a
score
null
malicious
null
result_at
null
enriched_at
null
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":null}
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

45 / 100 · heuristic score · 1 brand reference · 0 classifications

Open report

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

ai_title
mail-verifications.netlify.app — Google search page captured after redirect
ai_description
PhishDestroy records that mail-verifications.netlify.app resolved to a Google search page at capture time, not the Polish verification page its title claims.
ai_summary
The captured page for mail-verifications.netlify.app shows a Google search interface with a search box, quick-action chips and a "Happy Halloween!" note, while the recorded HTML title instead reads "Weryfikacja dwuetapowa Aby chronić Twoje konto, musimy mieć pewność, że to naprawdę Ty próbujesz się zalogować". The main interaction visible is entering a query into the search field, and the capture ended on www.google.com rather than on a verification form. The stored VirusTotal domain result reports 17 detections out of 92 engines. DNS8 reported "suspicious"; ESET reported "suspicious".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-10-31 13:34:45
revision
8d532577045e1cd71626f0187decb72826a24c3ece91dfc6fabc45a4d6e0c583
mode
reviewed
interpretation
Selected public package; text generation time is separate from source observation dates.

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 lookups
0

CAA records

Count
3
Domain
netlify.app
Allowed issuers
  • amazon.com
  • digicert.com;account=2d83e9ac9b6776c3f215150f6ebceea8cefe3bc2e1fb5efffb1d71e200575226

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
208797

Page title and metadata

Page title
Weryfikacja dwuetapowa Aby chronić Twoje konto, musimy mieć pewność, że to naprawdę Ty próbujesz się zalogować Logowanie – Konta Google
Canonical URL
https://accounts.google.com/v3/signin/challenge/ipp/verify

Trackers

Requests
0

Forms and mixed content

Upgrades insecure requests
Yes
Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
5
TLS
8
Waiting
205
Connection
10
Download
200
Response time, ms
428

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

DNS servers

Nameservers
  • IP address
    198.51.45.1
    Host
    dns2.p01.nsone.net
  • IP address
    198.51.44.65
    Host
    dns3.p01.nsone.net
  • IP address
    198.51.45.65
    Host
    dns4.p01.nsone.net
  • IP address
    198.51.44.1
    Host
    dns1.p01.nsone.net
DNS zone
netlify.app

Location

IP address
2a05:d014:58f:6200::259
ASN
16509
Organization
Amazon.com, Inc.
City
Frankfurt
Country
DE

TLS certificate

Issuer
DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1
Subject
*.netlify.app

DNS records

A
  • 35.157.26.135
  • 63.176.8.218
AAAA
  • 2a05:d014:58f:6200::259
  • 2a05:d014:58f:6200::258

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Header value
max-age=31536000; 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=31536000; includeSubDomains; preload
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
2a05:d014:58f:6200::258
IP version
6

Redirects

Redirect chain
  • https://mail-verifications.netlify.app

Page links

External link addresses
  • https://support.google.com/accounts
  • https://accounts.google.com/TOS
  • https://accounts.google.com/TOS
External links
3
Internal links
1

HTTP headers

Response headers
Server
Netlify
Content-type
text/html; charset=UTF-8
Strict-transport-security
max-age=31536000; includeSubDomains; preload
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "count": 3,
    "domain": "netlify.app",
    "issuers": [
        "amazon.com",
        "digicert.com;account=2d83e9ac9b6776c3f215150f6ebceea8cefe3bc2e1fb5efffb1d71e200575226"
    ]
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-16T03:33:40Z",
    "first": "2026-10-16T03:33:40Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 208797
}
Page title and metadata
{
    "title": "Weryfikacja dwuetapowa Aby chronić Twoje konto, musimy mieć pewność, że to naprawdę Ty próbujesz się zalogować\nLogowanie – Konta Google",
    "canonicalUrl": "https://accounts.google.com/v3/signin/challenge/ipp/verify"
}
Trackers
{
    "requests": 0
}
Forms and mixed content
{
    "upgrade_insecure": true,
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 5,
        "tls": 8,
        "wait": 205,
        "connect": 10,
        "download": 200
    },
    "response_ms": 428
}
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": 442218,
    "co2_grams": 0.0162,
    "cleaner_than": 1
}
Dns server
{
    "ns": [
        {
            "ip": "198.51.45.1",
            "host": "dns2.p01.nsone.net"
        },
        {
            "ip": "198.51.44.65",
            "host": "dns3.p01.nsone.net"
        },
        {
            "ip": "198.51.45.65",
            "host": "dns4.p01.nsone.net"
        },
        {
            "ip": "198.51.44.1",
            "host": "dns1.p01.nsone.net"
        }
    ],
    "zone": "netlify.app"
}
Location
{
    "ip": "2a05:d014:58f:6200::259",
    "asn": "16509",
    "org": "Amazon.com, Inc.",
    "city": "Frankfurt",
    "country": "DE"
}
Ssl
{
    "issuer": "DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1",
    "subject": "*.netlify.app"
}
DNS records
{
    "A": [
        "35.157.26.135",
        "63.176.8.218"
    ],
    "AAAA": [
        "2a05:d014:58f:6200::259",
        "2a05:d014:58f:6200::258"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=31536000; 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=31536000; includeSubDomains; preload",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "2a05:d014:58f:6200::258",
    "family": 6
}
Redirects
{
    "chain": [
        "https://mail-verifications.netlify.app"
    ]
}
Page links
{
    "external": [
        "https://support.google.com/accounts",
        "https://accounts.google.com/TOS",
        "https://accounts.google.com/TOS"
    ],
    "external_count": 3,
    "internal_count": 1
}
HTTP headers
{
    "headers": {
        "server": "Netlify",
        "content-type": "text/html; charset=UTF-8",
        "strict-transport-security": "max-age=31536000; includeSubDomains; preload"
    }
}

Questions about mail-verifications.netlify.app

Is mail-verifications.netlify.app legit?

PhishDestroy records that mail-verifications.netlify.app resolved to a Google search page at capture time, not the Polish verification page its title claims.

Is mail-verifications.netlify.app safe to connect a wallet?

This report does not record which wallet requests mail-verifications.netlify.app 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 mail-verifications.netlify.app?

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

Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 7 captures

Cloudflare Radar 1 / 7 Used in the analysis Source file SHA-256: 52da40c6ec67ee5b407f27bd1f9b163832b50808f8b83fbfb48171c4b4186509 SHA-256 of the prepared copy given to the model: 692f6b72f2fdfdf874475b789c4dfeb9f2fac2f38e02fcd962938bff7722d551
SourceCloudflare Radar
Recorded
StateStored capture
HTTP status200
Final URLhttps://www.google.com/
Position1 / 7
Open capture Source Report Wayback Download
All capture links and hashes (7)

Domain details

Domain
IP Context Germany35.157.26.135 Netlify shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider Netlify US(US)
Abuse contactabuse@netlify.com
Hosting abuse contact abuse@netlify.com Amazon.com, Inc. · AS16509
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 31, 2026
DOM Analysisanalyzed Oct 31, 2026score 45/1001 brand signal
Submitted URLhttp://mail-verifications.netlify.app/
Favicon Hash
Observed page title
Weryfikacja dwuetapowa Aby chronić Twoje konto, musimy mieć pewność, że to naprawdę Ty próbujesz się zalogować
Automated brand references
Google
TLS Certificate
Issued by DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1 · stored validity ends in 139 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Germany35.157.26.135
Network ASN
AS16509
Organization
Amazon.com, Inc.
Observed location
GermanyFrankfurt, DE
Server header
Netlify

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

TLS certificate

Issuer
DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1
Valid from
2026-02-16 00:00:00
Valid until
2027-03-19 23:59:59
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintbc3a8134c21a842e64ea34d488826dd2ba50f59a3bcbaed1e6b71a4242de1478
Certificate names · 2 SANs
  • *.netlify.app
  • netlify.app

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

viewdns.info · 35.157.26.135rapiddns.io
Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

17 / 92 security vendors flagged this domain
View on VT
Last analyzed
alphaMountain.ai
BitDefender
DNS8
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
Netcraft
Seclookup
SOCRadar
Sophos
VIPRE
Webroot
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of mail-verifications.netlify.app · checked Oct 31, 2026

98
Good
Performance
FCP
1.89 s
First Contentful Paint
LCP
1.9 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
1.89 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
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://mail-verifications.netlify.app/
Final URL: https://mail-verifications.netlify.app/
Weryfikacja dwuetapowa Aby chronić Twoje konto, musimy mieć pewność, że to naprawdę Ty próbujesz się zalogować
Response
HTTP 200
HTML body
431.9 KB
Compressed
202.7 KB
Links
1 internal · 3 external
Detected technologies
vue
Selected response headers
Cache-Control: public,max-age=0,must-revalidate
Content-Encoding: gzip
Content-Type: text/html; charset=UTF-8
Server: Netlify
Security headers present
Strict-Transport-Security
HSTS: observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 13
Accept-Ranges
bytes
Age
0
Cache-Control
public,max-age=0,must-revalidate
Cache-Status
"Netlify Edge"; fwd=miss; fwd-status=200; stored
Content-Encoding
gzip
Content-Type
text/html; charset=UTF-8
Date
Sat, 31 Oct 2026 12:31:02 GMT
Etag
"c747631a9827a8d67fc4dcb9bdc461d5-ssl-df"
Server
Netlify
Strict-Transport-Security
max-age=31536000; includeSubDomains; preload
Transfer-Encoding
chunked
Vary
Accept-Encoding
X-Nf-Request-Id
01M68Z29HSMXACM5BXGNS4VE9E

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

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

Captured network requests

Network requests: 3 SHA-256 hashes: 3 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-31 12:41 UTC.

Open this scan on URLScan 01a191f6-0134-75fd-a595-f2779ca87ad1 ↗

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. Domain monitor · First collection record

    Reachable

All retained availability observations3

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_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-31 13:38:07.000000
    Evidence SHA-256
    7c14ebaea8167f86312396ef4fa6d57c24a451338d32856008011bf713edd919
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 13:38:07
    Evidence reason
  2. 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-31 13:38:07.000000
    Evidence SHA-256
    7c14ebaea8167f86312396ef4fa6d57c24a451338d32856008011bf713edd919
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 13:38:07
    Evidence reason
  3. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 13:32:47.136253
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

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
    mail-verifications.netlify.app detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 6 of 6
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan classified the page as malicious · Score: 100
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • VirusTotal
    Detections recorded on VirusTotal: 17/92
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, 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. URLScan

    Page captured

    View source
  2. Cloudflare Radar

    Phishing

    View source
  3. Added to PhishDestroy

    mail-verifications.netlify.app

    View source
  4. VirusTotal

    17/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.

mail-verifications.netlify.app

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 17 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Open report 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?

3 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 mail-verifications.netlify.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

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.

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.

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/mail-verifications.netlify.app"
  title="PhishDestroy threat report for mail-verifications.netlify.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>