Skip to security report
Analytics Dashboard
Domain security and threat intelligence
inlogics.pro favicon

inlogics.pro

In short

inlogics.pro is a blocklisted domain detected by PhishDestroy on 2026-10-22. Risk: critical (81/100). Registrar: OVH SAS. Status: Last known active. Hosting: Onatel Burkina Faso. PhishDestroy sent 1 abuse report. VirusTotal: 4/92 engines flag it. Do not enter credentials or connect a wallet.

“inLogics — Conseil Datacenter, Cybersécurité & Infrastructures Critiques en Afrique”

Registrar
OVH SAS
Resolved IP
196.28.247.94
Registered
Sep 29, 2020
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
Risk signals
VirusTotal detections: 4/92
OTX: 4 refs Oct 22, 2026 1 Report Sent
API
This domain has been flagged as malicious
Security engines reporting a detection: 4. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
4 / 92
engine detections
Google Safe Browsing
No threat flag
OTX
4
community references
Page captures
10
open gallery
Domain age
2213 days
Reports sent
1
view timeline
Source evidenceVirusTotal 4 / 92 · OTX 4 references 6 sources

VirusTotal

4 / 92 engine detections

Open report

OTX

4 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

Critical
VirusTotal
4 / 92
OTX
4 community refs
Page captures
10
Page captures Source results Registration record

PhishDestroy threat report

Overview

PhishDestroy listed inlogics.pro as a suspicious domain based on security‑engine detections. The recorded page title is “inLogics — Conseil Datacenter, Cybersécurité & Infrastructures Critiques en Afrique”. The domain was first seen by PhishDestroy on 2026-10-22 and returned an HTTP 200 response at that time.

How the scam works

The detections point to a generic phishing risk where attackers host pages that mimic legitimate services to lure credentials or personal data. No specific credential‑harvesting form or other malicious behavior was observed on the captured page, so the assessment relies on the broader phishing indicators reported by security engines.

Evidence

VirusTotal scanned the domain on 2026-10-22 and reported four detections, three labeled malicious (CRDF, Gridinsoft, SOCRadar) and one suspicious (DNS8) out of 92 engines. Google Safe Browsing checked the same day and did not flag the site. urlscan.io captured the page on 2026-10-22, assigning a malicious verdict with a 100 score and categorising it as phishing, linking it to the brand Banco CTT. The domain also appears on the OpenPhish blocklist and has four OTX pulses as of 2026-10-22. PhishDestroy’s internal listing cites “🦠 VT: 3 malicious vendors” as the reason for inclusion.

Infrastructure

The domain was registered on 2020-09-29 through OVH SAS, with the creation date recorded as 2020-09-30. The recorded IP address is 196.28.247.94, belonging to Onatel in Burkina Faso (ASN 25543). TLS was provided by a Let’s Encrypt certificate issued on 2026-10-15 and valid until 2027-01-13, and the domain uses Cloudflare nameservers. Open ports observed during scanning were 22, 80, 443 and 3306.

What to do

Visitors should treat the site as untrusted and avoid entering any login credentials or personal information; if credentials were entered, change the associated passwords immediately. Organizations should add the domain to internal blocklists and monitor network logs for connections to the address. Reference the VirusTotal and urlscan findings when investigating or reporting the domain.

Useful links

urlscan.io scan and screenshotCloudflare Radar reportURLQuery reportStored capture screenshotCloudflare Radar screenshot (2026-10-22T13:03:37Z)URLQuery screenshotURLScan screenshot (2026-10-20T12:49:07Z)URLScan capture reportURLScan screenshot (2026-10-21T10:36:01Z)URLScan capture reportURLScan screenshot (2026-10-21T15:31:18Z)URLScan capture reportURLScan screenshot (2026-10-22T12:59:58Z)URLScan capture reportURLScan screenshot (2026-10-22T13:13:33Z)URLScan capture reportVirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review

Collected source details

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

URLScan · 2026-10-22T13:03:58Z

Observed: · Retrieved:

Uuid
01a163b5-f8f7-71db-83fa-0457dc8ea6fd
Final url
https://inlogics.pro/front/pt/
Status
200
Redirected
same-domain
Redirects
[
    {
        "to": "https://inlogics.pro/front/pt",
        "from": "http://inlogics.pro/front/pt",
        "status": 307
    },
    {
        "to": "https://inlogics.pro/front/pt/",
        "from": "https://inlogics.pro/front/pt",
        "status": 301
    }
]
Ip
196.28.247.94
Ptr
notification.fasonet.bf
Contacted IP addresses
[
    "196.28.247.94"
]
Asns
[
    "25543"
]
Countries
[
    "BF"
]
Document hash
17304d7dbd6173d54e663d2cbb1b262bad5d8791b65628e8298e11b3176f4ba9
Tls
{
    "san": [
        "inlogics.pro",
        "www.inlogics.pro"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YR2",
    "subject": "inlogics.pro",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-13T09:24:53Z",
    "valid_from": "2026-10-15T09:24:54Z"
}
Domain age days
2212
Apex age days
2212
Tls age days
7
Tls valid days
89
Requests
1
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 96,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "bancoctt"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "Banco CTT"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "nginx",
    "content-type": "text/html",
    "x-powered-by": "PleskLin",
    "strict-transport-security": "max-age=15768000; includeSubDomains"
}
Cloudflare Radar · 2026-10-22T13:03:37Z

