VirusTotal
13 / 92 engine detections
Open reportmakelarij.be is a Google impersonation page detected by PhishDestroy on 2026-10-16. Risk: critical (100/100). Registrar: Vimexx. Hosting: AS-ZXCS Stichting DIGI NL, NL. VirusTotal: 13/92 engines flag it. Google Safe Browsing flags it. Do not enter credentials or connect a wallet.
13 / 92 engine detections
Open reportThreat flag recorded
Open reportDBL_ABUSED_PHISH
no community references
Open reportprovider verdict: clean
Open reportNo malicious flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
makelarij.be is a Belgian domain that PhishDestroy classifies as an impersonation phishing page. It presents itself as a legitimate service so that visitors trust it with sensitive information. PhishDestroy first flagged it on 2026-10-16. At the most recent check on 2026-10-19, we could not confirm whether the site or its phishing content was still online, so treat the domain as dangerous.
Impersonation phishing copies the look, wording and branding of an organisation that victims already trust. Visitors usually arrive through an email, text message or ad. The page then asks them to log in, confirm account details or settle a supposed payment. Anything typed into the form goes straight to the operators, and victims can lose account access, personal data and money taken with stolen payment details.
Google Safe Browsing flags the domain as social engineering, the category it uses for deceptive pages that trick users into revealing information. Spamhaus lists it in its DBL under abused phishing. That listing indicates the domain is being used for phishing and points to an otherwise legitimate domain that has been misused. On VirusTotal, only CRDF flagged it, 1 of 92 engines on 2026-10-16. That count is low, but the Google and Spamhaus verdicts and our own blocklist entry point the same way.
The domain was registered on 2018-01-28 through Vimexx, more than eight years before it was caught hosting phishing. Together with the Spamhaus abused classification, that age suggests an established site that was taken over rather than a throwaway domain bought for the campaign. It resolves to 185.220.172.4 on AS206281 Stichting DIGI NL in the Netherlands.
If you entered a password on this site, change it now on the real service and anywhere else you reuse it. Then turn on two-factor authentication and review recent logins and account settings. If you gave card or bank details, contact your bank to block the card and dispute any unfamiliar charges. Be wary of follow-up calls or messages that cite details you typed into the page. Defenders should block the domain and its IP at the mail gateway and web proxy, and search logs for users who visited it on or after 2026-10-16. The owner of an affected legitimate site should audit the server for injected files and rotate its hosting credentials.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 01a1451a-63f1-7439-b404-7a1873a30277 |
|---|---|
| Final url | https://makelarij.be/wp-includes/Text/bgelawo/fjlargk/fagnvqi/hhdg/chi/index.html |
| Status | 401 |
| Ip | 2a06:2ec0:1:e::125 |
| Contacted IP addresses | [
"2a06:2ec0:1:e::125"
] |
| Asns | [
"206281"
] |
| Countries | [
"NL"
] |
| Document hash | cc90734ca6dc304a242ea8626cda4061179df093a1f258be82abfe08e65ed5de |
| Globals | [
"errorPageController",
"certificateErrorPageController",
"supervisedUserErrorPageController"
] |
| Tls | {
"san": [
"mail.makelarij.be",
"makelarij.be",
"www.makelarij.be"
],
"cipher": "AES_128_GCM",
"issuer": "YR1",
"subject": "makelarij.be",
"protocol": "TLS 1.3",
"valid_to": "2026-12-30T05:31:59Z",
"valid_from": "2026-10-01T05:32:00Z"
} |
| Domain age days | 3046 |
| Apex age days | 3046 |
| Tls age days | 15 |
| Tls valid days | 89 |
| Requests | 1 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": -84,
"malicious": false
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"server": "Apache",
"content-type": "text/html; charset=iso-8859-1"
} |
Observed: · Retrieved:
| Uuid | c9e2b9f6-bd22-4250-b98e-dd64189e5dee |
|---|---|
| Final url | https://makelarij.be/ |
| History | [
{
"url": "https://makelarij.be/",
"status": 0
}
] |
| DOM structure hash | a7fe83ec64bb23eb28090598db3d166ed98e52e39d1afbbfd74c579553f93e4e |
| Domain risks | [
"Business",
"Business & Economy"
] |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "makelarij.be",
"type": "A",
"value": "185.220.172.4"
},
{
"name": "makelarij.be",
"type": "AAAA",
"value": "2a06:2ec0:1:e::125"
}
] |
| Dnssec valid | true |
| Registration record | {
"created": "2018-01-28T00:00:00Z",
"nameservers": [
"ns.zxcs.nl",
"ns.zxcs.be",
"ns.zxcs.eu"
]
} |
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 55,
"malicious": 3,
"suspicious": 0,
"undetected": 34
} |
|---|---|
| Vendor labels | {
"CRDF": "malicious",
"Gridinsoft": "phishing",
"alphaMountain.ai": "phishing"
} |
| Reputation | 0 |
| First seen | 2024-03-05T07:39:14Z |
| DNS records | [
{
"ttl": 600,
"type": "AAAA",
"value": "2a06:2ec0:1:e::125"
},
{
"ttl": 600,
"type": "NS",
"value": "ns.zxcs.be"
},
{
"ttl": 600,
"type": "NS",
"value": "ns.zxcs.nl"
},
{
"ttl": 600,
"type": "NS",
"value": "ns.zxcs.eu"
},
{
"ttl": 600,
"type": "TXT",
"value": "v=spf1 a mx ip4:185.220.172.4 ip6:2a06:2ec0:1:e:0:0:0:125 include:filter-out.zxcs.nl ~all"
},
{
"ttl": 600,
"type": "A",
"value": "185.220.172.4"
},
{
"ttl": 600,
"type": "MX",
"value": "spamrelay.zxcs.nl",
"priority": 10
},
{
"ttl": 600,
"type": "SOA",
"rname": "hostmaster.makelarij.be",
"value": "ns.zxcs.nl"
}
] |
| Dns at | 2026-10-19T10:18:19Z |
| Jarm | 2ad2ad0002ad2ad00041d41d0000000464fb8c6842ac133bede81390a48134 |
| Certificate | {
"san": [
"mail.makelarij.be",
"makelarij.be",
"www.makelarij.be"
],
"issuer": "Let's Encrypt / YR1",
"serial": "614520cda505df87ba1b4509ae7ac103244",
"sha256": "c8710606847d09d0c1424f69922d1f7f7f1055bc9d42576a656aac3309f3a23a",
"subject": "makelarij.be",
"valid_to": "2026-12-30T05:31:59Z",
"valid_from": "2026-10-01T05:32:00Z"
} |
No. PhishDestroy classifies makelarij.be as a Google impersonation page (risk: critical, 100/100); it was first detected on 2026-10-16. VirusTotal: 13/92 engines flag it. Google Safe Browsing flags it. Listed on Spamhaus DBL. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on makelarij.be. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
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.
ns.zxcs.euspamrelay.zxcs.nlpriority 10Location describes the IP network.
c8710606847d09d0c1424f69922d1f7f7f1055bc9d42576a656aac3309f3a23amail.makelarij.bewww.makelarij.beSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
community.makelarij.beDomain recorddewarmsteboom.makelarij.beDomain recordmail.makelarij.beDomain recordsocial.makelarij.beDomain recordtochten.makelarij.beDomain recordverbruik.makelarij.beDomain recordwww.makelarij.beDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of makelarij.be · checked Oct 16, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://makelarij.be/wp-includes/Text/bgelawo/fjlargk/fagnvqi/hiug/pdfstemhnic.htmlContent-Type: text/html; charset=iso-8859-1Server: Apache439text/html; charset=iso-8859-1Fri, 16 Oct 2026 14:30:16 GMTApacheValues retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
No flag recorded→Flag recorded
Threat flag recorded
View source13/92 engine detections
View sourcemakelarij.be
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
makelarij.be
Listed domains receive at least one abuse report; this entry has no retained notification history.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
makelarij.be)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.