Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 13/92 engines flagged. malicious: 10. suspicious: 3. Analysis time (as stored): 2026-10-18T17:45:13Z. Retrieved (as stored): 2026-11-01T22:42:40Z. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
pgeebo02.wp-box.com favicon

pgeebo02.wp-box.com

In short

The captured page at pgeebo02.wp-box.com shows a WordPress-branded notice on a solid blue background. The WordPress logo and wordmark appear above a short message explaining that the site does not have a certificate and asking the visitor to contact technical support to obtain one. No form, button, or other interactive control is visible, so the page's only interaction is reading the notice and following its instruction to reach technical support.

“WordPress”

Review the evidence
Registrar
IndiaPDR
Resolved IP
Estonia109.94.209.151Arvid Logicum OU
Registered
Nov 27, 2025
First observed
Nov 1, 2026
PhishDestroy assessment Critical
99/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 13/92
VirusTotal
13 / 92
engine detections ·
URLScan
Malicious
engine verdict · score 63
Page captures
4
open gallery
Domain age
340 days
registered 2025-11-27 according to WHOIS · source data differ
Nov 1, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded pgeebo02.wp-box.com on 2026-11-01. Stored VirusTotal result: 13/92 engines flagged. malicious: 10. suspicious: 3. Analysis time (as stored): 2026-10-18T17:45:13Z. Retrieved (as stored): 2026-11-01T22:42:40Z. Risk: critical (99/100). Registrar: PDR. Status: Last known active. Hosting: Arvid Logicum OU. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
13 / 92
Hosting
Estonia109.94.209.151Arvid Logicum OU
Registrar
IndiaPDR
Registered
Nov 27, 2025
Page captures
4
Page captures Source results Registration record

Capture recorded with this analysis · Cloudflare Radar · 2026-11-01T22:42:44Z
SHA-256: 65d98d55dd886250f8740c9ca4695b2704ef68be3d3a0ccb5620446ae8d04ba3

PhishDestroy analysis, reviewed version

The captured page at pgeebo02.wp-box.com shows a WordPress-branded notice on a solid blue background. The WordPress logo and wordmark appear above a short message explaining that the site does not have a certificate and asking the visitor to contact technical support to obtain one. No form, button, or other interactive control is visible, so the page's only interaction is reading the notice and following its instruction to reach technical support.

The stored VirusTotal domain result reports 13 detections out of 92 engines. CRDF reported "malicious"; DNS8 reported "suspicious".

Source evidenceVirusTotal 13 / 92 8 sources

VirusTotal

13 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
47
Malicious
10
Suspicious
3
Undetected
32

Vendor labels

CRDF
malicious
DNS8
suspicious
ESET
suspicious
VIPRE
phishing
G-Data
phishing
Lionic
phishing
Sophos
phishing
Fortinet
phishing
SOCRadar
phishing
Seclookup
malicious
BitDefender
phishing
alphaMountain.ai
suspicious
Forcepoint ThreatSeeker
phishing

Reputation score

0

Tags

  • dga

Created

Updated

First seen

DNS records

  • TTL, seconds
    3600
    Type
    A
    Value
    109.94.209.151

DNS records observed

JARM fingerprint

3fd3fd0003fd3fd21c42d42d000000c1fc3d47ef34532079f4922fcb05ef65

Certificate

Subject alternative names
  • pgeebo02.wp-box.com
  • www.pgeebo02.wp-box.com
