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

norwaupdate2.wpenginepowered.com

In short

The captured page at norwaupdate2.wpenginepowered.com is a default WordPress blog post titled "Hello world!" under the site heading "anita ziyach Site" with the tagline "Your SUPER-powered WP Engine Site." The post is attributed to norwaupdate2 and dated November 26, 2023, with the stock WordPress welcome text inviting the user to edit or delete it. The footer credits the theme to StudioPress.

“anita ziyach Site – Your SUPER-powered WP Engine Site”

Review the evidence
Registrar
WP Engine
Resolved IP
United States141.193.213.11Cloudflare London, LLC · CDN
First observed
Nov 1, 2026
PhishDestroy assessment Critical
80/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 6/92
VirusTotal
6 / 92
engine detections ·
Page captures
6
open gallery
Nov 1, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded norwaupdate2.wpenginepowered.com on 2026-11-01. VirusTotal: 6/92 engines flag it. Risk: critical (80/100). Registrar: WP Engine. Status: Last known active. Hosting: Cloudflare London, LLC. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
6 / 92
Hosting
United States141.193.213.11Cloudflare London, LLC · CDN
Registrar
WP Engine
Page captures
6
Page captures Source results Registration record

PhishDestroy analysis, reviewed version

The captured page at norwaupdate2.wpenginepowered.com is a default WordPress blog post titled "Hello world!" under the site heading "anita ziyach Site" with the tagline "Your SUPER-powered WP Engine Site." The post is attributed to norwaupdate2 and dated November 26, 2023, with the stock WordPress welcome text inviting the user to edit or delete it. The footer credits the theme to StudioPress.

The stored VirusTotal domain result reports 6 detections out of 92 engines. VIPRE reported "phishing"; G-Data reported "phishing".

Source evidenceVirusTotal 6 / 92 8 sources

VirusTotal

6 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 15 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
53
Malicious
6
Suspicious
0
Undetected
33

Vendor labels

VIPRE
phishing
G-Data
phishing
Gridinsoft
phishing
ADMINUSLabs
malicious
BitDefender
phishing
alphaMountain.ai
phishing

Reputation score

0

Tags

  • dga

Categories

alphaMountain.ai
Phishing (alphaMountain.ai)

Registrar

MarkMonitor Inc.

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    A
    Value
    141.193.213.10
  • TTL, seconds
    300
    Type
    A
    Value
    141.193.213.11

DNS records observed

JARM fingerprint

27d40d40d00040d00042d43d00041df04c41293ba84f6efe3a613b22f983e6

Certificate

Subject alternative names
  • *.js.wpenginepowered.com
  • *.wpenginepowered.com
  • wpenginepowered.com
Issuer
Let's Encrypt / YE2
Serial
6178e0a2e313a4ff820c3c830387c973acb
SHA-256
3df3367eeb446833fac76d28c0f4e7e75774bf0009c4b14c6d0211fdd71d7a43
Subject
wpenginepowered.com
Valid until
Valid from

Registration record

Registrar
MarkMonitor Inc.
Registrar IANA ID
292
Registrar URL
http://www.markmonitor.com
Registered
Updated
Expires
Status
  • clientDeleteProhibited
  • clientTransferProhibited
  • clientUpdateProhibited
