Skip to security report
This domain has been flagged as malicious
Security engines reporting a detection: 18. Public blocklists reporting a match: 1. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
olmo-martin.net favicon

olmo-martin.net

In short

PhishDestroy describes olmo-martin.net as a page titled Interactive Terminal, offering a command executor input with a Run button.

“Interactive Terminal”

Registrar
IONOS SE
Resolved IP
Germany217.91.141.218Deutsche Telekom AG
Registered
Feb 24, 2020
First observed
Nov 1, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
VirusTotal detections: 18/92 Stored blocklist matches: 1 Google Safe Browsing: threat flag recorded
VirusTotal
engine detections ·
Google Safe Browsing
Blocklist matches
PhishFeed
OTX
community references
URLScan
engine verdict · score 1
Page captures
open gallery
Domain age
registered 2020-02-24 according to WHOIS · source data differ
OTX: 1 ref Nov 1, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy describes olmo-martin.net as a page titled Interactive Terminal, offering a command executor input with a Run button.

Critical
Status
Last known active
VirusTotal
18 / 92
Blocklist matches
1
Hosting
Germany217.91.141.218Deutsche Telekom AG
Registrar
IONOS SE
Registered
Feb 24, 2020
OTX
1 community ref
Page captures
10

PhishDestroy analysis, reviewed version

The captured page at olmo-martin.net presents itself as an Interactive Terminal, with a "Command Executor" heading above a single text field inviting the visitor to enter a command such as id or ls -la. Submitting that field is done through a green "Run" button beside it, making command entry the page's central interaction. Below the input, the page also shows a headline introducing visitors to a portfolio, along with a Behance link.

The stored VirusTotal domain result reports 18 detections out of 92 engines. Bkav reported "malicious"; CRDF reported "malicious".

Source evidenceVirusTotal 18 / 92 · Google Safe Browsing: flagged · OTX 1 references 7 sources

VirusTotal

18 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 15 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
45
Malicious
18
Suspicious
0
Undetected
29

Vendor labels

Bkav
malicious
CRDF
malicious
DNS8
phishing
VIPRE
phishing
G-Data
phishing
Lionic
phishing
Sophos
phishing
Fortinet
phishing
SOCRadar
phishing
Kaspersky
phishing
Seclookup
malicious
Gridinsoft
phishing
MalwareURL
phishing
BitDefender
phishing
Chong Lua Dao
malicious
alphaMountain.ai
phishing
Google Safe Browsing
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Categories

alphaMountain.ai
Business/Economy, Phishing (alphaMountain.ai)

Registrar

IONOS SE

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    21600
    Type
    NS
    Value
    ns1064.ui-dns.biz
  • TTL, seconds
    3600
    Type
    A
    Value
    217.91.141.218
  • TTL, seconds
    21600
    Type
    NS
    Value
    ns1092.ui-dns.de
  • TTL, seconds
    21600
    Type
    NS
    Value
    ns1088.ui-dns.org
  • TTL, seconds
    21600
    Type
    SOA
    Responsible mailbox
    hostmaster.1und1.com
    Value
    ns1050.ui-dns.com
  • TTL, seconds
    21600
    Type
    NS
    Value
    ns1050.ui-dns.com

DNS records observed

JARM fingerprint

2ad2ad16d00000022c2ad2ad2ad2adc08b3be7d1a4f5f4d1fd42f049726e8a

Certificate

Subject alternative names
  • olmo-martin.net
  • www.olmo-martin.net
Issuer
Let's Encrypt / YR2
Serial
5624e536d8ee1c7ce56b972bee2cd60c9f7
SHA-256
15c2c41caca276357b0e64bdd95b80f346c52035b74fc8d6a489e1ca9c4b76ba
Subject
olmo-martin.net
Valid until
Valid from

Registration record

Registrar
IONOS SE
Registrar IANA ID
83
Registrar URL
http://www.ionos.com
Registered
Updated
Expires
Status
  • clientTransferProhibited
Nameservers
  • ns1050.ui-dns.com
  • ns1064.ui-dns.biz
  • ns1088.ui-dns.org
  • ns1092.ui-dns.de
DNSSEC
unsigned

Registry data (RDAP)