Issuer
Let's Encrypt / YR1
Serial
641004e58e0b9f961c329566be7988c6134
SHA-256
187ae33d37f535ce6af4c404bcdbe7c1d912302e9c38c5a7bbe79bebdf9fe5b3
Subject
pgeebo02.wp-box.com
Valid until
Valid from
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 47,
    "malicious": 10,
    "suspicious": 3,
    "undetected": 32
}
Vendor labels
{
    "CRDF": "malicious",
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Seclookup": "malicious",
    "BitDefender": "phishing",
    "alphaMountain.ai": "suspicious",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
Created
2025-11-27T00:00:00Z
Updated
2025-11-27T00:00:00Z
First seen
2026-08-27T20:28:00Z
DNS records
[
    {
        "ttl": 3600,
        "type": "A",
        "value": "109.94.209.151"
    }
]
Dns at
2026-08-28T04:59:41Z
Jarm
3fd3fd0003fd3fd21c42d42d000000c1fc3d47ef34532079f4922fcb05ef65
Certificate
{
    "san": [
        "pgeebo02.wp-box.com",
        "www.pgeebo02.wp-box.com"
    ],
    "issuer": "Let's Encrypt / YR1",
    "serial": "641004e58e0b9f961c329566be7988c6134",
    "sha256": "187ae33d37f535ce6af4c404bcdbe7c1d912302e9c38c5a7bbe79bebdf9fe5b3",
    "subject": "pgeebo02.wp-box.com",
    "valid_to": "2026-11-25T19:05:51Z",
    "valid_from": "2026-08-27T19:05:52Z"
}
Separate collector summary

This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.

source
VirusTotal
scope
unknown
result_state
observed
numerator
13
denominator
92
malicious
null
suspicious
null
vendors
["alphaMountain.ai","BitDefender","CRDF","DNS8","ESET","Forcepoint ThreatSeeker","Fortinet","G-Data","Lionic","Seclookup","SOCRadar","Sophos","VIPRE"]
observed_at
2026-10-18 17:45:13
checked_at
2026-11-01 23:42:40
fetched_at
2026-11-01 22:42:41
time_basis
as stored; legacy timezone not established

Cloudflare Radar

Malicious

Open report
Cloudflare RadarOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Report ID

f5715e64-df7a-4f2c-a413-ef1c7b019c17

Final URL

https://pgeebo02.wp-box.com/

HTTP response

200

Navigation history

  • URL
    https://pgeebo02.wp-box.com/
    Status
    200

DOM structure hash

880c7ccd7a4e604a9b1ac2895dc3b1bfea18fc403b748d290dd58abcc9549d42

Document hash

e15ec883070a09245c61949e35c46a83a21fd89c3a90e79e3bab9409b78fffb9

Domain risk categories

  • Malware
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    pgeebo02.wp-box.com
    Type
    A
    Value
    109.94.209.151

DNSSEC valid

No

IP address

127.0.1.12

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

Verdict

Tags
  • malware
Malicious
Yes
Categories
  • malware

Registration record

Registrar
PDR Ltd. d/b/a PublicDomainRegistry.com
Registered
Updated
Expires
Nameservers
  • ns1.ns-host.com
  • ns2.ns-host.com
Original source fields · JSON
Uuid
f5715e64-df7a-4f2c-a413-ef1c7b019c17
Final url
https://pgeebo02.wp-box.com/
Status
200
History
[
    {
        "url": "https://pgeebo02.wp-box.com/",
        "status": 200
    }
]
DOM structure hash
880c7ccd7a4e604a9b1ac2895dc3b1bfea18fc403b748d290dd58abcc9549d42
Document hash
e15ec883070a09245c61949e35c46a83a21fd89c3a90e79e3bab9409b78fffb9
Domain risks
[
    "Malware",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "pgeebo02.wp-box.com",
        "type": "A",
        "value": "109.94.209.151"
    }
]
Dnssec valid
false
Ip
127.0.1.12

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

Verdict
{
    "tags": [
        "malware"
    ],
    "malicious": true,
    "categories": [
        "malware"
    ]
}
Registration record
{
    "registrar": "PDR Ltd. d/b/a PublicDomainRegistry.com",
    "created": "2025-11-27T09:07:41Z",
    "updated": "2026-10-30T19:02:27Z",
    "expires": "2027-11-27T09:07:41Z",
    "nameservers": [
        "ns1.ns-host.com",
        "ns2.ns-host.com"
    ]
}

URLScan

Malicious · engine verdict · score 63

SHA-256 4caedf02a6c217918dad5cd851d9591cd95078fbccb11d76d0dfc45d574baa1f

Open report
URLScanOriginal source recordObserved: 20 fields

Observed: · Retrieved:

Report ID

01a1992a-63e1-737b-98a7-bf2333e35cc8

Final URL

https://pgeebo02.wp-box.com/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://pgeebo02.wp-box.com/
    From
    http://pgeebo02.wp-box.com/
    Status
    307

IP address

109.94.209.151

Reverse DNS (PTR)

develop-wp.com

Contacted domains

  • binar-design.biz

Contacted IP addresses

  • 172.67.129.3
  • 109.94.209.151

Autonomous systems (ASN)

  • 13335
  • 202376

Server countries

  • EE

