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

determined-poppy-tempo.heyflow.page

In short

PhishDestroy stores a record for determined-poppy-tempo.heyflow.page. Source observations are dated separately; missing checks do not establish safety.

“interactive-forms”

Review the evidence
Registrar
SwedenNamecheap
Resolved IP
United States34.107.159.201Google LLC
Registered
Oct 23, 2024
First observed
Oct 25, 2026
PhishDestroy assessment Critical
88/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 8/92
VirusTotal
8 / 92
engine detections ·
URLQuery
2
detections
URLScan
Malicious
engine verdict · score 90
Page captures
5
open gallery
Domain age
739 days
registered 2024-10-23 according to WHOIS · source data differ
Oct 25, 2026
X Telegram API

Questions about determined-poppy-tempo.heyflow.page

Is determined-poppy-tempo.heyflow.page legit?

PhishDestroy stores a record for determined-poppy-tempo.heyflow.page. Source observations are dated separately; missing checks do not establish safety.

Is determined-poppy-tempo.heyflow.page safe to connect a wallet?

This report does not record which wallet requests determined-poppy-tempo.heyflow.page 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 determined-poppy-tempo.heyflow.page?

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

Source evidenceVirusTotal 8 / 92 8 sources

VirusTotal

8 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 10 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
53
Malicious
8
Suspicious
0
Undetected
31

Vendor labels

DNS8
phishing
ESET
phishing
VIPRE
phishing
Webroot
malicious
Gridinsoft
phishing
SafeToOpen
phishing
Chong Lua Dao
malicious
alphaMountain.ai
phishing

Reputation score

0

Created

Updated

First seen

DNS records

  • TTL, seconds
    21600
    Type
    NS
    Value
    mark.ns.cloudflare.com
  • TTL, seconds
    21600
    Type
    NS
    Value
    kelly.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    CNAME
    Value
    heyflow.page
  • TTL, seconds
    300
    Type
    A
    Value
    34.107.159.201
  • TTL, seconds
    3600
    Type
    TXT
    Value
    google-site-verification=-F8pU2LXVn-ybVh0phDhriIpuUOLAeIdCHX22-o39Zw
  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    kelly.ns.cloudflare.com

DNS records observed

JARM fingerprint

29d3fd00029d29d00042d43d00041d6f940079659edb62e1c38c38bd26ee84

Certificate

Subject alternative names
  • heyflow.page
  • *.heyflow.page
Issuer
Google Trust Services / WR3
Serial
109b40d093e0fbed099ed05d600fda62
SHA-256
6f2c6c411fbf1831c69c01ad42b2da73530e3394e48f62d4d611c35f952123b6
Subject
heyflow.page
Valid until
Valid from
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 53,
    "malicious": 8,
    "suspicious": 0,
    "undetected": 31
}
Vendor labels
{
    "DNS8": "phishing",
    "ESET": "phishing",
    "VIPRE": "phishing",
    "Webroot": "malicious",
    "Gridinsoft": "phishing",
    "SafeToOpen": "phishing",
    "Chong Lua Dao": "malicious",
    "alphaMountain.ai": "phishing"
}
Reputation
0
Created
2024-10-23T00:00:00Z
Updated
2024-10-23T00:00:00Z
First seen
2026-04-01T07:06:33Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "mark.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "kelly.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "CNAME",
        "value": "heyflow.page"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "34.107.159.201"
    },
    {
        "ttl": 3600,
        "type": "TXT",
        "value": "google-site-verification=-F8pU2LXVn-ybVh0phDhriIpuUOLAeIdCHX22-o39Zw"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "kelly.ns.cloudflare.com"
    }
]
Dns at
2026-10-25T08:00:51Z
Jarm
29d3fd00029d29d00042d43d00041d6f940079659edb62e1c38c38bd26ee84
Certificate
{
    "san": [
        "heyflow.page",
        "*.heyflow.page"
    ],
    "issuer": "Google Trust Services / WR3",
    "serial": "109b40d093e0fbed099ed05d600fda62",
    "sha256": "6f2c6c411fbf1831c69c01ad42b2da73530e3394e48f62d4d611c35f952123b6",
    "subject": "heyflow.page",
    "valid_to": "2027-01-21T07:56:59Z",
    "valid_from": "2026-10-23T07:01:04Z"
}
Separate source record · 8 malicious + 0 suspicious / 92 · 2026-10-25 07:55:31 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-25T07:55:31Z
fetched_at
2026-10-25T08:34:45Z
stats
{"timeout":0,"harmless":53,"malicious":8,"suspicious":0,"undetected":31}