Status
  • client transfer prohibited
Registry events
Transfer
Last changed
Registration
Registrar expiration
Last RDAP database update
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 45,
    "malicious": 18,
    "suspicious": 0,
    "undetected": 29
}
Vendor labels
{
    "Bkav": "malicious",
    "CRDF": "malicious",
    "DNS8": "phishing",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "phishing",
    "MalwareURL": "phishing",
    "BitDefender": "phishing",
    "Chong Lua Dao": "malicious",
    "alphaMountain.ai": "phishing",
    "Google Safe Browsing": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Business/Economy, Phishing (alphaMountain.ai)"
}
Registrar
IONOS SE
Created
2020-02-24T12:24:09Z
Expires
2027-02-24T12:24:09Z
Updated
2026-02-25T08:27:04Z
First seen
2024-03-05T08:55:18Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns1064.ui-dns.biz"
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "217.91.141.218"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns1092.ui-dns.de"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns1088.ui-dns.org"
    },
    {
        "ttl": 21600,
        "type": "SOA",
        "rname": "hostmaster.1und1.com",
        "value": "ns1050.ui-dns.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns1050.ui-dns.com"
    }
]
Dns at
2026-10-26T23:32:05Z
Jarm
2ad2ad16d00000022c2ad2ad2ad2adc08b3be7d1a4f5f4d1fd42f049726e8a
Certificate
{
    "san": [
        "olmo-martin.net",
        "www.olmo-martin.net"
    ],
    "issuer": "Let's Encrypt / YR2",
    "serial": "5624e536d8ee1c7ce56b972bee2cd60c9f7",
    "sha256": "15c2c41caca276357b0e64bdd95b80f346c52035b74fc8d6a489e1ca9c4b76ba",
    "subject": "olmo-martin.net",
    "valid_to": "2026-12-12T22:39:49Z",
    "valid_from": "2026-09-13T22:39:50Z"
}
Registration record
{
    "registrar": "IONOS SE",
    "registrar_iana_id": "83",
    "registrar_url": "http://www.ionos.com",
    "created": "2020-02-24T12:24:09Z",
    "updated": "2026-02-25T08:27:04Z",
    "expires": "2027-02-24T12:24:09Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "ns1050.ui-dns.com",
        "ns1064.ui-dns.biz",
        "ns1088.ui-dns.org",
        "ns1092.ui-dns.de"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "client transfer prohibited"
    ],
    "events": {
        "transfer": "2020-07-11T08:30:50Z",
        "last changed": "2020-07-11T08:35:19Z",
        "registration": "2020-02-24T12:24:09Z",
        "registrar expiration": "2027-02-24T12:24:09Z",
        "last update of RDAP database": "2026-10-24T14:45:40Z"
    }
}
Separate source record · 18 malicious + 0 suspicious / 92 · 2026-10-26 23:31:49 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-26T23:31:49Z
fetched_at
2026-11-01T08:31:42Z
stats
{"timeout":0,"harmless":45,"malicious":18,"suspicious":0,"undetected":29}

Google Safe Browsing

Threat flag recorded

Open report

URLScan

Malicious · engine verdict · score 1

SHA-256 23077e2bb08f456a550e45ea37491b7c84770fe55cd0d60ecbb89958b35f39cf

Open report
URLScanOriginal source recordObserved: 25 fields

Observed: · Retrieved:

Report ID

01a19640-ca6a-72fa-95dc-03633b401241

Final URL

https://olmo-martin.net/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://olmo-martin.net/
    From
    http://olmo-martin.net/
    Status
    307

IP address

217.91.141.218

Reverse DNS (PTR)

pd95b8dda.dip0.t-ipconnect.de

Contacted domains

  • static.mercdn.net
  • cdn.snkrdunk.com
  • www.googletagmanager.com
  • b6.im-apps.net
  • www.google.com
  • dmp.im-apps.net
  • ajax.googleapis.com
  • dm.slim02.jp
  • apm.yahoo.co.jp
  • gum.criteo.com
  • komeri.search.zetacx.net
  • s.yimg.jp
  • b.im-apps.net
  • audiencedata.im-apps.net
  • atb.im-apps.net
  • bs.nakanohito.jp
  • sslwidget.criteo.com
  • www.google-analytics.com
  • sync6.im-apps.net
  • mug.criteo.com
  • ad.doubleclick.net
  • cs.nakanohito.jp
  • www.clarity.ms
  • tshop.r10s.jp
  • dynamic.criteo.com
  • fonts.googleapis.com
  • maxcdn.bootstrapcdn.com
  • www.komeri.com