Nameservers
  • darwin.ns.cloudflare.com
  • lana.ns.cloudflare.com
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 53,
    "malicious": 6,
    "suspicious": 0,
    "undetected": 33
}
Vendor labels
{
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Gridinsoft": "phishing",
    "ADMINUSLabs": "malicious",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
Registrar
MarkMonitor Inc.
Created
2020-05-22T21:20:44Z
Expires
2028-05-22T21:20:44Z
Updated
2026-04-20T09:47:07Z
First seen
2023-11-28T12:54:32Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "141.193.213.10"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "141.193.213.11"
    }
]
Dns at
2026-10-25T11:00:46Z
Jarm
27d40d40d00040d00042d43d00041df04c41293ba84f6efe3a613b22f983e6
Certificate
{
    "san": [
        "*.js.wpenginepowered.com",
        "*.wpenginepowered.com",
        "wpenginepowered.com"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "6178e0a2e313a4ff820c3c830387c973acb",
    "sha256": "3df3367eeb446833fac76d28c0f4e7e75774bf0009c4b14c6d0211fdd71d7a43",
    "subject": "wpenginepowered.com",
    "valid_to": "2027-01-23T06:22:06Z",
    "valid_from": "2026-10-25T06:22:07Z"
}
Registration record
{
    "registrar": "MarkMonitor Inc.",
    "registrar_iana_id": "292",
    "registrar_url": "http://www.markmonitor.com",
    "created": "2020-05-22T21:20:44Z",
    "updated": "2026-04-20T09:47:07Z",
    "expires": "2028-05-22T00:00:00Z",
    "status": [
        "clientDeleteProhibited",
        "clientTransferProhibited",
        "clientUpdateProhibited"
    ],
    "nameservers": [
        "darwin.ns.cloudflare.com",
        "lana.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Separate source record · 6 malicious + 0 suspicious / 92 · 2026-10-25 10:21:34 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-25T10:21:34Z
fetched_at
2026-11-01T06:52:05Z
stats
{"timeout":0,"harmless":53,"malicious":6,"suspicious":0,"undetected":33}

OTX

no community references

Open report

Cloudflare Radar

provider verdict: clean

Open report
Cloudflare RadarOriginal source recordObserved: 12 fields

Observed: · Retrieved:

Report ID

4811d06c-5cc4-4fd2-a31a-920ed518e5a0

Final URL

https://norwaupdate2.wpenginepowered.com/

HTTP response

200

Navigation history

  • URL
    https://norwaupdate2.wpenginepowered.com/
    Status
    200

DOM structure hash

e3eaa52ad882ee9b9fd93152cfb644e559755bda244aa6e0a51064ec633b0eac

Document hash

3da3877bf013b7db76c02827fa4022fff1fb88bb6200db644a1ddf7d2fb9f0a8

Domain risk categories

  • Personal Blogs
  • Internet Communication

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    norwaupdate2.wpenginepowered.com
    Type
    A
    Value
    141.193.213.11
  • Name
    norwaupdate2.wpenginepowered.com
    Type
    A
    Value
    141.193.213.10

DNSSEC valid

No

IP address

127.0.1.8

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

Registration record

Registrar
MarkMonitor Inc.
Registered
Updated
Expires
Nameservers
  • darwin.ns.cloudflare.com
  • lana.ns.cloudflare.com
Original source fields · JSON
Uuid
4811d06c-5cc4-4fd2-a31a-920ed518e5a0
Final url
https://norwaupdate2.wpenginepowered.com/
Status
200
History
[
    {
        "url": "https://norwaupdate2.wpenginepowered.com/",
        "status": 200
    }
]
DOM structure hash
e3eaa52ad882ee9b9fd93152cfb644e559755bda244aa6e0a51064ec633b0eac
Document hash
3da3877bf013b7db76c02827fa4022fff1fb88bb6200db644a1ddf7d2fb9f0a8
Domain risks
[
    "Personal Blogs",
    "Internet Communication"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "norwaupdate2.wpenginepowered.com",
        "type": "A",
        "value": "141.193.213.11"
    },
    {
        "name": "norwaupdate2.wpenginepowered.com",
        "type": "A",
        "value": "141.193.213.10"
    }
]
Dnssec valid
false
Ip
127.0.1.8

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

Registration record
{
    "registrar": "MarkMonitor Inc.",
    "created": "2020-05-22T21:20:44Z",
    "updated": "2026-04-20T09:47:07Z",
    "expires": "2028-05-22T21:20:44Z",
    "nameservers": [
        "darwin.ns.cloudflare.com",
        "lana.ns.cloudflare.com"
    ]
}

Google Safe Browsing

No threat flag

Open report

URLScan

Page capture

SHA-256 459ab833c9e1dbc891620f3a06d3cf7cdd155106f83298ae5d4648f37ce03394

Open report
URLScanOriginal source recordObserved: 24 fields

Observed: · Retrieved:

Report ID

01a195d0-9d23-778e-bf03-e4d3e4f6db94

Final URL

https://norwaupdate2.wpenginepowered.com/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://norwaupdate2.wpenginepowered.com/
    From
    http://norwaupdate2.wpenginepowered.com/
    Status
    307

IP address

141.193.213.10

Contacted domains

  • secure.gravatar.com

Contacted IP addresses

  • 192.0.73.2
  • 141.193.213.10

Autonomous systems (ASN)

  • 2635
  • 209242

Server countries

  • US

Linked domains

  • www.studiopress.com

Document hash

459ab833c9e1dbc891620f3a06d3cf7cdd155106f83298ae5d4648f37ce03394

Script hashes

  • cb6f2d32c49d1c2b25e9ffc9aaafa3f83075346c01bcd4ae6eb187392a4292cf
  • 5274f11e6fb32ae0cf2dfb9f8043272865c397a7c4223b4cfa7d50ea52fbde89
  • ab326900e21f10d902070c93ca7824fb7f14e0901179b86631421e6bc4aaf257
  • fbf0d4e7883610c9e9e59e53b7a9573ab97cb12c9f6c3588ebc01a280823e3d9
  • 39967d241634394c8fe2b9602ccb73b3661e0ed422272d3fecc00a7e257e24a7
  • 063840b4b3f5869e0f0d078bab8bd29cfb3a59ee85e8e3edbbec35a8fe846fd3

JavaScript globals

  • jQuery
  • genesisBlocksShare
  • genesis_block_theme_js_vars
  • _wpemojiSettings
  • twemoji
  • wp

Cookies

  • cf_clearance

Browser storage keys

  • wpEmojiSettingsSupports

TLS session and certificate

Subject alternative names
  • *.js.wpenginepowered.com
  • *.wpenginepowered.com
  • wpenginepowered.com
Cipher
AES_128_GCM
Issuer
YE2
Subject
wpenginepowered.com
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

1069

Registered domain age, days

2326

Certificate age, days

7

Certificate validity, days

89

Page requests

16

Provider verdicts

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

HTTP headers

Server
cloudflare
Content-type
text/html; charset=UTF-8
X-powered-by
WP Engine
Original source fields · JSON
Uuid
01a195d0-9d23-778e-bf03-e4d3e4f6db94
Final url
https://norwaupdate2.wpenginepowered.com/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://norwaupdate2.wpenginepowered.com/",
        "from": "http://norwaupdate2.wpenginepowered.com/",
        "status": 307
    }
]
Ip
141.193.213.10
Contacted domains
[
    "secure.gravatar.com"
]
Contacted IP addresses
[
    "192.0.73.2",
    "141.193.213.10"
]
Asns
[
    "2635",
    "209242"
]
Countries
[
    "US"
]
Linked domains
[
    "www.studiopress.com"
]
Document hash
459ab833c9e1dbc891620f3a06d3cf7cdd155106f83298ae5d4648f37ce03394
Script hashes
[
    "cb6f2d32c49d1c2b25e9ffc9aaafa3f83075346c01bcd4ae6eb187392a4292cf",
    "5274f11e6fb32ae0cf2dfb9f8043272865c397a7c4223b4cfa7d50ea52fbde89",
    "ab326900e21f10d902070c93ca7824fb7f14e0901179b86631421e6bc4aaf257",
    "fbf0d4e7883610c9e9e59e53b7a9573ab97cb12c9f6c3588ebc01a280823e3d9",
    "39967d241634394c8fe2b9602ccb73b3661e0ed422272d3fecc00a7e257e24a7",
    "063840b4b3f5869e0f0d078bab8bd29cfb3a59ee85e8e3edbbec35a8fe846fd3"
]
Globals
[
    "jQuery",
    "genesisBlocksShare",
    "genesis_block_theme_js_vars",
    "_wpemojiSettings",
    "twemoji",
    "wp"
]
Cookies
[
    "cf_clearance"
]
Storage keys
[
    "wpEmojiSettingsSupports"
]
Tls
{
    "san": [
        "*.js.wpenginepowered.com",
        "*.wpenginepowered.com",
        "wpenginepowered.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE2",
    "subject": "wpenginepowered.com",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-23T06:22:06Z",
    "valid_from": "2026-10-25T06:22:07Z"
}
Domain age days
1069
Apex age days
2326
Tls age days
7
Tls valid days
89
Requests
16
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": -63,
        "malicious": false
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=UTF-8",
    "x-powered-by": "WP Engine"
}
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
01a13780-dfc3-7394-be73-333784c4aae2
score
null
malicious
null
result_at
null
enriched_at
2026-11-01T09:12:24Z
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":"2026-11-01 10:12:24"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

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