URLScan

Malicious · engine verdict · score 90

SHA-256 c3b5fbf810105278c8b81d9921f3f9d57f02f0421fb313beb21a69f5851bb2e1

Open report
URLScanOriginal source recordObserved: 23 fields

Observed: · Retrieved:

Report ID

01a171ca-38c1-741e-9571-263fff4e3439

Final URL

https://determined-poppy-tempo.heyflow.page/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://determined-poppy-tempo.heyflow.page/
    From
    http://determined-poppy-tempo.heyflow.page/
    Status
    307

IP address

34.107.159.201

Reverse DNS (PTR)

201.159.107.34.bc.googleusercontent.com

Contacted domains

  • assets.prd.heyflow.com
  • api.prd.heyflow.com
  • www.googletagmanager.com
  • www.google-analytics.com
  • functions.prd.heyflow.com
  • res.cloudinary.com
  • fonts.heyflow.cloud

Contacted IP addresses

  • 2a00:1450:4001:c25::8b
  • 2606:4700::6810:4e06
  • 2a00:1450:4001:c25::61
  • 2606:4700:20::681a:f0
  • 34.54.43.41
  • 34.107.159.201

Autonomous systems (ASN)

  • 15169
  • 13335
  • 396982

Server countries

  • DE
  • US

Linked domains

  • heyflow.app
  • get.heyflow.com
  • heyflow.com

Document hash

b42fe11782d28422d63ef5f21039c51b5bb3525a74e88e74f1fe98a059d758fb

JavaScript globals

  • currentlyMounting
  • heyflow
  • onImageLoadError
  • dataLayer
  • gtag
  • windowConstants
  • HEYFLOW_COOKIE_CONSENT_CONFIG
  • __svelte
  • heyflowShowCookieSettings
  • filterCSS
  • filterXSS
  • Client
  • google_tag_data
  • google_tag_manager
  • GoogleAnalyticsObject
  • ga
  • gaplugins
  • onYouTubeIframeAPIReady
  • gaGlobal

Browser storage keys

  • test
  • heyflow-session-id:interactive-forms

TLS session and certificate

Subject alternative names
  • heyflow.page
  • *.heyflow.page
Cipher
AES_128_GCM
Issuer
WR3
Subject
heyflow.page
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

206

Differs from the registration date in WHOIS (2024-10-23), which gives 732 days on the scan date 2026-10-25. The two sources disagree; both values are kept as recorded.

Registered domain age, days

206

Differs from the registration date in WHOIS (2024-10-23), which gives 732 days on the scan date 2026-10-25. The two sources disagree; both values are kept as recorded.

Certificate age, days

1

Certificate validity, days

90

Page requests

38

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
90
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP headers