Contacted IP addresses

  • 54.199.137.160
  • 34.49.1.209
  • 2600:1901:0:d959::
  • 2600:1901:0:2dbc::
  • 203.216.255.41
  • 203.114.55.131
  • 2620:100:a00b::38
  • 2a00:1450:4001:c21::66
  • 142.250.154.97
  • 2a02:26f0:7100::210:178
  • 2600:1901:0:d706::
  • 74.119.117.62
  • 142.251.13.149
  • 142.251.150.119
  • 35.186.221.74

Autonomous systems (ASN)

  • 16509
  • 396982
  • 23816
  • 2519
  • 19750
  • 15169
  • 20940
  • 8075
  • 44788
  • 54113

Server countries

  • JP
  • US
  • DE
  • CH
  • FR

Linked domains

  • www.youtube.com
  • twitter.com
  • www.instagram.com
  • www.facebook.com
  • lin.ee

Social media links

  • https://www.youtube.com
  • https://twitter.com/OLMO-MARTIN.NET
  • https://www.instagram.com/OLMO-MARTIN.NET
  • https://www.facebook.com/OLMO-MARTIN.NET
  • https://www.youtube.com/OLMO-MARTIN.NET

Document hash

84b11295b9bd0a50cf6db588b1367203111d97a667965b1340edb2157c1e8ff3

JavaScript globals

  • ytag
  • yjDataLayer
  • dataLayer
  • $
  • jQuery
  • deviceType
  • criteo_q
  • IsNumeric
  • ieVersionchecker
  • checkEnterKey
  • memberLoginDlg
  • closememberLoginDlg
  • navshare
  • zdView
  • Criteo
  • cto_csm_CspLogger
  • google_tag_manager
  • google_tag_data
  • clarity
  • _uic
  • _uih
  • itm_dl1_1022000
  • itm_dl2_1022000
  • _itm_
  • onYouTubeIframeAPIReady
  • gaGlobal
  • _UI_JSON
  • punycode
  • _uiconv
  • uiinit
  • _uia
  • Vesicomyid
  • ytagapi
  • yahoo_retargeting_sent_urls_counter
  • yahoo_retargeting_pv_id
  • IMLOGv2
  • IMUIDRequest
  • IMUID
  • _paq
  • Piwik

Cookies

  • _gcl_au
  • uid
  • _ga_S5RM945BLG
  • _ga
  • cto_bundle
  • _yjsu_yjad
  • __cf_bm
  • _im_vid
  • _im_id.1022000
  • _im_ses.1022000
  • AP
  • XA
  • XB

Browser storage keys

  • criteo_localstorage_check
  • _gcl_ls
  • cto_bundle
  • _yjsu_yjad
  • __itm_enc_1022000_X19pbV9zaWRzMQ
  • __itm_time_X19pbV9zaWRzMQ
  • __itm_uid_X19pbV9zaWRzMQ
  • _im_session_
  • _im_uid_status.1022000
  • _im_uid_expire.1022000
  • __storage_test__
  • zeta-session-key
  • zeta-user-id

TLS session and certificate

Subject alternative names
  • olmo-martin.net
  • www.olmo-martin.net
Cipher
AES_256_GCM
Issuer
YR2
Subject
olmo-martin.net
Protocol
TLS 1.2
Valid until
Valid from

Domain age, days

1974

Differs from the registration date in WHOIS (2020-02-24), which gives 2441 days on the scan date 2026-11-01. The two sources disagree; both values are kept as recorded.

Registered domain age, days

1974

Differs from the registration date in WHOIS (2020-02-24), which gives 2441 days on the scan date 2026-11-01. The two sources disagree; both values are kept as recorded.

Certificate age, days

48

Certificate validity, days

89

Page requests

140

Provider verdicts

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

HTTP headers