Open report

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

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

ai_title
norwaupdate2.wpenginepowered.com – Default WordPress Hello World Post
ai_description
PhishDestroy describes norwaupdate2.wpenginepowered.com as a captured WordPress site showing its default Hello world! post.
ai_summary
The captured page at norwaupdate2.wpenginepowered.com is a default WordPress blog post titled "Hello world!" under the site heading "anita ziyach Site" with the tagline "Your SUPER-powered WP Engine Site." The post is attributed to norwaupdate2 and dated November 26, 2023, with the stock WordPress welcome text inviting the user to edit or delete it. The footer credits the theme to StudioPress. The stored VirusTotal domain result reports 6 detections out of 92 engines. VIPRE reported "phishing"; G-Data reported "phishing".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-11-01 07:29:04
revision
585cc468ba4bfceb0faff08f807069a7579ea3e941dfd93c085f486821c9b6ab
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: 24 fields

Mail configuration

SPF lookups
0

CAA records

Domain
norwaupdate2.wpenginepowered.com

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Crawler rules

User agents
  • *
Present
Yes

Page title and metadata

Page title
anita ziyach Site – Your SUPER-powered WP Engine Site
Indexing directives
noindex, nofollow

Trackers

Requests
15
Observed services
  • Name
    Gravatar
    Company
    Automattic
    Country
    US
    Category
    Social Media
    Requests
    1

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
4
TLS
42
Waiting
583
Connection
19
Download
0
Response time, ms
648

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
  • 80
  • 443
  • 8080

