Skip to security report
Analytics Dashboard
Domain security and threat intelligence
headfire.pt favicon

headfire.pt

In short

headfire.pt is a Google impersonation page detected by PhishDestroy on 2026-09-08. Risk: critical (98/100). Status: Reachable · access restricted. Hosting: Cloudflare, Inc. VirusTotal: 15/89 engines flag it. Do not enter credentials or connect a wallet.

“Mon Super Site Web”

Resolved IP
188.114.97.3
Registered
Jun 11, 2026
PhishDestroy assessment Critical
Availability Reachable · access restricted Reachable response; page content was not verified Observed · HTTP probe
Risk signals
VirusTotal detections: 15/89 Automated brand label: Google Last known active
OTX: 5 refs Sep 8, 2026 CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 15. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
15 / 89
engine detections
Google Safe Browsing
No threat flag
OTX
5
community references
Page captures
4
open gallery
Domain age
133 days
Source evidenceVirusTotal 15 / 89 · OTX 5 references 5 sources

VirusTotal

15 / 89 engine detections

Open report

OTX

5 community references

Open report

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

Open report

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

Analysis

Critical
VirusTotal
15 / 89
OTX
5 community refs
Page captures
4
Page captures Source results Registration record

PhishDestroy threat report

Overview

headfire.pt is a Portuguese-domain site that PhishDestroy classifies as an impersonation phishing page. It poses as a legitimate service to get visitors to hand over account details or other sensitive information. We first detected it on 2026-09-08. On 2026-10-19 the site was still online, and its content was reachable but sat behind a protection layer.

How the scam works

Impersonation pages copy the look of a trusted brand or service so that a visitor believes they are on the real site. Victims are then led to type in login credentials, personal details or payment information, and the operator collects it all. The browser tab shows the title "Mon Super Site Web", which is French for "My Super Website" and reads like an unedited site-builder default. That generic title differs from the impersonation behaviour we classified. Anything entered on the page should be treated as being in the operator's hands.

Evidence

On 2026-09-18, VirusTotal showed 15 of 89 engines flagging the domain. The flagging vendors include alphaMountain.ai, BitDefender, CRDF, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data and Gridinsoft. These are separate detection pipelines, so their agreement makes a single false positive unlikely. The domain also appears in 5 AlienVault OTX threat pulses, which shows other researchers have tracked it. Among public blocklists, it is currently listed by PhishDestroy.

Infrastructure

The domain was registered on 2026-06-11, roughly three months before we flagged it. That gap suggests it may have been registered in advance and left dormant before going live. It resolves to Cloudflare's network (188.114.97.3, geolocated to Canada), which hides the origin server behind a shared proxy. The site serves a TLS certificate from Google Trust Services (WE1), so the padlock in the address bar says nothing about whether the site is legitimate.

What to do

If you entered a password on headfire.pt, change it right away on the genuine service and on any other account that uses the same password. Then enable two-factor authentication. If you supplied card or banking details, contact your bank to block the card and watch for unfamiliar charges. Be wary of follow-up emails or calls that cite what you submitted, since stolen details are often reused in further scams. Defenders should block the domain at DNS and proxy level, search logs for visits or form submissions to it, and report it to Cloudflare's abuse channel and the .pt registry.

Useful links

urlscan.io scan and screenshotVirusTotal reportGoogle Safe Browsing statusArchived copyReport phishing to GoogleSite owner? Request a review

Collected source details

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

URLScan · 2026-09-08T18:17:19Z

Observed: · Retrieved:

Uuid
01a0823d-06a9-7718-9dfb-f2e7b9b532df
Final url
https://headfire.pt/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://headfire.pt/",
        "from": "http://headfire.pt/",
        "status": 307
    }
]
Ip
188.114.97.3
Contacted IP addresses
[
    "188.114.97.3"
]
Asns
[
    "13335"
]
Document hash
bdb3551b68520cd16f1f9fc4014fb778b81b93a90094eee4beee304358fa7d19
Tls
{
    "san": [
        "headfire.pt",
        "*.headfire.pt"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WE1",
    "subject": "headfire.pt",
    "protocol": "QUIC",
    "valid_to": "2026-10-31T22:24:33Z",
    "valid_from": "2026-08-02T21:25:51Z"
}
Domain age days
3144
Apex age days
3144
Tls age days
36
Tls valid days
90
Requests
2
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": -59,
        "malicious": false
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html"
}
Cloudflare Radar · 2026-09-08T18:42:06Z

Observed: · Retrieved:

Uuid
a2eb2802-6545-417f-8af0-3063cf1eca49
Final url
https://headfire.pt/
Status
200
Redirected
https-only
History
[
    {
        "url": "http://headfire.pt/",
        "status": 307
    },
    {
        "url": "https://headfire.pt/",
        "status": 200
    }
]
DOM structure hash
5c23845d7ea8049f3410fa331c1478a462dad2c43dd4b1f806196809edad5e37
Document hash
bf59e1a70a3fc729574c2c751d4b2c6449d4912c97c8c1465834343fc47fe86e
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "headfire.pt",
        "type": "A",
        "value": "188.114.96.0"
    },
    {
        "name": "headfire.pt",
        "type": "A",
        "value": "188.114.97.0"
    },
    {
        "name": "headfire.pt",
        "type": "AAAA",
        "value": "2a06:98c1:3121::"
    },
    {
        "name": "headfire.pt",
        "type": "AAAA",
        "value": "2a06:98c1:3120::"
    }
]
Dnssec valid
false
Ip
188.114.96.0
Registration record
{
    "created": "2026-06-11T11:02:19Z",
    "expires": "2027-06-11T11:02:19Z",
    "nameservers": [
        "alec.ns.cloudflare.com",
        "jo.ns.cloudflare.com"
    ]
}

Questions about headfire.pt

Is headfire.pt legit?

No. PhishDestroy classifies headfire.pt as a Google impersonation page (risk: critical, 98/100); it was first detected on 2026-09-08. VirusTotal: 15/89 engines flag it. Treat the site as unsafe.

Is headfire.pt safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on headfire.pt. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used headfire.pt?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 4 captures

Primary capture 1 / 4
SourcePrimary capture
Recorded2026-09-08 18:18 UTC
StateStored capture
Position1 / 4
Open capture Wayback Download

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-09activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
RegistrationCreated Jun 11, 2026 (133d) — Expires Jun 11, 2027
HTTP Status403 Forbidden
Technical detailsProvenance & timestamps
First DetectedSep 8, 2026
DOM Analysisanalyzed Oct 9, 2026score 98/1001 brand signal
Submitted URLhttp://headfire.pt/
Favicon Hash
Observed page title
Mon Super Site Web
Automated brand references
Google
TLS Certificate
Issued by Google Trust Services / WE1 · stored validity ends in 68 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
188.114.97.3
Network ASN
AS13335
Organization
CloudFlare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • alec.ns.cloudflare.com
  • jo.ns.cloudflare.com

Mail routing 1 MX record

  • _dc-mx.494b7200e31c.headfire.ptpriority 0

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-10-01 03:32:26
Valid until
2026-12-30 04:32:21
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-10-10 22:03:53 UTC
Collection source
PhishDestroy collector
Certificate fingerprint5172b7f3720cef52cd170fe0092dfceca59d3f30c1dc89fd2925ae662d4e9c3d
Certificate names · 2 SANs
  • headfire.pt
  • *.headfire.pt

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

viewdns.info · 188.114.97.3rapiddns.io

Latest Classified Outcome 2026-10-22 10:13:35 UTC

Primary outcome Reachable but protected reason: HTTP access restricted 65% confidence
Attribution Cloudflare mechanism: Access Restriction source: Current Http Probe
Evidence layers Availability: Reachable but protected Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Reachable but protected HTTP access restricted Cloudflare Access Restriction 65% 2026-10-22 10:13:35 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-22 10:13:35 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

15 / 89 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 15 detections
alphaMountain.ai
BitDefender
CRDF
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
Seclookup
SOCRadar
Sophos
VIPRE
Webroot

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of headfire.pt · checked Sep 8, 2026

100
Good
Performance
FCP
1.53s
First Contentful Paint
LCP
1.53s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.7s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details2

Availability observations

Last reachable 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.

Check for cloaking

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

Page titles differ

alive_content: raw=content_403; http=403; via=https_proxy; server=cloudflare

Browser
Mon Super Site Web
Crawler
403 Forbidden
headfire.pt
Saved result
Cloaked / Filtered
Stored observation history21

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

    Unknown→protected

    http_access_restricted · Cloudflare · access_restriction

  2. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · Cloudflare · access_restriction

  3. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · Cloudflare · access_restriction

  4. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · Cloudflare · access_restriction

  5. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · Cloudflare · access_restriction

Earlier observations 16
  1. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · Cloudflare · access_restriction

  2. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · Cloudflare · access_restriction

  3. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · Cloudflare · access_restriction

  4. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · Cloudflare · access_restriction

  5. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · Cloudflare · access_restriction

  6. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · Cloudflare · access_restriction

  7. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · Cloudflare · access_restriction

  8. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · Cloudflare · access_restriction

  9. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · Cloudflare · access_restriction

  10. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · Cloudflare · access_restriction

  11. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · Cloudflare · access_restriction

  12. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · Cloudflare · access_restriction

  13. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · Cloudflare · access_restriction

  14. Availability monitor · Recorded state

    protected

    http_access_restricted · Cloudflare · access_restriction

  15. VirusTotal · Detection count

    14→15

  16. Availability monitor · First collection record

    Reachable

Recorded activity

5 entries
  1. AlienVault OTX

    5 community references

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. VirusTotal

    15/89 engine detections

    View source
  4. Added to PhishDestroy

    headfire.pt

    View source
  5. URLScan

    Page captured

    View source

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 15 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Open report OTX 5 refs 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 Archived
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 0 stored notification records Reachable · access restricted

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Immediate steps Find reporting contacts

Official reporting routes

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including headfire.pt)
  • 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

Live Threat Feed Appeal This Listing
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

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/headfire.pt"
  title="PhishDestroy threat report for headfire.pt"
  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>