Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 18. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
officialwikipedia.org favicon

officialwikipedia.org

In short

PhishDestroy describes the connection reset error page captured at officialwikipedia.org, where the browser reported ERR_CONNECTION_RESET.

“Official Wiki Knowledge Services Pty Ltd — Digital information and online publishing solutions across Australia”

Review the evidence
Registrar
United StatesGoDaddy
Resolved IP
Netherlands154.83.186.199Datagear LLP
Registered
Dec 16, 2025
First observed
Nov 1, 2026
PhishDestroy assessment Critical
95/100
Evidence score
First observed Nov 1, 2026 08:18 UTC · PhishDestroy
Risk signals
VirusTotal detections: 18/92
VirusTotal
18 / 92
engine detections ·
OTX
1
community references
URLScan
Malicious
engine verdict · score 79
Page captures
5
open gallery
Domain age
319 days
registered 2025-12-16 according to WHOIS
OTX: 1 ref Nov 1, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy describes the connection reset error page captured at officialwikipedia.org, where the browser reported ERR_CONNECTION_RESET.

Critical
VirusTotal
18 / 92
Hosting
Netherlands154.83.186.199Datagear LLP
Registrar
United StatesGoDaddy
Registered
Dec 16, 2025
OTX
1 community ref
Page captures
5
Page captures Source results Registration record

PhishDestroy analysis, reviewed version

The captured page at officialwikipedia.org is a browser error screen rather than a website interface, showing the heading "This site can't be reached" with the explanation that the connection was reset. It displays the error code ERR_CONNECTION_RESET alongside suggestions to check the connection, proxy and firewall, and offers Details and Reload buttons as the only interactions.

The stored VirusTotal domain result reports 18 detections out of 92 engines. DNS8 reported "suspicious"; ESET reported "suspicious".

Source evidenceVirusTotal 18 / 92 · OTX 1 references 7 sources

VirusTotal

18 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 12 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
43
Malicious
15
Suspicious
3
Undetected
31

Vendor labels

DNS8
suspicious
ESET
suspicious
VIPRE
malware
G-Data
phishing
Lionic
phishing
Sophos
phishing
CyRadar
phishing
Webroot
malicious
Fortinet
phishing
SOCRadar
phishing
Kaspersky
phishing
Seclookup
malicious
Gridinsoft
suspicious
BitDefender
phishing
Chong Lua Dao
malicious
alphaMountain.ai
phishing
Yandex Safebrowsing
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Categories

alphaMountain.ai
Phishing (alphaMountain.ai)

Created

Updated

First seen

DNS records

  • TTL, seconds
    21600
    Type
    NS
    Value
    ns1.mysecurecloudhost.com
  • TTL, seconds
    21600
    Type
    SOA
    Responsible mailbox
    servers.mysecurecloudhost.com
    Value
    ns1.mysecurecloudhost.com
  • TTL, seconds
    21600
    Type
    NS
    Value
    ns2.mysecurecloudhost.com
  • TTL, seconds
    21600
    Type
    NS
    Value
    ns3.mysecurecloudhost.com
  • TTL, seconds
    7200
    Type
    MX
    Value
    officialwikipedia.org
    Priority
    0
  • TTL, seconds
    7200
    Type
    TXT
    Value
    v=spf1 +a +mx +ip4:192.250.229.176 include:spf.mysecurecloudhost.com ~all
  • TTL, seconds
    21600
    Type
    NS
    Value
    ns4.mysecurecloudhost.com
  • TTL, seconds
    7200
    Type
    A
    Value
    154.83.186.199

DNS records observed

JARM fingerprint

2ad2ad0002ad2ad00042d42d00000000f78d2dc0ce6e5bbc5b8149a4872356

Certificate

Subject alternative names
  • officialwikipedia.org
Issuer
Let's Encrypt / YR1
Serial
665c8bf351cc0d34c40b8318b31aa245f57
SHA-256
6719204981332c16688974d8ed3d316da7694b0e7679fd2daa90557415edb1d4
Subject
officialwikipedia.org
Valid until
Valid from