Carbon estimate

Bytes
27943
CO₂, grams
0.001
Cleaner than, %
50

DNS servers

Nameservers
  • IP address
    172.64.33.151
    Host
    darwin.ns.cloudflare.com
  • IP address
    172.64.32.182
    Host
    lana.ns.cloudflare.com
DNS zone
wpenginepowered.com

Cookies

Cookies
  • Name
    cf_clearance
    Secure
    Yes
    HTTP-only
    Yes
    SameSite
    None

Location

IP address
141.193.213.11
ASN
209242
Organization
Cloudflare London, LLC
Country
US

TLS certificate

Issuer
Let's Encrypt / YE2
Subject
wpenginepowered.com

DNS records

A
  • 141.193.213.11
  • 141.193.213.10

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

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
141.193.213.10
IP version
4

Redirects

Redirect chain
  • https://norwaupdate2.wpenginepowered.com

Page links

External link addresses
  • https://www.studiopress.com/
External links
1
Internal links
4

HTTP headers

Response headers
Server
cloudflare
Content-type
text/html; charset=UTF-8
X-powered-by
WP Engine
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "norwaupdate2.wpenginepowered.com"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Crawler rules
{
    "agents": [
        "*"
    ],
    "present": true
}
Page title and metadata
{
    "title": "anita ziyach Site – Your SUPER-powered WP Engine Site",
    "robots": "noindex, nofollow"
}
Trackers
{
    "requests": 15,
    "trackers": [
        {
            "name": "Gravatar",
            "company": "Automattic",
            "country": "US",
            "category": "Social Media",
            "requests": 1
        }
    ]
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 4,
        "tls": 42,
        "wait": 583,
        "connect": 19,
        "download": 0
    },
    "response_ms": 648
}
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": [
        80,
        443,
        8080
    ]
}
Carbon
{
    "bytes": 27943,
    "co2_grams": 0.001,
    "cleaner_than": 50
}
Dns server
{
    "ns": [
        {
            "ip": "172.64.33.151",
            "host": "darwin.ns.cloudflare.com"
        },
        {
            "ip": "172.64.32.182",
            "host": "lana.ns.cloudflare.com"
        }
    ],
    "zone": "wpenginepowered.com"
}
Cookies
{
    "cookies": [
        {
            "name": "cf_clearance",
            "secure": true,
            "http_only": true,
            "same_site": "None"
        }
    ]
}
Location
{
    "ip": "141.193.213.11",
    "asn": "209242",
    "org": "Cloudflare London, LLC",
    "country": "US"
}
Ssl
{
    "issuer": "Let's Encrypt / YE2",
    "subject": "wpenginepowered.com"
}
DNS records
{
    "A": [
        "141.193.213.11",
        "141.193.213.10"
    ]
}
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
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "141.193.213.10",
    "family": 4
}
Redirects
{
    "chain": [
        "https://norwaupdate2.wpenginepowered.com"
    ]
}
Page links
{
    "external": [
        "https://www.studiopress.com/"
    ],
    "external_count": 1,
    "internal_count": 4
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html; charset=UTF-8",
        "x-powered-by": "WP Engine"
    }
}

