Skip to security report
Domain security and threat intelligence
olympushorse.com.br favicon

olympushorse.com.br

In short

olympushorse.com.br is an Ar24 impersonation page detected by PhishDestroy on 2026-10-21. Risk: high (65/100). Status: Last known active. Hosting: WEBSITEWELCOME.COM. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.

“Olympus Horse”

Resolved IP
50.116.87.118
Registered
Oct 8, 2020
PhishDestroy assessment High
Availability Last known active Latest stored reachability observation Observed · HTTP probe
Spamhaus DBL: DBL_ABUSED_PHISH Automated brand label: Ar24
Oct 21, 2026
API
This domain has been flagged as malicious
PhishDestroy forensic analysis flagged this domain. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
engine detections
Google Safe Browsing
Page captures
open gallery
Domain age
Source evidenceVirusTotal 0 / 92 6 sources

Spamhaus DBL

DBL_ABUSED_PHISH

VirusTotal

0 / 92 engine detections

Open report

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

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

Analysis

High
VirusTotal
0 / 92
Page captures
5

PhishDestroy threat report

Overview

PhishDestroy’s intake AI flagged olympushorse.com.br because a fresh URLScan scan returned a malicious verdict and the AI assigned a high confidence of phishing. The prior assessment indicated that the site appears to impersonate the French electronic registered‑mail service AR24 and would present a login page to capture user credentials, although no page content was captured. The domain was first seen by PhishDestroy on 2026-10-21, when an HTTP 200 response from www.olympushorse.com.br was recorded.

How the scam works

In a typical AR24 phishing campaign the attacker hosts a look‑alike login page that asks for the victim’s email address and password. Submitted credentials are then harvested and can be used to access the mailbox or to launch further social‑engineering attacks.

Evidence

URLScan’s analysis on 2026-10-21 gave the page a malicious overall score of 100, categorized it as phishing and flagged the AR24 brand. VirusTotal checked the domain on 2026-10-21 with 92 engines and reported zero detections and zero suspicious findings. Google Safe Browsing checked the URL on 2026-10-21 and did not flag it. The external OpenPhish list included the domain, and PhishDestroy’s internal blocklist also contains it; OTX showed no pulses on the same date.

Infrastructure

The domain was created 1854 days ago and resolves to 50.116.87.118, an address owned by WEBSITEWELCOME.COM in Brazil. TLS is provided by a Let’s Encrypt certificate issued on 2026-10-06 for *.olympushorse.com.br and valid until 2027-01-04. Nameservers are ns1.agenciaintegracao.com.br and ns2.agenciaintegracao.com.br, with an MX record pointing to mail.olympushorse.com.br and an SPF record that includes websitewelcome.com; DNSSEC is not enabled.

What to do

Anyone who may have entered AR24 credentials on this site should change their AR24 password immediately and enable any available two‑factor authentication. Organizations should block olympushorse.com.br at the network perimeter and monitor logs for connections to that host. Continue to watch for related indicators, as the lack of detections on VirusTotal does not guarantee safety.

Collected source details

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

URLScan · 2026-10-21T14:31:10Z

Observed: · Retrieved:

Uuid
01a15edf-3d99-72b9-8865-44353848386d
Final url
https://olympushorse.com.br/dolo/ar24/
Status
200
Ip
50.116.87.118
Ptr
50-116-87-118.unifiedlayer.com
Contacted IP addresses
[
    "50.116.87.118"
]
Asns
[
    "31898"
]
Countries
[
    "BR"
]
Document hash
100731bbf748f569ef6a9c321cb60696879c5d6d4d194d00b9cb7e3a51a67626
Cookies
[
    "PHPSESSID"
]
Tls
{
    "san": [
        "*.olympushorse.com.br",
        "olympushorse.com.br"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "YR2",
    "subject": "*.olympushorse.com.br",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-04T03:21:42Z",
    "valid_from": "2026-10-06T03:21:43Z"
}
Domain age days
1854
Apex age days
1854
Tls age days
15
Tls valid days
89
Requests
10
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 68,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "ar24"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "AR24"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "Apache",
    "content-type": "text/html; charset=UTF-8"
}
Cloudflare Radar · 2026-10-21T15:31:19Z