Server
Microsoft-IIS/10.0
Content-type
text/html; charset=utf-8
X-powered-by
ASP.NET
Strict-transport-security
max-age=0; preload
Original source fields · JSON
Uuid
01a19640-ca6a-72fa-95dc-03633b401241
Final url
https://olmo-martin.net/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://olmo-martin.net/",
        "from": "http://olmo-martin.net/",
        "status": 307
    }
]
Ip
217.91.141.218
Ptr
pd95b8dda.dip0.t-ipconnect.de
Contacted domains
[
    "static.mercdn.net",
    "cdn.snkrdunk.com",
    "www.googletagmanager.com",
    "b6.im-apps.net",
    "www.google.com",
    "dmp.im-apps.net",
    "ajax.googleapis.com",
    "dm.slim02.jp",
    "apm.yahoo.co.jp",
    "gum.criteo.com",
    "komeri.search.zetacx.net",
    "s.yimg.jp",
    "b.im-apps.net",
    "audiencedata.im-apps.net",
    "atb.im-apps.net",
    "bs.nakanohito.jp",
    "sslwidget.criteo.com",
    "www.google-analytics.com",
    "sync6.im-apps.net",
    "mug.criteo.com",
    "ad.doubleclick.net",
    "cs.nakanohito.jp",
    "www.clarity.ms",
    "tshop.r10s.jp",
    "dynamic.criteo.com",
    "fonts.googleapis.com",
    "maxcdn.bootstrapcdn.com",
    "www.komeri.com"
]
Contacted IP addresses
[
    "54.199.137.160",
    "34.49.1.209",
    "2600:1901:0:d959::",
    "2600:1901:0:2dbc::",
    "203.216.255.41",
    "203.114.55.131",
    "2620:100:a00b::38",
    "2a00:1450:4001:c21::66",
    "142.250.154.97",
    "2a02:26f0:7100::210:178",
    "2600:1901:0:d706::",
    "74.119.117.62",
    "142.251.13.149",
    "142.251.150.119",
    "35.186.221.74"
]
Asns
[
    "16509",
    "396982",
    "23816",
    "2519",
    "19750",
    "15169",
    "20940",
    "8075",
    "44788",
    "54113"
]
Countries
[
    "JP",
    "US",
    "DE",
    "CH",
    "FR"
]
Linked domains
[
    "www.youtube.com",
    "twitter.com",
    "www.instagram.com",
    "www.facebook.com",
    "lin.ee"
]
Social
[
    "https://www.youtube.com",
    "https://twitter.com/OLMO-MARTIN.NET",
    "https://www.instagram.com/OLMO-MARTIN.NET",
    "https://www.facebook.com/OLMO-MARTIN.NET",
    "https://www.youtube.com/OLMO-MARTIN.NET"
]
Document hash
84b11295b9bd0a50cf6db588b1367203111d97a667965b1340edb2157c1e8ff3
Globals
[
    "ytag",
    "yjDataLayer",
    "dataLayer",
    "$",
    "jQuery",
    "deviceType",
    "criteo_q",
    "IsNumeric",
    "ieVersionchecker",
    "checkEnterKey",
    "memberLoginDlg",
    "closememberLoginDlg",
    "navshare",
    "zdView",
    "Criteo",
    "cto_csm_CspLogger",
    "google_tag_manager",
    "google_tag_data",
    "clarity",
    "_uic",
    "_uih",
    "itm_dl1_1022000",
    "itm_dl2_1022000",
    "_itm_",
    "onYouTubeIframeAPIReady",
    "gaGlobal",
    "_UI_JSON",
    "punycode",
    "_uiconv",
    "uiinit",
    "_uia",
    "Vesicomyid",
    "ytagapi",
    "yahoo_retargeting_sent_urls_counter",
    "yahoo_retargeting_pv_id",
    "IMLOGv2",
    "IMUIDRequest",
    "IMUID",
    "_paq",
    "Piwik"
]
Cookies
[
    "_gcl_au",
    "uid",
    "_ga_S5RM945BLG",
    "_ga",
    "cto_bundle",
    "_yjsu_yjad",
    "__cf_bm",
    "_im_vid",
    "_im_id.1022000",
    "_im_ses.1022000",
    "AP",
    "XA",
    "XB"
]
Storage keys
[
    "criteo_localstorage_check",
    "_gcl_ls",
    "cto_bundle",
    "_yjsu_yjad",
    "__itm_enc_1022000_X19pbV9zaWRzMQ",
    "__itm_time_X19pbV9zaWRzMQ",
    "__itm_uid_X19pbV9zaWRzMQ",
    "_im_session_",
    "_im_uid_status.1022000",
    "_im_uid_expire.1022000",
    "__storage_test__",
    "zeta-session-key",
    "zeta-user-id"
]
Tls
{
    "san": [
        "olmo-martin.net",
        "www.olmo-martin.net"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "YR2",
    "subject": "olmo-martin.net",
    "protocol": "TLS 1.2",
    "valid_to": "2026-12-12T22:39:49Z",
    "valid_from": "2026-09-13T22:39:50Z"
}
Domain age days
1974

Differs from the registration date in WHOIS (2020-02-24), which gives 2441 days on the scan date 2026-11-01. The two sources disagree; both values are kept as recorded.

Apex age days
1974

Differs from the registration date in WHOIS (2020-02-24), which gives 2441 days on the scan date 2026-11-01. The two sources disagree; both values are kept as recorded.

Tls age days
48
Tls valid days
89
Requests
140
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 1,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "Microsoft-IIS/10.0",
    "content-type": "text/html; charset=utf-8",
    "x-powered-by": "ASP.NET",
    "strict-transport-security": "max-age=0; preload"
}
Separate monitor record · date not recorded

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