Server
Google Frontend
Content-type
text/html
Original source fields · JSON
Uuid
01a171ca-38c1-741e-9571-263fff4e3439
Final url
https://determined-poppy-tempo.heyflow.page/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://determined-poppy-tempo.heyflow.page/",
        "from": "http://determined-poppy-tempo.heyflow.page/",
        "status": 307
    }
]
Ip
34.107.159.201
Ptr
201.159.107.34.bc.googleusercontent.com
Contacted domains
[
    "assets.prd.heyflow.com",
    "api.prd.heyflow.com",
    "www.googletagmanager.com",
    "www.google-analytics.com",
    "functions.prd.heyflow.com",
    "res.cloudinary.com",
    "fonts.heyflow.cloud"
]
Contacted IP addresses
[
    "2a00:1450:4001:c25::8b",
    "2606:4700::6810:4e06",
    "2a00:1450:4001:c25::61",
    "2606:4700:20::681a:f0",
    "34.54.43.41",
    "34.107.159.201"
]
Asns
[
    "15169",
    "13335",
    "396982"
]
Countries
[
    "DE",
    "US"
]
Linked domains
[
    "heyflow.app",
    "get.heyflow.com",
    "heyflow.com"
]
Document hash
b42fe11782d28422d63ef5f21039c51b5bb3525a74e88e74f1fe98a059d758fb
Globals
[
    "currentlyMounting",
    "heyflow",
    "onImageLoadError",
    "dataLayer",
    "gtag",
    "windowConstants",
    "HEYFLOW_COOKIE_CONSENT_CONFIG",
    "__svelte",
    "heyflowShowCookieSettings",
    "filterCSS",
    "filterXSS",
    "Client",
    "google_tag_data",
    "google_tag_manager",
    "GoogleAnalyticsObject",
    "ga",
    "gaplugins",
    "onYouTubeIframeAPIReady",
    "gaGlobal"
]
Storage keys
[
    "test",
    "heyflow-session-id:interactive-forms"
]
Tls
{
    "san": [
        "heyflow.page",
        "*.heyflow.page"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WR3",
    "subject": "heyflow.page",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-21T07:56:59Z",
    "valid_from": "2026-10-23T07:01:04Z"
}
Domain age days
206

Differs from the registration date in WHOIS (2024-10-23), which gives 732 days on the scan date 2026-10-25. The two sources disagree; both values are kept as recorded.

Apex age days
206

Differs from the registration date in WHOIS (2024-10-23), which gives 732 days on the scan date 2026-10-25. The two sources disagree; both values are kept as recorded.

Tls age days
1
Tls valid days
90
Requests
38
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 90,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "Google Frontend",
    "content-type": "text/html"
}
Separate monitor record · 2026-10-26 04:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a171ca-38c1-741e-9571-263fff4e3439
score
0
malicious
false
result_at
2026-10-26T04:30:33Z
enriched_at
2026-10-26T09:20:11Z
source_timestamps
{"urlscan_result_at":"2026-10-26 05:30:33","urlscan_enriched_at":"2026-10-26 10:20:11"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

no community references

Open report

Cloudflare Radar

provider verdict: clean

Open report
Cloudflare RadarOriginal source recordObserved: 10 fields

Observed: · Retrieved:

Report ID

9e615e17-0ff1-41f4-9b1a-b025f2cffda9

Final URL

https://determined-poppy-tempo.heyflow.page/

HTTP response

200

Navigation history

  • URL
    https://determined-poppy-tempo.heyflow.page/
    Status
    200

DOM structure hash

da9c05b4d2f52e50622aafc8b0e956998519e3e2c10f4e2198d59dfaae82eeb8

Document hash

b42fe11782d28422d63ef5f21039c51b5bb3525a74e88e74f1fe98a059d758fb

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    determined-poppy-tempo.heyflow.page
    Type
    CNAME
    Value
    heyflow.page
  • Name
    heyflow.page
    Type
    A
    Value
    34.107.159.201

DNSSEC valid

No

IP address

34.107.159.201
Original source fields · JSON
Uuid
9e615e17-0ff1-41f4-9b1a-b025f2cffda9
Final url
https://determined-poppy-tempo.heyflow.page/
Status
200
History
[
    {
        "url": "https://determined-poppy-tempo.heyflow.page/",
        "status": 200
    }
]
DOM structure hash
da9c05b4d2f52e50622aafc8b0e956998519e3e2c10f4e2198d59dfaae82eeb8
Document hash
b42fe11782d28422d63ef5f21039c51b5bb3525a74e88e74f1fe98a059d758fb
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "determined-poppy-tempo.heyflow.page",
        "type": "CNAME",
        "value": "heyflow.page"
    },
    {
        "name": "heyflow.page",
        "type": "A",
        "value": "34.107.159.201"
    }
]
Dnssec valid
false
Ip
34.107.159.201

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

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