Observed: · Retrieved:

Uuid
2c66e1f9-279b-443e-91d6-5ce9fe39ecd4
Final url
https://olympushorse.com.br/
Status
200
History
[
    {
        "url": "https://olympushorse.com.br/",
        "status": 200
    }
]
DOM structure hash
f9d62b36d18d95b9467d80b0e44da36661e7db6feb993947f5dafd9971c324cf
Document hash
44aa1d1cc607394c12746892f759658f679b236f731c9f9a75f4106c388ac652
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "olympushorse.com.br",
        "type": "A",
        "value": "50.116.87.118"
    }
]
Dnssec valid
false
Ip
50.116.87.118
Registration record
{
    "created": "2020-10-08T00:00:00Z",
    "updated": "2025-12-04T00:00:00Z",
    "expires": "2027-10-08T00:00:00Z",
    "nameservers": [
        "ns222.prodns.com.br",
        "ns223.prodns.com.br"
    ]
}
VirusTotal · 2026-10-21T08:04:32Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 55,
    "malicious": 0,
    "suspicious": 0,
    "undetected": 37
}
Reputation
0
Expires
2027-10-08T00:00:00Z
First seen
2025-11-01T04:22:02Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns2.agenciaintegracao.com.br"
    },
    {
        "ttl": 14400,
        "type": "A",
        "value": "50.116.87.118"
    },
    {
        "ttl": 14400,
        "type": "MX",
        "value": "mail.olympushorse.com.br",
        "priority": 0
    },
    {
        "ttl": 21600,
        "type": "SOA",
        "rname": "financeiro.integracaodigital.com.br",
        "value": "ns1.agenciaintegracao.com.br"
    },
    {
        "ttl": 14400,
        "type": "TXT",
        "value": "v=spf1 a mx include:websitewelcome.com ~all"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns1.agenciaintegracao.com.br"
    }
]
Dns at
2026-10-21T08:05:03Z
Jarm
29d29d15d29d29d00042d42d000000cd600c085f371f8533aaf66051f8e5b1
Certificate
{
    "san": [
        "*.olympushorse.com.br",
        "olympushorse.com.br"
    ],
    "issuer": "Let's Encrypt / YR2",
    "serial": "662cf0136062bdaddade42a2107e1c51c7d",
    "sha256": "e0cba37c30adb4abdfb606402e29ec62a3cff6b314c9449ccd672cff5f31f513",
    "subject": "*.olympushorse.com.br",
    "valid_to": "2027-01-04T03:21:42Z",
    "valid_from": "2026-10-06T03:21:43Z"
}
Website checks · 2026-10-21T15:36:53Z
Mail configuration
{
    "mx": [
        "mail.olympushorse.com.br"
    ],
    "spf": "v=spf1 a mx include:websitewelcome.com ~all",
    "dkim": [
        "default"
    ],
    "dkim_bits": 2048,
    "spf_lookups": 10
}
Caa records
{
    "domain": "olympushorse.com.br"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-10-21T15:32:58Z",
    "first": "2021-12-19T21:56:03Z",
    "changes": 8,
    "days_archived": 11,
    "scans_per_day": 0.01,
    "avg_page_bytes": 4135
}
Page title and metadata
{
    "title": "Olympus Horse",
    "ogImage": "assets/images/index-meta.jpg",
    "twitterCard": "summary_large_image"
}
Trackers
{
    "requests": 57,
    "trackers": [
        {
            "name": "Facebook",
            "company": "Meta",
            "country": "US",
            "category": "Advertising",
            "requests": 4
        },
        {
            "name": "Facebook Custom Audience",
            "company": "Meta",
            "country": "US",
            "category": "Advertising",
            "requests": 1
        },
        {
            "name": "Google Tag",
            "company": "Google",
            "country": "US",
            "category": "Advertising",
            "requests": 2
        },
        {
            "name": "Bootstrap CDN",
            "company": "BootstrapCDN",
            "country": "US",
            "category": "Hosting",
            "requests": 2
        },
        {
            "name": "Google Fonts",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 3
        },
        {
            "name": "Google Static",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 4
        },
        {
            "name": "Facebook Connect",
            "company": "Meta",
            "country": "US",
            "category": "Site Analytics",
            "requests": 3
        },
        {
            "name": "Google Analytics",
            "company": "Google",
            "country": "US",
            "category": "Site Analytics",
            "requests": 3
        },
        {
            "name": "Google Tag Manager",
            "company": "Google",
            "country": "US",
            "category": "Utilities",
            "requests": 1
        }
    ]
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 2,
        "tls": 201,
        "wait": 197,
        "connect": 195,
        "download": 207
    },
    "response_ms": 802
}
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": [
        21,
        22,
        25,
        53,
        80,
        110,
        143,
        443,
        587,
        993,
        995,
        3306
    ]
}
Carbon
{
    "bytes": 25523,
    "co2_grams": 0.0009,
    "cleaner_than": 51
}
Dns server
{
    "ns": [
        {
            "ip": "50.116.87.117",
            "host": "ns2.agenciaintegracao.com.br"
        },
        {
            "ip": "50.116.87.116",
            "host": "ns1.agenciaintegracao.com.br"
        }
    ],
    "zone": "olympushorse.com.br"
}
Cookies
{
    "cookies": [
        {
            "name": "_ga"
        },
        {
            "name": "_gid"
        },
        {
            "name": "_gat_UA-117619599-53"
        },
        {
            "name": "_fbp",
            "same_site": "Lax"
        },
        {
            "name": "_ga_LZX6VN3RRT"
        }
    ]
}
Location
{
    "ip": "50.116.87.118",
    "asn": "31898",
    "org": "WEBSITEWELCOME.COM",
    "city": "Vinhedo",
    "country": "BR"
}
Ssl
{
    "issuer": "Let's Encrypt / YR2",
    "subject": "*.olympushorse.com.br"
}
DNS records
{
    "A": [
        "50.116.87.118"
    ],
    "MX": [
        "{\"exchange\": \"mail.olympushorse.com.br\", \"priority\": 0}"
    ],
    "NS": [
        "ns1.agenciaintegracao.com.br",
        "ns2.agenciaintegracao.com.br"
    ],
    "SOA": "{\"nsname\": \"ns1.agenciaintegracao.com.br\", \"hostmaster\": \"financeiro.integracaodigital.com.br\", \"serial\": 2026100601, \"refresh\": 86400, \"retry\": 7200, \"expire\": 3600000, \"minttl\": 86400}",
    "TXT": [
        "v=spf1 a mx include:websitewelcome.com ~all"
    ]
}
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": "50.116.87.118",
    "family": 4
}
Redirects
{
    "chain": [
        "https://olympushorse.com.br"
    ]
}
Tech stack
{
    "technologies": [
        "Bootstrap",
        "Animate.css",
        "Apache HTTP Server",
        "Google Tag Manager",
        "jQuery",
        "Google Analytics",
        "Facebook Pixel",
        "core-js",
        "WhatsApp Business Chat",
        "Google Font API",
        "Popper",
        "Open Graph"
    ]
}
Page links
{
    "external": [
        "https://www.facebook.com/olympushorse",
        "https://www.instagram.com/olympushorsebr/",
        "https://br.pinterest.com/mktolympushorse0174",
        "https://olympushopbr.com.br/",
        "https://www.integracaodigital.com.br/n/",
        "https://api.whatsapp.com/send",
        "https://mobirise.site/"
    ],
    "external_count": 7,
    "internal_count": 9
}
Registration record
{
    "created": "2020-10-08T00:00:00Z",
    "expires": "2027-10-08T00:00:00Z",
    "status": [
        "published"
    ],
    "nameservers": [
        "ns222.prodns.com.br",
        "ns223.prodns.com.br"
    ]
}
HTTP headers
{
    "headers": {
        "server": "Apache",
        "content-type": "text/html"
    }
}