Registry data (RDAP)

Status
  • client delete prohibited
  • client renew prohibited
  • client transfer prohibited
  • client update prohibited
Registry events
Expiration
Last changed
Registration
Last RDAP database update
Registrar
GoDaddy.com, LLC
Registrar IANA ID
146
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 43,
    "malicious": 15,
    "suspicious": 3,
    "undetected": 31
}
Vendor labels
{
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "malware",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "BitDefender": "phishing",
    "Chong Lua Dao": "malicious",
    "alphaMountain.ai": "phishing",
    "Yandex Safebrowsing": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
Created
2025-12-16T00:00:00Z
Updated
2025-12-17T00:00:00Z
First seen
2025-12-19T16:05:33Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns1.mysecurecloudhost.com"
    },
    {
        "ttl": 21600,
        "type": "SOA",
        "rname": "servers.mysecurecloudhost.com",
        "value": "ns1.mysecurecloudhost.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns2.mysecurecloudhost.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns3.mysecurecloudhost.com"
    },
    {
        "ttl": 7200,
        "type": "MX",
        "value": "officialwikipedia.org",
        "priority": 0
    },
    {
        "ttl": 7200,
        "type": "TXT",
        "value": "v=spf1 +a +mx +ip4:192.250.229.176 include:spf.mysecurecloudhost.com ~all"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns4.mysecurecloudhost.com"
    },
    {
        "ttl": 7200,
        "type": "A",
        "value": "154.83.186.199"
    }
]
Dns at
2026-10-19T23:58:16Z
Jarm
2ad2ad0002ad2ad00042d42d00000000f78d2dc0ce6e5bbc5b8149a4872356
Certificate
{
    "san": [
        "officialwikipedia.org"
    ],
    "issuer": "Let's Encrypt / YR1",
    "serial": "665c8bf351cc0d34c40b8318b31aa245f57",
    "sha256": "6719204981332c16688974d8ed3d316da7694b0e7679fd2daa90557415edb1d4",
    "subject": "officialwikipedia.org",
    "valid_to": "2026-10-22T23:12:53Z",
    "valid_from": "2026-07-24T23:12:54Z"
}
Registry data
{
    "status": [
        "client delete prohibited",
        "client renew prohibited",
        "client transfer prohibited",
        "client update prohibited"
    ],
    "events": {
        "expiration": "2026-12-16T09:42:07Z",
        "last changed": "2026-08-12T08:00:09Z",
        "registration": "2025-12-16T09:42:07Z",
        "last update of RDAP database": "2026-10-17T23:45:53Z"
    },
    "registrar": "GoDaddy.com, LLC",
    "registrar_iana_id": "146"
}
Separate source record · 15 malicious + 3 suspicious / 92 · 2026-10-19 23:53:00 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-19T23:53:00Z
fetched_at
2026-11-01T08:31:44Z
stats
{"timeout":0,"harmless":43,"malicious":15,"suspicious":3,"undetected":31}

URLScan

Malicious · engine verdict · score 79

SHA-256 568f159d06fdd4ca9354687eb0dca2e5dfb3243e9a7f526de1c7f1d1bd5774af

Open report
URLScanOriginal source recordObserved: 18 fields

Observed: · Retrieved:

Report ID

01a1963d-a407-724f-a167-06f4d2b2c579

Final URL

https://officialwikipedia.org/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://officialwikipedia.org/
    From
    http://officialwikipedia.org/
    Status
    307

IP address

154.83.186.199

Contacted IP addresses

  • 154.83.186.199

Autonomous systems (ASN)

  • 200758

Server countries

  • NL

Document hash

568f159d06fdd4ca9354687eb0dca2e5dfb3243e9a7f526de1c7f1d1bd5774af

TLS session and certificate

Subject alternative names
  • officialwikipedia.org