Open report
Separate monitor score · 10 / 100 · 2026-10-25T07:20:24Z

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

record_source
domain_monitor.dom_analysis
heuristic_score
10
analyzed_at
2026-10-25T07:20:24Z
source_timestamp
2026-10-25 08:20:24
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

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

Domain
determined-poppy-tempo.heyflow.page

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
0
Archived days
1
Average page size, bytes
19720

Page title and metadata

Page title
interactive-forms
Open Graph type
website
Indexing directives
noindex
Open Graph image
https://assets.prd.heyflow.com/builder/meta-image/default.png
Open Graph title
interactive-forms
Twitter card
summary_large_image
Open Graph description
Built with Heyflow

Trackers

Requests
24
Observed services
  • Name
    Google Tag
    Company
    Google
    Country
    US
    Category
    Advertising
    Requests
    1
  • Name
    Cloudinary
    Company
    Cloudinary
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    Google Tag Manager
    Company
    Google
    Country
    US
    Category
    Utilities
    Requests
    1

Forms and mixed content

Scripts without SRI
  • https://assets.prd.heyflow.com/flows/interactive-forms/www/dist/vendor.chunk-MGqacwoL.js
  • https://assets.prd.heyflow.com/flows/interactive-forms/www/dist/flow-CwXKpuZ_.js
  • https://assets.prd.heyflow.com/builder/cookie-consent/latest/bundle-latest.js
  • https://assets.prd.heyflow.com/flows/interactive-forms/www/dist/custom-code-YjRmMDY0.js
Third-party scripts
4

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
59
TLS
21
Waiting
21
Connection
10
Download
4
Response time, ms
115

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443

Carbon estimate

Bytes
188934
CO₂, grams
0.0069
Cleaner than, %
8

DNS servers

Nameservers
  • IP address
    172.64.33.130
    Host
    mark.ns.cloudflare.com
  • IP address
    172.64.34.91
    Host
    kelly.ns.cloudflare.com
DNS zone
heyflow.page

Location

IP address
34.107.159.201
ASN
396982
Organization
Google LLC
City
Kansas City
Country
US

TLS certificate

Issuer
Google Trust Services / WR3
Subject
heyflow.page

DNS records

A
  • 34.107.159.201
NS
  • kelly.ns.cloudflare.com
  • mark.ns.cloudflare.com
SOA
Primary nameserver
kelly.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2417790553
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800
TXT
  • google-site-verification=-F8pU2LXVn-ybVh0phDhriIpuUOLAeIdCHX22-o39Zw
CNAME
  • heyflow.page

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

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
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
34.107.159.201
IP version
4

Redirects

Redirect chain
  • https://determined-poppy-tempo.heyflow.page

Page links

External link addresses
  • https://heyflow.app/legal/imprint
  • https://heyflow.app/legal/imprinthttps://heyflow.app/legal/data-privacy
  • https://get.heyflow.com/report-abuse
External links
3

HTTP headers