Questions about olympushorse.com.br

Is olympushorse.com.br legit?

No. PhishDestroy classifies olympushorse.com.br as an Ar24 impersonation page (risk: high, 65/100); it was first detected on 2026-10-21. Listed on Spamhaus DBL. Treat the site as unsafe.

Is olympushorse.com.br safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on olympushorse.com.br. 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 olympushorse.com.br?

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 · 5 captures

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Ar24 report ↗
IP Reputation abuse score 0/100 0 reports checked Oct 21, 2026
RegistrationCreated Oct 8, 2020 — Expires Oct 8, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 21, 2026
DOM Analysisanalyzed Oct 21, 2026score 63/1001 brand signal
Submitted URLhttp://olympushorse.com.br/dolo/ar24
Favicon Hash
Observed page title
Olympus Horse
Automated brand references
Base
TLS Certificate
Issued by Let's Encrypt / YR2 · stored validity ends in 72 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
50.116.87.118
Network ASN
AS31898
Organization
WEBSITEWELCOME.COM
Observed location
Vinhedo, BR
Server header
Apache

Nameservers 2

  • ns222.prodns.com.br
  • ns223.prodns.com.br

Mail routing 1 MX record

  • mail.olympushorse.com.brpriority 0

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR2
Valid from
2026-10-06 03:21:43
Valid until
2027-01-04 03:21:42
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprinte0cba37c30adb4abdfb606402e29ec62a3cff6b314c9449ccd672cff5f31f513
Certificate names · 2 SANs
  • *.olympushorse.com.br
  • olympushorse.com.br

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