Observed: · Retrieved:

Uuid
d0c6808d-cc35-4532-b0c9-70a249d69559
Final url
https://inlogics.pro/
Status
200
History
[
    {
        "url": "https://inlogics.pro/",
        "status": 200
    }
]
DOM structure hash
a8e01e91af1789aec9e25e35157f2a0088154226d697296f31786163a6303a24
Document hash
ba626a815075a96abe9c0d663e72cbee6ad60a0321e00363559da8a7776458d2
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "inlogics.pro",
        "type": "A",
        "value": "196.28.247.94"
    }
]
Dnssec valid
false
Ip
196.28.247.94
VirusTotal · 2026-10-22T13:20:36Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 55,
    "malicious": 3,
    "suspicious": 1,
    "undetected": 33
}
Vendor labels
{
    "CRDF": "malicious",
    "DNS8": "suspicious",
    "SOCRadar": "phishing",
    "Gridinsoft": "phishing"
}
Reputation
0
Registrar
OVH SAS
Created
2020-09-29T22:06:26Z
Expires
2023-09-29T22:06:26Z
Updated
2022-09-25T12:29:43Z
First seen
2024-08-06T09:47:12Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "john.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "MX",
        "value": "mx2.mail.ovh.net",
        "priority": 5
    },
    {
        "ttl": 300,
        "type": "MX",
        "value": "mx1.mail.ovh.net",
        "priority": 1
    },
    {
        "ttl": 300,
        "type": "TXT",
        "value": "v=spf1 ip4=188.165.36.237 ip4=87.98.160.167 ip4=91.121.53.175 include:mx.ovh.com ~all"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "196.28.247.94"
    },
    {
        "ttl": 300,
        "type": "MX",
        "value": "mx3.mail.ovh.net",
        "priority": 100
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "amber.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "TXT",
        "value": "google-site-verification=FcHoYiEkAIjPs3MPCrqoQEAm43HgSKFASzjnESdkQxU"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "amber.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "TXT",
        "value": "1|www.inlogics.pro"
    }
]
Dns at
2026-10-22T13:21:05Z
Jarm
00000000000000000042d43d0000009535d5979f591ae8e547c5e5743e5b64
Certificate
{
    "san": [
        "inlogics.pro",
        "www.inlogics.pro"
    ],
    "issuer": "Let's Encrypt / YR2",
    "serial": "5c17505554105f3955e888ce543eb4655ca",
    "sha256": "1dc86cc0f84933edf80a6f3e99983291f9c2c23681b9764dd4b8f0277caf745a",
    "subject": "inlogics.pro",
    "valid_to": "2027-01-13T09:24:53Z",
    "valid_from": "2026-10-15T09:24:54Z"
}
Registration record
{
    "registrar": "OVH SAS",
    "registrar_iana_id": "433",
    "registrar_url": "http://www.ovh.com",
    "created": "2020-09-29T20:06:26Z",
    "updated": "2020-12-17T10:48:12Z",
    "expires": "2021-09-29T20:06:26Z",
    "status": [
        "clientDeleteProhibited",
        "clientTransferProhibited"
    ],
    "nameservers": [
        "amber.ns.cloudflare.com",
        "john.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "client delete prohibited",
        "client transfer prohibited"
    ],
    "events": {
        "expiration": "2027-09-29T22:06:26Z",
        "last changed": "2026-09-27T19:38:43Z",
        "registration": "2020-09-29T22:06:26Z",
        "registrar expiration": "2027-09-29T22:08:27Z",
        "last update of RDAP database": "2026-09-27T19:38:56Z"
    }
}
Website checks · 2026-10-22T13:07:10Z
Mail configuration
{
    "mx": [
        "mx1.mail.ovh.net",
        "mx3.mail.ovh.net",
        "mx2.mail.ovh.net"
    ],
    "spf": "v=spf1 ip4=188.165.36.237 ip4=87.98.160.167 ip4=91.121.53.175 include:mx.ovh.com ~all",
    "dmarc": true,
    "spf_lookups": 3
}
Caa records
{
    "domain": "inlogics.pro"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-10-22T12:59:40Z",
    "first": "2021-01-26T21:41:20Z",
    "changes": 24,
    "days_archived": 34,
    "scans_per_day": 0.02,
    "avg_page_bytes": 6880
}
Page title and metadata
{
    "ogUrl": "https://www.inlogics.pro/",
    "title": "inLogics — Conseil Datacenter, Cybersécurité & Infrastructures Critiques en Afrique",
    "author": "inLogics",
    "ogType": "website",
    "robots": "index, follow",
    "ogTitle": "inLogics — Conseil Datacenter, Cybersécurité & Infrastructures Critiques en Afrique",
    "keywords": "datacenter Afrique, cybersécurité Afrique, audit datacenter, SOC Afrique, conseil infrastructure critique, CISSP Afrique, inLogics, Burkina Faso",
    "description": "Cabinet de conseil spécialisé en datacenters, cybersécurité et infrastructures numériques critiques. +15 ans d'expérience en Afrique de l'Ouest et Centrale. Certifiés CISSP & ISO 27001.",
    "ogDescription": "Cabinet de conseil spécialisé en datacenters, cybersécurité et infrastructures numériques critiques. +15 ans d'expérience en Afrique de l'Ouest et Centrale."
}
Trackers
{
    "requests": 10,
    "trackers": [
        {
            "name": "Google Fonts",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        },
        {
            "name": "Google Static",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 2
        }
    ]
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 18,
        "tls": 143,
        "wait": 274,
        "connect": 137,
        "download": 137
    },
    "response_ms": 709
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        22,
        80,
        443,
        3306
    ]
}
Carbon
{
    "bytes": 45568,
    "co2_grams": 0.0017,
    "cleaner_than": 39
}
Dns server
{
    "ns": [
        {
            "ip": "172.64.33.185",
            "host": "john.ns.cloudflare.com"
        },
        {
            "ip": "108.162.192.64",
            "host": "amber.ns.cloudflare.com"
        }
    ],
    "zone": "inlogics.pro"
}
Location
{
    "ip": "196.28.247.94",
    "asn": "25543",
    "org": "Onatel Burkina Faso",
    "city": "Bobo-Dioulasso",
    "country": "BF"
}
Ssl
{
    "issuer": "Let's Encrypt / YR2",
    "subject": "inlogics.pro"
}
DNS records
{
    "A": [
        "196.28.247.94"
    ],
    "MX": [
        "{\"exchange\": \"mx1.mail.ovh.net\", \"priority\": 1}",
        "{\"exchange\": \"mx3.mail.ovh.net\", \"priority\": 100}",
        "{\"exchange\": \"mx2.mail.ovh.net\", \"priority\": 5}"
    ],
    "NS": [
        "john.ns.cloudflare.com",
        "amber.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"amber.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2417433606, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}",
    "TXT": [
        "1|www.inlogics.pro",
        "v=spf1 ip4=188.165.36.237 ip4=87.98.160.167 ip4=91.121.53.175 include:mx.ovh.com ~all",
        "google-site-verification=FcHoYiEkAIjPs3MPCrqoQEAm43HgSKFASzjnESdkQxU"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": true
}
Hsts
{
    "header": "max-age=15768000; includeSubDomains",
    "message": "HSTS max-age is 15768000, below the 31536000 minimum."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": "max-age=15768000; includeSubDomains",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "196.28.247.94",
    "family": 4
}
Redirects
{
    "chain": [
        "https://inlogics.pro"
    ]
}
Subdomains
{
    "count": 15,
    "subdomains": [
        "apitest.inlogics.pro",
        "cloud.inlogics.pro",
        "elearning.ifrisse.inlogics.pro",
        "gw.inlogics.pro",
        "ifrisse.inlogics.pro",
        "labs.inlogics.pro",
        "mail.inlogics.pro",
        "monitor.inlogics.pro",
        "monitoring.inlogics.pro",
        "moov.inlogics.pro",
        "office.inlogics.pro",
        "soulga.inlogics.pro",
        "speedtest.inlogics.pro",
        "webmail.inlogics.pro",
        "www.inlogics.pro"
    ]
}
Tech stack
{
    "technologies": [
        "Plesk",
        "Nginx",
        "Google Font API",
        "HSTS",
        "Open Graph"
    ]
}
Page links
{
    "external": [
        "https://www.inlogics.pro/"
    ],
    "external_count": 1,
    "internal_count": 7
}
HTTP headers
{
    "headers": {
        "server": "nginx",
        "content-type": "text/html",
        "x-powered-by": "PleskLin",
        "strict-transport-security": "max-age=15768000; includeSubDomains"
    }
}

Questions about inlogics.pro

Is inlogics.pro legit?

No. PhishDestroy classifies inlogics.pro as a blocklisted domain (risk: critical, 81/100); it was first detected on 2026-10-22. VirusTotal: 4/92 engines flag it. Treat the site as unsafe.

Is inlogics.pro safe to connect a wallet?

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

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

Primary capture 1 / 10
SourcePrimary capture
Recorded2026-10-22 13:04 UTC
StateStored capture
HTTP status at archiveHTTP 200
Final URLhttps://inlogics.pro/front/pt/
Position1 / 10
Open capture Wayback Download

Domain details

Domain
IP Reputation abuse score 78/100 50 reports Email SpamPort ScanHackingSpoofingBrute-ForceExploited Host checked Oct 22, 2026
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar OVH SAS
Abuse contactabuse@ovh.net
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for inlogics.pro →
RegistrationCreated Sep 29, 2020 — Expires Sep 29, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 22, 2026
DOM Analysisanalyzed Oct 22, 2026score 81/100
Submitted URLhttp://inlogics.pro/front/pt
Favicon Hash
Case ID
Observed page title
inLogics — Conseil Datacenter, Cybersécurité & Infrastructures Critiques en Afrique
TLS Certificate
Issued by Let's Encrypt / YR2 · stored validity ends in 82 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
196.28.247.94
Network ASN
AS25543
Organization
Onatel Burkina Faso
Observed location
Bobo-Dioulasso, BF
Server header
nginx

Nameservers 2

  • amber.ns.cloudflare.com
  • john.ns.cloudflare.com

Mail routing 3 MX records

  • mx1.mail.ovh.netpriority 1
  • mx3.mail.ovh.netpriority 100
  • mx2.mail.ovh.netpriority 5

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR2
Valid from
2026-10-15 09:24:54
Valid until
2027-01-13 09:24:53
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint1dc86cc0f84933edf80a6f3e99983291f9c2c23681b9764dd4b8f0277caf745a
Certificate names · 2 SANs
  • inlogics.pro
  • www.inlogics.pro

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

viewdns.info · 196.28.247.94rapiddns.io
Recorded subdomains15

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • apitest.inlogics.proDomain record
  • cloud.inlogics.proDomain record
  • elearning.ifrisse.inlogics.proDomain record
  • gw.inlogics.proDomain record
  • ifrisse.inlogics.proDomain record
  • labs.inlogics.proDomain record
  • mail.inlogics.proDomain record
  • monitor.inlogics.proDomain record
  • monitoring.inlogics.proDomain record
  • moov.inlogics.proDomain record
  • office.inlogics.proDomain record
  • soulga.inlogics.proDomain record
  • speedtest.inlogics.proDomain record
  • webmail.inlogics.proDomain record
  • www.inlogics.proDomain record

The original observation time is not recorded for these hostnames.

Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

4 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 4 detections
CRDF
DNS8
Gridinsoft
SOCRadar
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of inlogics.pro · checked Oct 22, 2026

93
Good
Performance
FCP
2.6s
First Contentful Paint
LCP
2.6s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.84s
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://inlogics.pro/front/pt
Final URL: https://inlogics.pro/front/pt/
Banco CTT - Iniciar sessão
Response
HTTP 200
HTML body
9.4 KB
Compressed
3.7 KB
Links
3 internal · 0 external
Detected technologies
nginx
Selected response headers
Server: nginx
Content-Type: text/html
X-Powered-By: PleskLin
Security headers present
Strict-Transport-Security
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 10
Accept-Ranges
bytes
Connection
keep-alive
Content-Length
9582
Content-Type
text/html
Date
Thu, 22 Oct 2026 13:00:40 GMT
Etag
"6acd6c1f-256e"
Last-Modified
Mon, 12 Oct 2026 23:24:15 GMT
Server
nginx
Strict-Transport-Security
max-age=15768000; includeSubDomains
X-Powered-By
PleskLin

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

Archived
Registration & observation details1

Availability observations

Last reachable observation

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Stored observation history1

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

  1. Availability monitor · First collection record

    Reachable

Recorded activity

6 entries
  1. AlienVault OTX

    4 community references

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. VirusTotal

    4/92 engine detections

    View source
  4. Abuse report sent

    PD-20261022-F66204

    abuse@ovh.net
  5. URLScan

    Page captured

    View source
  6. Added to PhishDestroy

    inlogics.pro

    View source

Check for cloaking

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

inlogics.pro

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 4 det. ChainPatrol URLQuery Report stored SSL Labs Stored certificate dates valid CF Radar Open report OTX 4 refs WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261022-F66204 Recipient: abuse@ovh.net
PDF notice generated
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

6 evidence signal groups linked 1 stored notification records Last known active
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 inlogics.pro)
  • 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/inlogics.pro"
  title="PhishDestroy threat report for inlogics.pro"
  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>