Document hash

e15ec883070a09245c61949e35c46a83a21fd89c3a90e79e3bab9409b78fffb9

TLS session and certificate

Subject alternative names
  • *.wp-box.com
Cipher
AES_128_GCM
Issuer
YE1
Subject
*.wp-box.com
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

66

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

Registered domain age, days

1355

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

Certificate age, days

12

Certificate validity, days

89

Page requests

4

Provider verdicts

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

HTTP headers

Server
nginx
Content-type
text/html; charset=UTF-8
Original source fields · JSON
Uuid
01a1992a-63e1-737b-98a7-bf2333e35cc8
Final url
https://pgeebo02.wp-box.com/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://pgeebo02.wp-box.com/",
        "from": "http://pgeebo02.wp-box.com/",
        "status": 307
    }
]
Ip
109.94.209.151
Ptr
develop-wp.com
Contacted domains
[
    "binar-design.biz"
]
Contacted IP addresses
[
    "172.67.129.3",
    "109.94.209.151"
]
Asns
[
    "13335",
    "202376"
]
Countries
[
    "EE"
]
Document hash
e15ec883070a09245c61949e35c46a83a21fd89c3a90e79e3bab9409b78fffb9
Tls
{
    "san": [
        "*.wp-box.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE1",
    "subject": "*.wp-box.com",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-18T13:46:18Z",
    "valid_from": "2026-10-20T13:46:19Z"
}
Domain age days
66

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

Apex age days
1355

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

Tls age days
12
Tls valid days
89
Requests
4
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 63,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "nginx",
    "content-type": "text/html; charset=UTF-8"
}
Separate monitor record · 2026-11-02 04:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a1992a-63e1-737b-98a7-bf2333e35cc8
score
0
malicious
false
result_at
2026-11-02T04:30:16Z
enriched_at
2026-11-02T09:11:40Z
source_timestamps
{"urlscan_result_at":"2026-11-02 05:30:16","urlscan_enriched_at":"2026-11-02 10:11:40"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

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

Open report
Separate monitor score · 10 / 100 · 2026-11-01T22:44:06Z

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-01T22:44:06Z
source_timestamp
2026-11-01 23:44:06
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
pgeebo02.wp-box.com WordPress certificate notice page
ai_description
PhishDestroy describes pgeebo02.wp-box.com, a captured WordPress page stating that the site has no certificate and asking visitors to contact technical support.
ai_summary
The captured page at pgeebo02.wp-box.com shows a WordPress-branded notice on a solid blue background. The WordPress logo and wordmark appear above a short message explaining that the site does not have a certificate and asking the visitor to contact technical support to obtain one. No form, button, or other interactive control is visible, so the page's only interaction is reading the notice and following its instruction to reach technical support. The stored VirusTotal domain result reports 13 detections out of 92 engines. CRDF reported "malicious"; DNS8 reported "suspicious".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-11-01 23:43:21
revision
8b4c2bf99e60c6278f61d1bcb0edee3b07f63596b4f09fa8ad1676c14c88ddab
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: 21 fields

CAA records

Domain
pgeebo02.wp-box.com

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
1131

Page title and metadata

Page title
WordPress

Trackers

Requests
3

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
152
TLS
54
Waiting
52
Connection
45
Download
0
Response time, ms
303

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

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

Carbon estimate

Bytes
1639
CO₂, grams
0.0001
Cleaner than, %
95

DNS servers

Nameservers
  • IP address
    109.94.209.18
    Host
    ns1.ns-host.com
  • IP address
    109.94.209.107
    Host
    ns2.ns-host.com
DNS zone
wp-box.com

Location

IP address
109.94.209.151
ASN
202376
Organization
Arvid Logicum OU
City
Tallinn
Country
EE

TLS certificate

Issuer
Let's Encrypt / YE1
Subject
*.wp-box.com

DNS records

A
  • 109.94.209.151

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

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
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
109.94.209.151
IP version
4

Redirects

Redirect chain
  • https://pgeebo02.wp-box.com

Registration record

Registrar
PDR Ltd. d/b/a PublicDomainRegistry.com
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • ns1.ns-host.com
  • ns2.ns-host.com

HTTP headers

Response headers
Server
nginx
Content-type
text/html; charset=UTF-8
Original source fields · JSON
Caa records
{
    "domain": "pgeebo02.wp-box.com"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-11-01T22:13:11Z",
    "first": "2026-11-01T22:13:11Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 1131
}
Page title and metadata
{
    "title": "WordPress"
}
Trackers
{
    "requests": 3
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 152,
        "tls": 54,
        "wait": 52,
        "connect": 45,
        "download": 0
    },
    "response_ms": 303
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        21,
        25,
        53,
        80,
        110,
        143,
        443,
        587,
        993,
        995
    ]
}
Carbon
{
    "bytes": 1639,
    "co2_grams": 0.0001,
    "cleaner_than": 95
}
Dns server
{
    "ns": [
        {
            "ip": "109.94.209.18",
            "host": "ns1.ns-host.com"
        },
        {
            "ip": "109.94.209.107",
            "host": "ns2.ns-host.com"
        }
    ],
    "zone": "wp-box.com"
}
Location
{
    "ip": "109.94.209.151",
    "asn": "202376",
    "org": "Arvid Logicum OU",
    "city": "Tallinn",
    "country": "EE"
}
Ssl
{
    "issuer": "Let's Encrypt / YE1",
    "subject": "*.wp-box.com"
}
DNS records
{
    "A": [
        "109.94.209.151"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "109.94.209.151",
    "family": 4
}
Redirects
{
    "chain": [
        "https://pgeebo02.wp-box.com"
    ]
}
Registration record
{
    "registrar": "PDR Ltd. d/b/a PublicDomainRegistry.com",
    "created": "2025-11-27T09:07:41Z",
    "updated": "2026-10-30T19:02:27Z",
    "expires": "2027-11-27T09:07:41Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "ns1.ns-host.com",
        "ns2.ns-host.com"
    ]
}
HTTP headers
{
    "headers": {
        "server": "nginx",
        "content-type": "text/html; charset=UTF-8"
    }
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Malware Security threats Malware
View full Cloudflare Radar report

Questions about pgeebo02.wp-box.com

Is pgeebo02.wp-box.com legit?

PhishDestroy rates pgeebo02.wp-box.com as critical risk (99/100) from the recorded evidence; it was first recorded on 2026-11-01. Stored VirusTotal result: 13/92 engines flagged. malicious: 10. suspicious: 3. Analysis time (as stored): 2026-10-18T17:45:13Z. Retrieved (as stored): 2026-11-01T22:42:40Z. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is pgeebo02.wp-box.com safe to connect a wallet?

This report does not record which wallet requests pgeebo02.wp-box.com 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 pgeebo02.wp-box.com?

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

Cloudflare Radar 1 / 4 Used in the analysis Source file SHA-256: 65d98d55dd886250f8740c9ca4695b2704ef68be3d3a0ccb5620446ae8d04ba3 SHA-256 of the prepared copy given to the model: 618e23cac8ee43a1bab4e10f271429f6779c536c7041461f9fde7be29defb473
SourceCloudflare Radar
Recorded
StateStored capture
HTTP status200
Final URLhttps://pgeebo02.wp-box.com/
Position1 / 4
Open capture Source Report Wayback Download
All capture links and hashes (4)

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 63 report ↗
IP Reputation Estonia109.94.209.151 abuse score 0/100 0 reports checked Nov 2, 2026
Registrar (base domain) PDR IN(IN)
Abuse contactabuse-contact@publicdomainregistry.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for wp-box.com →
Registration (base domain)wp-box.com · Created Nov 27, 2025 (340d) — Expires Nov 27, 2027
WHOIS statusclientTransferProhibited
HTTP Status200
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://pgeebo02.wp-box.com/
Favicon Hash
Observed page title
WordPress
Automated brand references
Wordpress
TLS Certificate
Issued by YE1 · stored validity ends in 76 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Estonia109.94.209.151
Network ASN
AS202376
AS name
ARVID-LOGICUM Arvid Logicum OU, EE
Organization
Arvid Logicum OU
Observed location
EstoniaTallinn, EE
Server header
nginx

Nameservers 2

  • ns1.ns-host.com
  • ns2.ns-host.com

Location describes the IP network.

TLS certificate

Issuer
YE1
Valid from
2026-10-20 13:46:19
Valid until
2027-01-18 13:46:18
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint187ae33d37f535ce6af4c404bcdbe7c1d912302e9c38c5a7bbe79bebdf9fe5b3
Certificate names · 1 SAN
  • *.wp-box.com

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

viewdns.info · 109.94.209.151rapiddns.io

Latest Classified Outcome 2026-11-02 11:53:26 UTC

The site was serving its pages at the latest check.

Technical details
Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-11-02 11:53:26 UTC
RDAP registration
Observed timeline last reachable: 2026-11-02 11:53:26 UTC last content: 2026-11-02 11:53:26 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Recorded subdomains1

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

  • www.pgeebo02.wp-box.comDomain record
Technologies · 1 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

13 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
CRDF
DNS8
ESET
VIPRE
G-Data
Lionic
Sophos
Fortinet
SOCRadar
Seclookup
BitDefender
alphaMountain.ai
Forcepoint ThreatSeeker

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of pgeebo02.wp-box.com · checked Nov 1, 2026

100
Good
Performance
FCP
0.79 s
First Contentful Paint
LCP
0.79 s
Largest Contentful Paint
CLS
0.028
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
1.12 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 200
Requested URL: http://pgeebo02.wp-box.com/
WordPress
Response
HTTP 200
HTML body
1.6 KB
Compressed
703 B
Links
0 internal · 0 external
Detected technologies
nginxwordpress
Selected response headers
Server: nginx
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 · 6
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=UTF-8
Date
Sun, 01 Nov 2026 22:13:14 GMT
Server
nginx
Transfer-Encoding
chunked

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

Archived
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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

Captured network requests

Network requests: 4 SHA-256 hashes: 4 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 22:15 UTC.

Open this scan on URLScan 01a1992a-63e1-737b-98a7-bf2333e35cc8 ↗

Stored observation history2

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

  1. Availability monitor · Recorded state

    live_content

    content_served

  2. Domain monitor · First collection record

    Reachable

All retained availability observations7

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_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 12:53:26.000000
    Evidence SHA-256
    5349527de953bc80eb284547c5f1965942a4ca4190d53217e36d657dfb1a7d8d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 12:53:26
    Evidence reason
    alive_content
  2. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 12:53:26.000000
    Evidence SHA-256
    5349527de953bc80eb284547c5f1965942a4ca4190d53217e36d657dfb1a7d8d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 12:53:26
    Evidence reason
    alive_content
  3. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 01:08:27.000000
    Evidence SHA-256
    d5e05e38f74d8edeae36955794e72cfa6e1200e7c44075ceee61d584dc14d471
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 01:08:27
    Evidence reason
    alive_content
  4. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 01:08:27.000000
    Evidence SHA-256
    d5e05e38f74d8edeae36955794e72cfa6e1200e7c44075ceee61d584dc14d471
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 01:08:27
    Evidence reason
    alive_content
  5. 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-11-01 23:20:11.055498
    Evidence SHA-256
    7c023747294077bd6e2ec2b080dc137e75a3ed6faf38dbdfcaa23e6958793fa3
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-01 23:20:11.055498
    Evidence reason
  6. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    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-11-01 23:12:26.000000
    Evidence SHA-256
    9f50d5318cf5e09d7962e237987e33f08cea7db24876470fddd896fc01c3c7e1
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-01 23:12:26
    Evidence reason
  7. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    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-11-01 23:12:26.000000
    Evidence SHA-256
    9f50d5318cf5e09d7962e237987e33f08cea7db24876470fddd896fc01c3c7e1
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-01 23:12:26
    Evidence reason

Threat Response Pipeline

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

Recorded events: 11. 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
    pgeebo02.wp-box.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · Cloudflare Radar: Malicious · Automated brand label: Wordpress · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 9 of 9
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 63
  • 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: 13/92
  • Cloudflare Radar: Malicious
    Cloudflare Radar classified this domain as Malware, Security threats
  • Automated brand label: Wordpress
    Collector label, not confirmed by a page check.
  • 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

4 entries
  1. Wayback Machine

    Page archived

    View source
  2. Added to PhishDestroy

    pgeebo02.wp-box.com

    View source
  3. URLScan

    Page captured

    View source
  4. VirusTotal

    13/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
All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Check for cloaking

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

pgeebo02.wp-box.com

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 13 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Malicious 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?

3 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.

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 pgeebo02.wp-box.com)
  • 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/pgeebo02.wp-box.com"
  title="PhishDestroy threat report for pgeebo02.wp-box.com"
  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>