Cipher
AES_256_GCM
Issuer
YR1
Subject
officialwikipedia.org
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

319

Registered domain age, days

319

Certificate age, days

99

Certificate validity, days

89

Page requests

3

Provider verdicts

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

HTTP headers

Server
nginx/1.30.0
Content-type
text/html; charset=UTF-8
Original source fields · JSON
Uuid
01a1963d-a407-724f-a167-06f4d2b2c579
Final url
https://officialwikipedia.org/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://officialwikipedia.org/",
        "from": "http://officialwikipedia.org/",
        "status": 307
    }
]
Ip
154.83.186.199
Contacted IP addresses
[
    "154.83.186.199"
]
Asns
[
    "200758"
]
Countries
[
    "NL"
]
Document hash
568f159d06fdd4ca9354687eb0dca2e5dfb3243e9a7f526de1c7f1d1bd5774af
Tls
{
    "san": [
        "officialwikipedia.org"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "YR1",
    "subject": "officialwikipedia.org",
    "protocol": "TLS 1.3",
    "valid_to": "2026-10-22T23:12:53Z",
    "valid_from": "2026-07-24T23:12:54Z"
}
Domain age days
319
Apex age days
319
Tls age days
99
Tls valid days
89
Requests
3
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 79,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "nginx/1.30.0",
    "content-type": "text/html; charset=UTF-8"
}
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
01a1963d-a407-724f-a167-06f4d2b2c579
score
null
malicious
null
result_at
null
enriched_at
2026-11-01T09:10:39Z
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":"2026-11-01 10:10:39"}
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: 10 fields

Observed: · Retrieved:

Report ID

4a3caa4b-5aca-4aeb-bb2e-145680fb2420

Final URL

https://officialwikipedia.org/

Navigation history

  • URL
    https://officialwikipedia.org/
    Status
    0

DOM structure hash

0be15d34945b061b4688e4c7a258d982bf21eeec94f047738c21f26a19145958

Domain risk categories

  • Malware
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    officialwikipedia.org
    Type
    A
    Value
    154.83.186.199

DNSSEC valid

No

Verdict

Tags
  • malware
Malicious
Yes
Categories
  • malware

Registration record

Registrar
GoDaddy.com, LLC
Registered
Updated
Expires
Nameservers
  • ns1.mysecurecloudhost.com
  • ns2.mysecurecloudhost.com
  • ns3.mysecurecloudhost.com
  • ns4.mysecurecloudhost.com
Original source fields · JSON
Uuid
4a3caa4b-5aca-4aeb-bb2e-145680fb2420
Final url
https://officialwikipedia.org/
History
[
    {
        "url": "https://officialwikipedia.org/",
        "status": 0
    }
]
DOM structure hash
0be15d34945b061b4688e4c7a258d982bf21eeec94f047738c21f26a19145958
Domain risks
[
    "Malware",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "officialwikipedia.org",
        "type": "A",
        "value": "154.83.186.199"
    }
]
Dnssec valid
false
Verdict
{
    "tags": [
        "malware"
    ],
    "malicious": true,
    "categories": [
        "malware"
    ]
}
Registration record
{
    "registrar": "GoDaddy.com, LLC",
    "created": "2025-12-16T09:42:07Z",
    "updated": "2026-08-12T08:00:09Z",
    "expires": "2026-12-16T09:42:07Z",
    "nameservers": [
        "ns1.mysecurecloudhost.com",
        "ns2.mysecurecloudhost.com",
        "ns3.mysecurecloudhost.com",
        "ns4.mysecurecloudhost.com"
    ]
}

Google Safe Browsing

No threat flag

Open report

PhishDestroy DOM

10 / 100 · heuristic score · 1 brand reference · 0 classifications

Open report
Separate monitor score · 10 / 100 · 2026-11-01T08:49:27Z

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