Questions about norwaupdate2.wpenginepowered.com

Is norwaupdate2.wpenginepowered.com legit?

PhishDestroy rates norwaupdate2.wpenginepowered.com as critical risk (80/100) from the recorded evidence; it was first recorded on 2026-11-01. VirusTotal: 6/92 engines flag it. Treat the site as unsafe.

Is norwaupdate2.wpenginepowered.com safe to connect a wallet?

This report does not record which wallet requests norwaupdate2.wpenginepowered.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 norwaupdate2.wpenginepowered.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 · 6 captures

Cloudflare Radar 1 / 6 Used in the analysis Source file SHA-256: 455282d85447a4dd3690396b79ad827aa47802b57ac6b6faaa4f8b5612baf608 SHA-256 of the prepared copy given to the model: d158480de8c6df6d70ae2d1ee82bee96b880880dbaf5204439ceba52de6ea8a1
SourceCloudflare Radar
Recorded
StateStored capture
HTTP status200
Final URLhttps://norwaupdate2.wpenginepowered.com/
Position1 / 6
Open capture Source Report Wayback Download
All capture links and hashes (6)

Domain details

Domain
IP Context United States141.193.213.11 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider WP Engine
Abuse contactabuse@wpengine.com
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://norwaupdate2.wpenginepowered.com/
Favicon Hash
Observed page title
anita ziyach Site – Your SUPER-powered WP Engine Site
Automated brand references
Wordpress
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 82 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
United States141.193.213.11
Network ASN
AS209242
AS name
CLOUDFLARESPECTRUM Cloudflare London, LLC, US
Organization
Cloudflare London, LLC
Observed location
United StatesAustin, US
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-10-25 06:22:07
Valid until
2027-01-23 06:22:06
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint3df3367eeb446833fac76d28c0f4e7e75774bf0009c4b14c6d0211fdd71d7a43
Certificate names · 3 SANs
  • *.js.wpenginepowered.com
  • *.wpenginepowered.com
  • wpenginepowered.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 · 141.193.213.11rapiddns.io