Latest Classified Outcome 2026-10-23 10:38:51 UTC

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-10-23 10:38:51 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-23 10:38:51 UTC last content: 2026-10-23 10:38:51 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 · 7 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

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 olympushorse.com.br · checked Oct 21, 2026

32
Poor
Performance
FCP
4.05s
First Contentful Paint
LCP
12.02s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
2543ms
Total Blocking Time
SI
6.88s
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://olympushorse.com.br/dolo/ar24
Final URL: https://www.olympushorse.com.br/dolo/ar24/
Connexion - AR24
Response
HTTP 200
HTML body
10.6 KB
Compressed
3.6 KB
Links
0 internal · 0 external
Detected technologies
apache
Selected response headers
Server: Apache
Cache-Control: no-store, no-cache, must-revalidate
Content-Encoding: gzip
Content-Type: text/html; charset=UTF-8
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 11
Cache-Control
no-store, no-cache, must-revalidate
Connection
Keep-Alive
Content-Encoding
gzip
Content-Length
4485
Content-Type
text/html; charset=UTF-8
Date
Wed, 21 Oct 2026 15:29:56 GMT
Expires
Thu, 19 Nov 1981 08:52:00 GMT
Keep-Alive
timeout=5, max=74
Pragma
no-cache
Server
Apache
Vary
Accept-Encoding

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

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.

Stored observation history2

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→live_content

    content_served

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

Recorded activity

3 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    0/92 engine detections

    View source
  3. Added to PhishDestroy

    olympushorse.com.br

    View source

Check for cloaking

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

olympushorse.com.br

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

2 evidence signal groups linked 0 stored notification records Last known active

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.

Official reporting routes

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →

Report to Your Local Authorities

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

97-country directory

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

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

Recommendations & Advice for Victims

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

What should I do immediately?

Urgent

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

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

What information should I collect for my report?

FBI guidelines

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

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including olympushorse.com.br)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

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

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

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.

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/olympushorse.com.br"
  title="PhishDestroy threat report for olympushorse.com.br"
  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>