record_source
domain_monitor.dom_analysis
heuristic_score
10
analyzed_at
2026-11-01T08:49:27Z
source_timestamp
2026-11-01 09:49:27
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

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
officialwikipedia.org connection reset error page capture
ai_description
PhishDestroy describes the connection reset error page captured at officialwikipedia.org, where the browser reported ERR_CONNECTION_RESET.
ai_summary
The captured page at officialwikipedia.org is a browser error screen rather than a website interface, showing the heading "This site can't be reached" with the explanation that the connection was reset. It displays the error code ERR_CONNECTION_RESET alongside suggestions to check the connection, proxy and firewall, and offers Details and Reload buttons as the only interactions. The stored VirusTotal domain result reports 18 detections out of 92 engines. DNS8 reported "suspicious"; ESET reported "suspicious".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-11-01 09:39:21
revision
d95f0c350009d785b6782aa4d2cf604a14e65b8b375b601e77174f04f36253ac
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: 14 fields

Mail configuration

MX records
  • officialwikipedia.org
SPF record
v=spf1 +a +mx +ip4:192.250.229.176 include:spf.mysecurecloudhost.com ~all
DKIM
  • default
DMARC
Yes
DKIM key size, bits
2048
SPF lookups
5

CAA records

Domain
officialwikipedia.org

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

Last observation
First observation
Recorded changes
0
Archived days
1
Average page size, bytes
5877

Trackers

Requests
2

TLS connection

ALPN
http/1.1
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
No
Forward secrecy
Yes

Ports

Open ports
  • 21
  • 22
  • 25
  • 53
  • 80
  • 110
  • 143
  • 443
  • 587
  • 993
  • 995
  • 8888

DNS servers

Nameservers
  • IP address
    76.223.26.245
    Host
    ns3.mysecurecloudhost.com
  • IP address
    75.2.118.134
    Host
    ns2.mysecurecloudhost.com
  • IP address
    13.248.158.180
    Host
    ns1.mysecurecloudhost.com
  • IP address
    99.83.147.209
    Host
    ns4.mysecurecloudhost.com
DNS zone
officialwikipedia.org

Location

IP address
154.83.186.199
ASN
200758
Organization
Datagear LLP
City
Amsterdam
Country
NL

TLS certificate

Issuer
Let's Encrypt / YR1
Subject
officialwikipedia.org

DNS records

A
  • 154.83.186.199
MX
  • Mail server
    officialwikipedia.org
    Priority
    0
NS
  • ns4.mysecurecloudhost.com
  • ns3.mysecurecloudhost.com
  • ns2.mysecurecloudhost.com
  • ns1.mysecurecloudhost.com
SOA
Primary nameserver
ns1.mysecurecloudhost.com
Hostmaster
servers.mysecurecloudhost.com
Serial
2026052200
Refresh, seconds
3600
Retry, seconds
1800
Expiry, seconds
1209600
Minimum TTL, seconds
86400
TXT
  • v=spf1 +a +mx +ip4:192.250.229.176 include:spf.mysecurecloudhost.com ~all

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

IP lookup

IP address
154.83.186.199
IP version
4

Registration record

Registrar
GoDaddy.com, LLC
Registered
Updated
Expires
Status
  • clientDeleteProhibited https://icann.org/epp
  • clientRenewProhibited https://icann.org/epp
  • clientTransferProhibited https://icann.org/epp
  • clientUpdateProhibited https://icann.org/epp
Nameservers
  • ns1.mysecurecloudhost.com
  • ns2.mysecurecloudhost.com
  • ns3.mysecurecloudhost.com
  • ns4.mysecurecloudhost.com