record_source
domain_monitor.urlscan
uuid
01a16853-3866-76c9-b500-762dfb815198
score
null
malicious
null
result_at
null
enriched_at
2026-11-01T09:10:38Z
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":"2026-11-01 10:10:38"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

1 community reference

Open report

Cloudflare Radar

Scan report

Open report
Cloudflare RadarOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Report ID

083d9384-5954-4187-8cad-a734a3e9522a

Final URL

https://olmo-martin.net/

HTTP response

200

Navigation history

  • URL
    https://olmo-martin.net/
    Status
    200

DOM structure hash

152db06ffb7241eb5fa586ac09a2e4730e6b8824aa727ae12d25f7f9edadb542

Document hash

2e0911ae082b2b6194930a75323cf00affc420711f95e2d542f6bb07223eb52b

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    olmo-martin.net
    Type
    A
    Value
    217.91.141.218

DNSSEC valid

No

IP address

127.0.1.13

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

Registration record

Registrar
IONOS SE
Registered
Updated
Expires
Nameservers
  • ns1050.ui-dns.com
  • ns1064.ui-dns.biz
  • ns1088.ui-dns.org
  • ns1092.ui-dns.de
Original source fields · JSON
Uuid
083d9384-5954-4187-8cad-a734a3e9522a
Final url
https://olmo-martin.net/
Status
200
History
[
    {
        "url": "https://olmo-martin.net/",
        "status": 200
    }
]
DOM structure hash
152db06ffb7241eb5fa586ac09a2e4730e6b8824aa727ae12d25f7f9edadb542
Document hash
2e0911ae082b2b6194930a75323cf00affc420711f95e2d542f6bb07223eb52b
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "olmo-martin.net",
        "type": "A",
        "value": "217.91.141.218"
    }
]
Dnssec valid
false
Ip
127.0.1.13

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

Registration record
{
    "registrar": "IONOS SE",
    "created": "2020-02-24T12:24:09Z",
    "updated": "2026-02-25T08:27:04Z",
    "expires": "2027-02-24T12:24:09Z",
    "nameservers": [
        "ns1050.ui-dns.com",
        "ns1064.ui-dns.biz",
        "ns1088.ui-dns.org",
        "ns1092.ui-dns.de"
    ]
}

PhishDestroy DOM

10 / 100 · heuristic score · 3 brand references · 0 classifications

Open report

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

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