Response headers
Server
Google Frontend
Content-type
text/html
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "determined-poppy-tempo.heyflow.page"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-10-25T06:43:07Z",
    "first": "2026-10-25T06:43:07Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 19720
}
Page title and metadata
{
    "title": "interactive-forms",
    "ogType": "website",
    "robots": "noindex",
    "ogImage": "https://assets.prd.heyflow.com/builder/meta-image/default.png",
    "ogTitle": "interactive-forms",
    "twitterCard": "summary_large_image",
    "ogDescription": "Built with Heyflow"
}
Trackers
{
    "requests": 24,
    "trackers": [
        {
            "name": "Google Tag",
            "company": "Google",
            "country": "US",
            "category": "Advertising",
            "requests": 1
        },
        {
            "name": "Cloudinary",
            "company": "Cloudinary",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        },
        {
            "name": "Google Tag Manager",
            "company": "Google",
            "country": "US",
            "category": "Utilities",
            "requests": 1
        }
    ]
}
Forms and mixed content
{
    "no_sri": [
        "https://assets.prd.heyflow.com/flows/interactive-forms/www/dist/vendor.chunk-MGqacwoL.js",
        "https://assets.prd.heyflow.com/flows/interactive-forms/www/dist/flow-CwXKpuZ_.js",
        "https://assets.prd.heyflow.com/builder/cookie-consent/latest/bundle-latest.js",
        "https://assets.prd.heyflow.com/flows/interactive-forms/www/dist/custom-code-YjRmMDY0.js"
    ],
    "third_party_scripts": 4
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 59,
        "tls": 21,
        "wait": 21,
        "connect": 10,
        "download": 4
    },
    "response_ms": 115
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Carbon
{
    "bytes": 188934,
    "co2_grams": 0.0069,
    "cleaner_than": 8
}
Dns server
{
    "ns": [
        {
            "ip": "172.64.33.130",
            "host": "mark.ns.cloudflare.com"
        },
        {
            "ip": "172.64.34.91",
            "host": "kelly.ns.cloudflare.com"
        }
    ],
    "zone": "heyflow.page"
}
Location
{
    "ip": "34.107.159.201",
    "asn": "396982",
    "org": "Google LLC",
    "city": "Kansas City",
    "country": "US"
}
Ssl
{
    "issuer": "Google Trust Services / WR3",
    "subject": "heyflow.page"
}
DNS records
{
    "A": [
        "34.107.159.201"
    ],
    "NS": [
        "kelly.ns.cloudflare.com",
        "mark.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"kelly.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2417790553, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}",
    "TXT": [
        "google-site-verification=-F8pU2LXVn-ybVh0phDhriIpuUOLAeIdCHX22-o39Zw"
    ],
    "CNAME": [
        "heyflow.page"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "34.107.159.201",
    "family": 4
}
Redirects
{
    "chain": [
        "https://determined-poppy-tempo.heyflow.page"
    ]
}
Page links
{
    "external": [
        "https://heyflow.app/legal/imprint",
        "https://heyflow.app/legal/imprinthttps://heyflow.app/legal/data-privacy",
        "https://get.heyflow.com/report-abuse"
    ],
    "external_count": 3
}
HTTP headers
{
    "headers": {
        "server": "Google Frontend",
        "content-type": "text/html"
    }
}
Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 5 captures

Primary capture 1 / 5
SourcePrimary capture
Recorded
StateStored capture
Position1 / 5
Open capture Wayback Download
All capture links and hashes (5)
Observed page title
interactive-forms
Automated brand references
WhatsApp
TLS Certificate
Issued by WR3 · stored validity ends in 81 days
determined-poppy-tempo.heyflow.page: caution — 8/92 VirusTotal engines. PhishDestroy risk score 88/100 (critical).
Social preview card determined-poppy-tempo.heyflow.page: caution — 8/92 VirusTotal engines. PhishDestroy risk score 88/100 (critical). v 6e01f4858330

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 90 report ↗
IP Reputation United States34.107.159.201 abuse score 0/100 0 reports checked Oct 25, 2026
Registrar (base domain) Namecheap SE(SE)
Abuse contact["5d0020a4748f3125s@"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for heyflow.page →
Registration (base domain)heyflow.page · Created Oct 23, 2024 — Expires Oct 23, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 25, 2026
DOM Analysisanalyzed Oct 25, 2026score 10/1001 brand signal
Submitted URLhttp://determined-poppy-tempo.heyflow.page/
Favicon Hash
ICANN OVERSIGHT Registration: heyflow.page

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For the registrable domain heyflow.page behind this subdomain, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.

Accreditation is a contract, not a safety seal. Verify ICANN fees Read RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
United States34.107.159.201
Network ASN
AS396982
AS name
GOOGLE-CLOUD-PLATFORM - Google LLC, US
Organization
Google LLC
Observed location
United StatesKansas City, US
Server header
Google Frontend

Nameservers 2

  • kelly.ns.cloudflare.com
  • mark.ns.cloudflare.com

SOA

  • nsname: kelly.ns.cloudflare.com
  • hostmaster: dns.cloudflare.com
  • serial: 2417790553
  • refresh: 10000
  • retry: 2400
  • expire: 604800
  • minttl: 1800

Location describes the IP network.

TLS certificate

Issuer
WR3
Valid from
2026-10-23 07:01:04
Valid until
2027-01-21 07:56:59
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint1d652ffb285dc6ffaf57dea8684d824684c286b505be2a782265c1a1117c6006
Certificate names · 2 SANs
  • heyflow.page
  • *.heyflow.page

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

viewdns.info · 34.107.159.201rapiddns.io

Latest Classified Outcome 2026-11-01 03:37:30 UTC

The site was serving its pages at the latest check.

Technical details
Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-11-01 03:37:30 UTC
RDAP registration
Observed timeline last reachable: 2026-11-01 03:37:30 UTC last content: 2026-11-01 03:37:30 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 · 4 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

8 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 8 detections
alphaMountain.ai
Chong Lua Dao
DNS8
ESET
Gridinsoft
SafeToOpen
VIPRE
Webroot

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of determined-poppy-tempo.heyflow.page · checked Oct 25, 2026

62
Needs Work
Performance
FCP
3.32 s
First Contentful Paint
LCP
7.98 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
270 ms
Total Blocking Time
SI
3.91 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://determined-poppy-tempo.heyflow.page/
Final URL: https://determined-poppy-tempo.heyflow.page/
interactive-forms
Response
HTTP 200
HTML body
184.5 KB
Compressed
18.3 KB
Links
0 internal · 3 external
Detected technologies
react
Selected response headers
Content-Type: text/html
Content-Encoding: gzip
Server: Google Frontend
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Favicon fingerprint: 02f00e150ba2faf3bf9b73640304b2cccaaa076b28a2dfefb42855c668805c10
Open Graph title: interactive-forms
Open Graph description: Built with Heyflow
Twitter card: summary_large_image
Saved response-header values · 9
Access-Control-Allow-Origin
*
Alt-Svc
h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
Content-Encoding
gzip
Content-Type
text/html
Date
Sun, 25 Oct 2026 06:42:44 GMT
Server
Google Frontend
Transfer-Encoding
chunked
Vary
Accept-Encoding
Via
1.1 google

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

Archived
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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: 38 SHA-256 hashes: 37 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-29 01:58 UTC.

Open this scan on URLScan 01a171ca-38c1-741e-9571-263fff4e3439 ↗

Stored observation history5

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

  1. Availability monitor · Recorded state

    live_content

    content_served

  2. Availability monitor · Recorded state

    live_content

    content_served

  3. Availability monitor · Recorded state

    live_content

    content_served

  4. Availability monitor · Recorded state

    live_content

    content_served

  5. Domain monitor · First collection record

    Reachable

All retained availability observations35

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_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 04:37:30.000000
    Evidence SHA-256
    bf9b99363a05bc5885301341c1162851b0698ac42c7580aa5b46118e00270f00
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 04:37:30
    Evidence reason
    alive_content
  2. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 04:37:30.000000
    Evidence SHA-256
    bf9b99363a05bc5885301341c1162851b0698ac42c7580aa5b46118e00270f00
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 04:37:30
    Evidence reason
    alive_content
  3. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:49:10.000000
    Evidence SHA-256
    0d21da18950a35ca1f664df54ca5a3ff93145a62ce98618a26333e4acd8ea719
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:49:10
    Evidence reason
    alive_content
  4. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:49:10.000000
    Evidence SHA-256
    0d21da18950a35ca1f664df54ca5a3ff93145a62ce98618a26333e4acd8ea719
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:49:10
    Evidence reason
    alive_content
  5. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 11:20:09.112163
    Evidence SHA-256
    b5c6551e799cfe4d3cb298004536f14652a7bd27158039d9a8bde93b0611124a
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 11:20:09.112163
    Evidence reason
  6. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 04:30:29.000000
    Evidence SHA-256
    3faa077c50866093da2c7f58f803eaa964c8409494449950f55104132c956521
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 04:30:29
    Evidence reason
    alive_content
  7. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 04:30:29.000000
    Evidence SHA-256
    3faa077c50866093da2c7f58f803eaa964c8409494449950f55104132c956521
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 04:30:29
    Evidence reason
    alive_content
  8. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 00:45:45.000000
    Evidence SHA-256
    43258d6fa1d01dd8cf6d66fd987f105bab430aa4939eee03273b6a48a505db94
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 00:45:45
    Evidence reason
    alive_content
  9. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 00:45:45.000000
    Evidence SHA-256
    43258d6fa1d01dd8cf6d66fd987f105bab430aa4939eee03273b6a48a505db94
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 00:45:45
    Evidence reason
    alive_content
  10. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:54:02.000000
    Evidence SHA-256
    1e864114c89c2eac40285ab02436020b0f3fb0f96d8adcb34282ad1cf6a6325d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 12:54:02
    Evidence reason
    alive_content
  11. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:54:02.000000
    Evidence SHA-256
    1e864114c89c2eac40285ab02436020b0f3fb0f96d8adcb34282ad1cf6a6325d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 12:54:02
    Evidence reason
    alive_content
  12. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 05:03:05.462458
    Evidence SHA-256
    bbc8a7612fad967fe6394ef6e3533c42adb354b0403e4f596ca1b553348f1852
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 05:03:05.462458
    Evidence reason
  13. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:53:10.000000
    Evidence SHA-256
    366ec1ffed41ee094f8c9a635caa2ccef374a4b40c97c11ee7628f878be63e6f
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:53:10
    Evidence reason
    alive_content
  14. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:53:10.000000
    Evidence SHA-256
    366ec1ffed41ee094f8c9a635caa2ccef374a4b40c97c11ee7628f878be63e6f
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:53:10
    Evidence reason
    alive_content
  15. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 12:52:05.000000
    Evidence SHA-256
    c249ebf3cb053041a3a477ca7f83b21efc6c559d565eba771525fae43e3c6308
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:52:05
    Evidence reason
    alive_content
  16. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 12:52:05.000000
    Evidence SHA-256
    c249ebf3cb053041a3a477ca7f83b21efc6c559d565eba771525fae43e3c6308
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:52:05
    Evidence reason
    alive_content
  17. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 04:28:04.000000
    Evidence SHA-256
    099368532efed886e9ecd4ae1e62d86a59c02caa12b25d4a7008918f859cfd54
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 04:28:04
    Evidence reason
    alive_content
  18. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 04:28:04.000000
    Evidence SHA-256
    099368532efed886e9ecd4ae1e62d86a59c02caa12b25d4a7008918f859cfd54
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 04:28:04
    Evidence reason
    alive_content
  19. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 00:01:18.000000
    Evidence SHA-256
    2a1cfb066e087dba17591e393bdf5152e9d7ced4376a50e8fd09d44eb0d0b715
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 00:01:18
    Evidence reason
    alive_content
  20. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 00:01:18.000000
    Evidence SHA-256
    2a1cfb066e087dba17591e393bdf5152e9d7ced4376a50e8fd09d44eb0d0b715
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 00:01:18
    Evidence reason
    alive_content
  21. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 17:03:14.895165
    Evidence SHA-256
    73d1f345e73e3fe3ec20cf30f9fc86221ba9885e7af8cdcc18189657c73b0d4e
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-28 17:03:14.895165
    Evidence reason
  22. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 12:01:57.000000
    Evidence SHA-256
    446b2e669cbc0c4b6160201570c3ca7246e2e77b041d6deec381977f0b349ef2
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 12:01:57
    Evidence reason
    alive_content
  23. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 12:01:57.000000
    Evidence SHA-256
    446b2e669cbc0c4b6160201570c3ca7246e2e77b041d6deec381977f0b349ef2
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 12:01:57
    Evidence reason
    alive_content
  24. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 00:02:28.000000
    Evidence SHA-256
    633689ba49ddc610fe1eb522be9a4dcacb9466fcb1cdcdcec9d8ed8ca746c7f5
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 00:02:28
    Evidence reason
    alive_content
  25. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 00:02:28.000000
    Evidence SHA-256
    633689ba49ddc610fe1eb522be9a4dcacb9466fcb1cdcdcec9d8ed8ca746c7f5
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 00:02:28
    Evidence reason
    alive_content
  26. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:02:50.000000
    Evidence SHA-256
    eacf1829ec6af9360ab8985188c8dc6f86d16b067c1868e75e03e3285c8764b6
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 12:02:50
    Evidence reason
    alive_content
  27. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:02:50.000000
    Evidence SHA-256
    eacf1829ec6af9360ab8985188c8dc6f86d16b067c1868e75e03e3285c8764b6
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 12:02:50
    Evidence reason
    alive_content
  28. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 13:02:20.000000
    Evidence SHA-256
    8fb1aa660749f2c6ea54c3336b27b7bbb396343eed16718e7d119acc6c9a1af3
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 13:02:20
    Evidence reason
    alive_content
  29. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 13:02:20.000000
    Evidence SHA-256
    8fb1aa660749f2c6ea54c3336b27b7bbb396343eed16718e7d119acc6c9a1af3
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 13:02:20
    Evidence reason
    alive_content
  30. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 01:19:18.000000
    Evidence SHA-256
    bfd852f77d31672218578536adceaeb8034a4d65582bae3d83f0dadbe7f148f8
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 01:19:18
    Evidence reason
    alive_content
  31. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 01:19:18.000000
    Evidence SHA-256
    bfd852f77d31672218578536adceaeb8034a4d65582bae3d83f0dadbe7f148f8
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 01:19:18
    Evidence reason
    alive_content
  32. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 13:22:50.000000
    Evidence SHA-256
    b3c84488af12a523b8609e2f9bc8fe272141497ebb2ba787ef9034becbbedba8
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 13:22:50
    Evidence reason
    alive_content
  33. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 13:22:50.000000
    Evidence SHA-256
    b3c84488af12a523b8609e2f9bc8fe272141497ebb2ba787ef9034becbbedba8
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 13:22:50
    Evidence reason
    alive_content
  34. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 07:41:45.000000
    Evidence SHA-256
    6f5ef0c0c068899d02e436d30579dc3fa44bcdc57663fb2ad085aaa34834939c
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 07:41:45
    Evidence reason
  35. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 07:41:45.000000
    Evidence SHA-256
    6f5ef0c0c068899d02e436d30579dc3fa44bcdc57663fb2ad085aaa34834939c
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 07:41:45
    Evidence reason

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · in progress

Recorded events: 9. 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
    determined-poppy-tempo.heyflow.page detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 7 of 7
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 90
  • 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.
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 8/92
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, URLQuery, 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. VirusTotal

    8/92 engine detections

    View source
  2. Wayback Machine

    Page archived

    View source
  3. Added to PhishDestroy

    determined-poppy-tempo.heyflow.page

    View source
  4. URLScan

    Page captured

    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.

determined-poppy-tempo.heyflow.page

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 8 det. ChainPatrol URLQuery 2 det. 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?

4 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 determined-poppy-tempo.heyflow.page)
  • 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.

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/determined-poppy-tempo.heyflow.page"
  title="PhishDestroy threat report for determined-poppy-tempo.heyflow.page"
  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>