Original source fields · JSON
Mail configuration
{
    "mx": [
        "officialwikipedia.org"
    ],
    "spf": "v=spf1 +a +mx +ip4:192.250.229.176 include:spf.mysecurecloudhost.com ~all",
    "dkim": [
        "default"
    ],
    "dmarc": true,
    "dkim_bits": 2048,
    "spf_lookups": 5
}
Caa records
{
    "domain": "officialwikipedia.org"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-11-01T08:22:27Z",
    "first": "2026-11-01T08:22:27Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 5877
}
Trackers
{
    "requests": 2
}
TLS connection
{
    "alpn": "http/1.1",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": false,
    "forward_secrecy": true
}
Ports
{
    "open": [
        21,
        22,
        25,
        53,
        80,
        110,
        143,
        443,
        587,
        993,
        995,
        8888
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "76.223.26.245",
            "host": "ns3.mysecurecloudhost.com"
        },
        {
            "ip": "75.2.118.134",
            "host": "ns2.mysecurecloudhost.com"
        },
        {
            "ip": "13.248.158.180",
            "host": "ns1.mysecurecloudhost.com"
        },
        {
            "ip": "99.83.147.209",
            "host": "ns4.mysecurecloudhost.com"
        }
    ],
    "zone": "officialwikipedia.org"
}
Location
{
    "ip": "154.83.186.199",
    "asn": "200758",
    "org": "Datagear LLP",
    "city": "Amsterdam",
    "country": "NL"
}
Ssl
{
    "issuer": "Let's Encrypt / YR1",
    "subject": "officialwikipedia.org"
}
DNS records
{
    "A": [
        "154.83.186.199"
    ],
    "MX": [
        "{\"exchange\": \"officialwikipedia.org\", \"priority\": 0}"
    ],
    "NS": [
        "ns4.mysecurecloudhost.com",
        "ns3.mysecurecloudhost.com",
        "ns2.mysecurecloudhost.com",
        "ns1.mysecurecloudhost.com"
    ],
    "SOA": "{\"nsname\": \"ns1.mysecurecloudhost.com\", \"hostmaster\": \"servers.mysecurecloudhost.com\", \"serial\": 2026052200, \"refresh\": 3600, \"retry\": 1800, \"expire\": 1209600, \"minttl\": 86400}",
    "TXT": [
        "v=spf1 +a +mx +ip4:192.250.229.176 include:spf.mysecurecloudhost.com ~all"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Get ip
{
    "ip": "154.83.186.199",
    "family": 4
}
Registration record
{
    "registrar": "GoDaddy.com, LLC",
    "created": "2025-12-16T09:42:07Z",
    "updated": "2026-08-12T08:00:09Z",
    "expires": "2026-12-16T09:42:07Z",
    "status": [
        "clientDeleteProhibited https://icann.org/epp",
        "clientRenewProhibited https://icann.org/epp",
        "clientTransferProhibited https://icann.org/epp",
        "clientUpdateProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "ns1.mysecurecloudhost.com",
        "ns2.mysecurecloudhost.com",
        "ns3.mysecurecloudhost.com",
        "ns4.mysecurecloudhost.com"
    ]
}

Questions about officialwikipedia.org

Is officialwikipedia.org legit?

PhishDestroy describes the connection reset error page captured at officialwikipedia.org, where the browser reported ERR_CONNECTION_RESET.

Is officialwikipedia.org safe to connect a wallet?

This report does not record which wallet requests officialwikipedia.org 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 officialwikipedia.org?

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 · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 5 captures

Cloudflare Radar 1 / 5 Used in the analysis Source file SHA-256: a5db7ab655d3900bfb2bf44f8483ca7ce06fc6f795376f14b777be50f1f0af62 SHA-256 of the prepared copy given to the model: 9b2bd0fda53e1c8aebf8b218f9819433925b9342fe39730c23b507fc9285f8eb
SourceCloudflare Radar
Recorded
StateStored capture
Final URLhttps://officialwikipedia.org/
Position1 / 5
Open capture Source Report Wayback Download
All capture links and hashes (5)

Domain details

Domain
IP Reputation Netherlands154.83.186.199 abuse score 0/100 0 reports checked Nov 1, 2026
Registrar GoDaddy US(US)
Abuse contactabuse@godaddy.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for officialwikipedia.org →
RegistrationCreated Dec 16, 2025 (319d) — Expires Dec 16, 2026
WHOIS statusclientDeleteProhibitedclientRenewProhibitedclientTransferProhibitedclientUpdateProhibited
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedNov 1, 2026
DOM Analysisanalyzed Nov 1, 2026score 10/1001 brand signal
Submitted URLhttp://officialwikipedia.org/
Observed page title
Official Wiki Knowledge Services Pty Ltd — Digital information and online publishing solutions across Australia
Automated brand references
Across
TLS Certificate
Issued by E7

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Netherlands154.83.186.199
Network ASN
AS200758
AS name
ORG-DL626-RIPE Datagear LLP, GB
Organization
Datagear LLP
Observed location
NetherlandsAmsterdam, NL
Server header
nginx/1.26.3

Nameservers 4

  • ns1.mysecurecloudhost.com
  • ns2.mysecurecloudhost.com
  • ns3.mysecurecloudhost.com
  • ns4.mysecurecloudhost.com

SOA

  • nsname: ns1.mysecurecloudhost.com
  • hostmaster: servers.mysecurecloudhost.com
  • serial: 2026052200
  • refresh: 3600
  • retry: 1800
  • expire: 1209600
  • minttl: 86400

Mail routing 1 MX record

  • officialwikipedia.orgpriority 0

Location describes the IP network.

TLS certificate

Issuer
E7
Valid from
2026-05-06 08:48:14
Valid until
2026-08-04 08:48:13
Hostname coverage
Stored certificate expired or unverified
Validity
Stored certificate expired
Collection source
PhishDestroy collector
Certificate fingerprint6719204981332c16688974d8ed3d316da7694b0e7679fd2daa90557415edb1d4
Certificate names · 1 SAN
  • officialwikipedia.org

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

viewdns.info · 154.83.186.199rapiddns.io
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
Chong Lua Dao
CyRadar
DNS8
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
Seclookup
SOCRadar
Sophos
VIPRE
Webroot
Yandex Safebrowsing

Archived Evidence

Wayback Machine Snapshot
View Archive
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://officialwikipedia.org/
Official Wiki Knowledge Services Pty Ltd — Digital information and online publishing solutions across Australia
Official Wiki Knowledge Services Pty Ltd — Digital information and online publishing solutions across Australia
Response
HTTP 200
HTML body
24.3 KB
Compressed
5.1 KB
Links
20 internal · 0 external
Detected technologies
nginx
Selected response headers
Server: nginx/1.30.0
Content-Type: text/html; charset=UTF-8
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 7
Connection
keep-alive
Content-Encoding
gzip
Content-Length
5248
Content-Type
text/html; charset=UTF-8
Date
Sun, 01 Nov 2026 08:26:17 GMT
Server
nginx/1.30.0
Vary
Accept-Encoding

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

Archived

Captured network requests

Network requests: 3 SHA-256 hashes: 3 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:37 UTC.

Open this scan on URLScan 01a1963d-a407-724f-a167-06f4d2b2c579 ↗

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. Domain monitor · First collection record

    Reachable

All retained availability observations1

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
    stale
    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
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

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

Recorded events: 10. 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
    officialwikipedia.org detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · OTX Community References · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 8 of 8
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 79
  • 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
  • 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 Recorded: 1 of 1

Recorded activity

5 entries
  1. URLScan

    Page captured

    View source
  2. AlienVault OTX

    1 community references

    View source
  3. Wayback Machine

    Page archived

    View source
  4. Added to PhishDestroy

    officialwikipedia.org

    View source
  5. 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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Check for cloaking

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

officialwikipedia.org

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 18 det. ChainPatrol URLQuery SSL Labs Stored certificate expired or unverified CF Radar Open report OTX 1 ref WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

4 evidence signal groups linked Unverified
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.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
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.

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

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 officialwikipedia.org)
  • 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

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.

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