ai_title
olmo-martin.net — Interactive Terminal command executor page
ai_description
PhishDestroy describes olmo-martin.net as a page titled Interactive Terminal, offering a command executor input with a Run button.
ai_summary
The captured page at olmo-martin.net presents itself as an Interactive Terminal, with a "Command Executor" heading above a single text field inviting the visitor to enter a command such as id or ls -la. Submitting that field is done through a green "Run" button beside it, making command entry the page's central interaction. Below the input, the page also shows a headline introducing visitors to a portfolio, along with a Behance link. The stored VirusTotal domain result reports 18 detections out of 92 engines. Bkav reported "malicious"; CRDF reported "malicious".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-11-01 09:36:53
revision
e9c8381c59f2bd5ca59780388e91f9b6a69b24d90190144f051c258aad569ab6
mode
reviewed
interpretation
Selected public package; text generation time is separate from source observation dates.

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

Collected source details

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

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 25 fields

Mail configuration

SPF lookups
0

CAA records

Domain
olmo-martin.net

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
13
Archived days
19
Snapshots per day
0.01
Average page size, bytes
9876

Crawler rules

User agents
  • *
Present
Yes
Sitemap URLs
  • https://olmo-martin.net/index.php/sitemap.xml

Sitemap

Present
Yes
URL count
5000

Page title and metadata

Indexing directives
noindex, nofollow
Generator
WordPress 7.0
Canonical URL
https://olmo-martin.net/

Trackers

Requests
4

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
8
TLS
77
Waiting
4885
Connection
28
Download
22
Response time, ms
5020

TLS connection

ALPN
h2
Cipher
ECDHE-RSA-AES256-GCM-SHA384
Protocol
TLSv1.2
Supported versions
  • TLSv1
  • TLSv1.1
  • TLSv1.2
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443

Carbon estimate

Bytes
26075
CO₂, grams
0.001
Cleaner than, %
51

DNS servers

Nameservers
  • IP address
    185.132.34.50
    Host
    ns1050.ui-dns.com
  • IP address
    185.132.32.92
    Host
    ns1092.ui-dns.de
  • IP address
    185.132.35.88
    Host
    ns1088.ui-dns.org
  • IP address
    185.132.33.64
    Host
    ns1064.ui-dns.biz
DNS zone
olmo-martin.net

Location

IP address
217.91.141.218
ASN
3320
Organization
Deutsche Telekom AG
City
Dortmund
Country
DE

TLS certificate

Issuer
Let's Encrypt / YR2
Subject
olmo-martin.net

DNS records

A
  • 217.91.141.218
NS
  • ns1092.ui-dns.de
  • ns1050.ui-dns.com
  • ns1088.ui-dns.org
  • ns1064.ui-dns.biz
SOA
Primary nameserver
ns1050.ui-dns.com
Hostmaster
hostmaster.1und1.com
Serial
2017060118
Refresh, seconds
28800
Retry, seconds
7200
Expiry, seconds
604800
Minimum TTL, seconds
600

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Header value
max-age=0; preload
Observation
HSTS max-age is 0, below the 31536000 minimum.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
max-age=0; preload
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
217.91.141.218
IP version
4

Redirects

Redirect chain
  • https://olmo-martin.net

Page links

External link addresses
  • https://cikmaparcacin.com/
  • https://yolundayim.com/
  • https://cikmaparcacin.com/ilan/
  • https://casino50.com/
External links
4
Internal links
1

Registration record

Registrar
IONOS SE
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • ns1050.ui-dns.com
  • ns1064.ui-dns.biz
  • ns1088.ui-dns.org
  • ns1092.ui-dns.de

HTTP headers