Latest Classified Outcome 2026-11-02 00:07:17 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 00:07:17 UTC
RDAP registration
Observed timeline last reachable: 2026-11-02 00:07:17 UTC last content: 2026-11-02 00:07:17 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.
Technologies · 9 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

6 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 6 detections
ADMINUSLabs
alphaMountain.ai
BitDefender
G-Data
Gridinsoft
VIPRE
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of norwaupdate2.wpenginepowered.com · checked Nov 1, 2026

100
Good
Performance
FCP
1.09 s
First Contentful Paint
LCP
1.09 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
1.6 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://norwaupdate2.wpenginepowered.com/
anita ziyach Site – Your SUPER-powered WP Engine Site
Response
HTTP 200
HTML body
27.3 KB
Compressed
7.4 KB
Links
5 internal · 1 external
Detected technologies
jquerywordpresscloudflare
Selected response headers
Content-Type: text/html; charset=UTF-8
Server: cloudflare
X-Powered-By: WP Engine
Cache-Control: max-age=600, must-revalidate
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Favicon fingerprint: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
Saved response-header values · 16
alt-svc
h3=":443"; ma=86400
Cache-Control
max-age=600, must-revalidate
cf-cache-status
DYNAMIC
CF-RAY
a538ca82ea27a4f9-GRU
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=UTF-8
Date
Sun, 01 Nov 2026 06:20:00 GMT
Link
; rel="https://api.w.org/"
Server
cloudflare
Transfer-Encoding
chunked
Vary
Accept-Encoding
X-Cache
HIT: 1
X-Cache-Group
normal
X-Cacheable
SHORT
X-Powered-By
WP Engine

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: 16 SHA-256 hashes: 15 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 06:36 UTC.

Open this scan on URLScan 01a195d0-9d23-778e-bf03-e4d3e4f6db94 ↗

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. Availability monitor · Recorded state

    live_content

    content_served

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 01:07:17.000000
    Evidence SHA-256
    65b70e83743d3454743f84b0ebf31d0f197c8e8e4f0a60756fa94b1cd35249c8
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 01:07:17
    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 01:07:17.000000
    Evidence SHA-256
    65b70e83743d3454743f84b0ebf31d0f197c8e8e4f0a60756fa94b1cd35249c8
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 01:07:17
    Evidence reason
    alive_content
  3. 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
  4. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    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-01 13:10:34.000000
    Evidence SHA-256
    fb37644ca48d5dbf14e2294f0a4dcdc4d1be2d228ee6c18673ab9b6b285406ef
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 13:10:34
    Evidence reason
    alive_content
  5. 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-01 13:10:34.000000
    Evidence SHA-256
    fb37644ca48d5dbf14e2294f0a4dcdc4d1be2d228ee6c18673ab9b6b285406ef
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 13:10:34
    Evidence reason
    alive_content
  6. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 07:36:00.000000
    Evidence SHA-256
    6d0137d637078e8551a9615db9238f7ee0d06735119ffa92eb423b3e4bb0ba86
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 07:36:00
    Evidence reason
  7. http_observationunknown
    Observation source
    http_observation
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 07:36:00.000000
    Evidence SHA-256
    6d0137d637078e8551a9615db9238f7ee0d06735119ffa92eb423b3e4bb0ba86
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 07:36:00
    Evidence reason

Threat Response Pipeline

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

Recorded events: 8. 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
    norwaupdate2.wpenginepowered.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · Cloudflare Radar Report · VirusTotal · Automated brand label: Wordpress · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 6 of 6
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • 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.
  • VirusTotal
    Detections recorded on VirusTotal: 6/92
  • 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

3 entries
  1. URLScan

    Page captured

    View source
  2. Added to PhishDestroy

    norwaupdate2.wpenginepowered.com

    View source
  3. VirusTotal

    6/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.

norwaupdate2.wpenginepowered.com

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 6 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Open report 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 norwaupdate2.wpenginepowered.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/norwaupdate2.wpenginepowered.com"
  title="PhishDestroy threat report for norwaupdate2.wpenginepowered.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>