Response headers
Server
Microsoft-IIS/10.0
Content-type
text/html; charset=UTF-8
X-powered-by
ASP.NET
Strict-transport-security
max-age=0; preload
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "olmo-martin.net"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-11-01T08:25:34Z",
    "first": "2021-02-26T10:31:11Z",
    "changes": 13,
    "days_archived": 19,
    "scans_per_day": 0.01,
    "avg_page_bytes": 9876
}
Crawler rules
{
    "agents": [
        "*"
    ],
    "present": true,
    "sitemaps": [
        "https://olmo-martin.net/index.php/sitemap.xml"
    ]
}
Sitemap
{
    "present": true,
    "url_count": 5000
}
Page title and metadata
{
    "robots": "noindex, nofollow",
    "generator": "WordPress 7.0",
    "canonicalUrl": "https://olmo-martin.net/"
}
Trackers
{
    "requests": 4
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 8,
        "tls": 77,
        "wait": 4885,
        "connect": 28,
        "download": 22
    },
    "response_ms": 5020
}
TLS connection
{
    "alpn": "h2",
    "cipher": "ECDHE-RSA-AES256-GCM-SHA384",
    "protocol": "TLSv1.2",
    "versions": [
        "TLSv1",
        "TLSv1.1",
        "TLSv1.2"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Carbon
{
    "bytes": 26075,
    "co2_grams": 0.001,
    "cleaner_than": 51
}
Dns server
{
    "ns": [
        {
            "ip": "185.132.34.50",
            "host": "ns1050.ui-dns.com"
        },
        {
            "ip": "185.132.32.92",
            "host": "ns1092.ui-dns.de"
        },
        {
            "ip": "185.132.35.88",
            "host": "ns1088.ui-dns.org"
        },
        {
            "ip": "185.132.33.64",
            "host": "ns1064.ui-dns.biz"
        }
    ],
    "zone": "olmo-martin.net"
}
Location
{
    "ip": "217.91.141.218",
    "asn": "3320",
    "org": "Deutsche Telekom AG",
    "city": "Dortmund",
    "country": "DE"
}
Ssl
{
    "issuer": "Let's Encrypt / YR2",
    "subject": "olmo-martin.net"
}
DNS records
{
    "A": [
        "217.91.141.218"
    ],
    "NS": [
        "ns1092.ui-dns.de",
        "ns1050.ui-dns.com",
        "ns1088.ui-dns.org",
        "ns1064.ui-dns.biz"
    ],
    "SOA": "{\"nsname\": \"ns1050.ui-dns.com\", \"hostmaster\": \"hostmaster.1und1.com\", \"serial\": 2017060118, \"refresh\": 28800, \"retry\": 7200, \"expire\": 604800, \"minttl\": 600}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=0; preload",
    "message": "HSTS max-age is 0, below the 31536000 minimum."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": "max-age=0; preload",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "217.91.141.218",
    "family": 4
}
Redirects
{
    "chain": [
        "https://olmo-martin.net"
    ]
}
Page links
{
    "external": [
        "https://cikmaparcacin.com/",
        "https://yolundayim.com/",
        "https://cikmaparcacin.com/ilan/",
        "https://casino50.com/"
    ],
    "external_count": 4,
    "internal_count": 1
}
Registration record
{
    "registrar": "IONOS SE",
    "created": "2020-02-24T12:24:09Z",
    "updated": "2026-02-25T08:27:04Z",
    "expires": "2027-02-24T12:24:09Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "ns1050.ui-dns.com",
        "ns1064.ui-dns.biz",
        "ns1088.ui-dns.org",
        "ns1092.ui-dns.de"
    ]
}
HTTP headers
{
    "headers": {
        "server": "Microsoft-IIS/10.0",
        "content-type": "text/html; charset=UTF-8",
        "x-powered-by": "ASP.NET",
        "strict-transport-security": "max-age=0; preload"
    }
}

Questions about olmo-martin.net

Is olmo-martin.net legit?

PhishDestroy describes olmo-martin.net as a page titled Interactive Terminal, offering a command executor input with a Run button.

Is olmo-martin.net safe to connect a wallet?

This report does not record which wallet requests olmo-martin.net 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 olmo-martin.net?

It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority; a report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy · PhishFeed · no match in the other 10 2
PhishDestroy PhishDestroy list View source
PhishFeed Listed View source

Last checked

Stored Capture · 10 captures

All capture links and hashes (10)

Domain details

Domain
Google Safe Browsing Flagged Social engineering checked Nov 1, 2026
IP Reputation Germany217.91.141.218 abuse score 0/100 0 reports checked Nov 1, 2026
Hosting abuse contact abuse@telekom.de Deutsche Telekom AG · AS3320
RegistrationCreated Feb 24, 2020 — Expires Feb 24, 2027
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedNov 1, 2026
DOM Analysisanalyzed Nov 1, 2026score 10/1003 brand signals
Submitted URLhttp://olmo-martin.net/
Observed page title
Interactive Terminal
Automated brand references
Facebook Instagram YouTube
TLS Certificate
Issued by YR2 · stored validity ends in 41 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Germany217.91.141.218
Network ASN
AS3320
AS name
DTAG Deutsche Telekom AG, DE
Organization
Deutsche Telekom AG
Observed location
GermanyDortmund, DE
Server header
Microsoft-IIS/10.0

Nameservers 4

  • ns1050.ui-dns.com
  • ns1064.ui-dns.biz
  • ns1088.ui-dns.org
  • ns1092.ui-dns.de

SOA

  • nsname: ns1050.ui-dns.com
  • hostmaster: hostmaster.1und1.com
  • serial: 2017060118
  • refresh: 28800
  • retry: 7200
  • expire: 604800
  • minttl: 600

Registrar abuse contact VirusTotal WHOIS

Location describes the IP network.

TLS certificate

Issuer
YR2
Valid from
2026-09-13 22:39:50
Valid until
2026-12-12 22:39:49
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint15c2c41caca276357b0e64bdd95b80f346c52035b74fc8d6a489e1ca9c4b76ba
Certificate names · 2 SANs
  • olmo-martin.net
  • www.olmo-martin.net

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

Report This Domain Submit evidence & help protect others

VirusTotal Analysis

18 / 92 security vendors flagged this domain
View on VT
Last analyzed
alphaMountain.ai
BitDefender
Bkav
Chong Lua Dao
CRDF
DNS8
Forcepoint ThreatSeeker
Fortinet
G-Data
Google Safe Browsing
Gridinsoft
Kaspersky
Lionic
MalwareURL
Seclookup
SOCRadar
Sophos
VIPRE

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of olmo-martin.net · checked Nov 1, 2026

96
Good
Performance
FCP
1.04 s
First Contentful Paint
LCP
1.04 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
5.29 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 403
Requested URL: http://olmo-martin.net/
403 - Verboten: Zugriff verweigert.
Response
HTTP 403
HTML body
1.2 KB
Compressed
669 B
Links
0 internal · 0 external
Selected response headers
Content-Type: text/html
Server: Microsoft-IIS/10.0
X-Powered-By: ASP.NET
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 5
Content-Length
1244
Content-Type
text/html
Date
Sun, 01 Nov 2026 08:28:52 GMT
Server
Microsoft-IIS/10.0
X-Powered-By
ASP.NET

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

Captured network requests

Network requests: 140 SHA-256 hashes: 62 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-11-01 08:42 UTC.

Open this scan on URLScan 01a19640-ca6a-72fa-95dc-03633b401241 ↗

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. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

  2. Domain monitor · First collection record

    Reachable

All retained availability observations2

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

  1. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 09:34:00.081071
    Evidence SHA-256
    95dedd1e4016ea57e34bdbce51e0ec491a6e3d89d4fb09684d0437765fe8625c
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  2. 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 23:31:41.538396
    Evidence SHA-256
    d507886309fe7925b612af112c97b5593f8ff1d1bd6793149e30d59a14244ced
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 23:31:41.538396
    Evidence reason

Threat Response Pipeline

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

Recorded events: 12. 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
    olmo-martin.net detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · Google Safe Browsing · Blocklist Detection · OTX Community References · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 10 of 10
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 1
  • 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: 18/92
  • Google Safe Browsing
    Listed as unsafe by Google Safe Browsing (Google Transparency Report)
  • Blocklist Detection
    Found in blocklists: PhishFeed
  • OTX Community References
    Community publication references on AlienVault OTX: 1. References are not vendor verdicts and are excluded from the evidence score.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

6 entries
  1. URLScan

    Page captured

    View source
  2. AlienVault OTX

    1 community references

    View source
  3. Google Safe Browsing

    Threat flag recorded

    View source
  4. Wayback Machine

    Page archived

    View source
  5. Added to PhishDestroy

    olmo-martin.net

    View source
  6. VirusTotal

    18/92 engine detections

    View source
How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

Check for cloaking

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

olmo-martin.net

Evidence & External Reports

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.

Official reporting routes

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.

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 olmo-martin.net)
  • 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

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

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

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

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/olmo-martin.net"
  title="PhishDestroy threat report for olmo-martin.net"
  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>