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

hellpdesk.net

In short

hellpdesk.net is a Phishingtest impersonation page detected by PhishDestroy on 2026-10-26.

“Microsoft SSO Sign In”

Review the evidence
Registrar
GoDaddy
Resolved IP
103.214.5.132
Registered
Oct 13, 2016
PhishDestroy assessment Critical
100/100
Evidence score
Availability Server error The latest stored response was inconclusive Observed HTTP probe
Risk signals
VirusTotal detections: 5/92 Spamhaus DBL: phishing domain Stored blocklist matches: 1 Automated brand label: Phishingtest Scam type: Impersonation
VirusTotal
5 / 92
engine detections ·
OTX
32
community references
Cloudflare Radar
clean
source verdict
Page captures
10
open gallery
Domain age
3665 days
Reports sent
1
view timeline
OTX: 32 refs Oct 26, 2026 1 Report Sent CDN
X Telegram API

Analysis

Domain summary

hellpdesk.net is a Phishingtest impersonation page detected by PhishDestroy on 2026-10-26. Risk: critical (100/100). Registrar: GoDaddy. Status: Server error. Hosting: HOSTSLIM OU. PhishDestroy sent 1 abuse report. VirusTotal: 5/92 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.

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

PhishDestroy threat report

Overview

The captured screenshot dated 2026-10-26 shows a plain server error page headed Not Found with the line The requested URL was not found on this server, while collected page metadata recorded the title Microsoft SSO Sign In. PhishDestroy listed the domain after VirusTotal flagged it and it was first seen on 2026-10-26.

How the scam works

The recorded sign-in title points to a page built to imitate a Microsoft single sign-on prompt, so a visitor would be invited to type a username, password or second factor into attacker-controlled fields. Anyone who submitted credentials could hand over access to their genuine account, which is the standard credential harvesting risk in this category.

Evidence

The screenshot itself shows only an error message with no form fields visible on 2026-10-26. urlscan.io returned a malicious overall verdict with a score of 100 and a phishing category on 2026-10-26, while its ML engine scored -68. VirusTotal reported 5 detections from 92 engines with each flagging vendor labelling it phishing, and OpenPhish plus PhishDestroy's internal lists carried it on 2026-10-26. Google Safe Browsing was not flagged and 12 DNS resolvers reported no blocking on 2026-10-26.

Infrastructure

The domain was registered on 2016-10-13 through GoDaddy.com, LLC, with DNS delegated to nameservers tied to a landing-page routing service. Hosting was recorded on a HostSlim network address in the Netherlands, with CloudFront appearing in the response headers on 2026-10-26. A Let's Encrypt certificate issued to the domain was valid from 2026-09-28 to 2026-12-27.

What to do

If you submitted credentials, change your password on the genuine Microsoft service, enable two-factor authentication, and review recent sign-in activity for unexpected access. Treat any link or message directing you to hellpdesk.net as malicious and do not enter information there. Security teams should block hellpdesk.net in proxies, DNS filters and email gateways, and correlate sightings against the recorded certificate and DNS delegation.

Useful links

urlscan.io scan and screenshotCloudflare Radar reportURLQuery reportStored capture screenshotCloudflare Radar screenshot (2026-10-26T17:09:02Z)URLScan screenshot (2026-08-04T05:21:10Z)URLScan capture reportURLScan screenshot (2026-10-21T22:06:10Z)URLScan capture reportURLScan screenshot (2026-10-22T05:28:11Z)URLScan capture reportURLScan screenshot (2026-10-26T13:00:51Z)URLScan capture reportURLScan screenshot (2026-10-26T16:18:42Z)URLScan capture reportURLScan screenshot (2026-10-26T17:36:01Z)URLScan capture reportVirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review
Source evidenceVirusTotal 5 / 92 · OTX 32 references 9 sources

VirusTotal

5 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 12 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
54
Malicious
5
Suspicious
0
Undetected
33

Vendor labels

SOCRadar
phishing
LevelBlue
phishing
Gridinsoft
phishing
alphaMountain.ai
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Popularity ranks

Alexa
319973
Statvoo
319973
Cisco Umbrella
946552
Cloudflare Radar
1000000

Created

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    A
    Value
    103.214.5.132
  • TTL, seconds
    3600
    Type
    NS
    Value
    ns2.landingpagerouter.com
  • TTL, seconds
    3600
    Type
    NS
    Value
    ns1.landingpagerouter.com
  • TTL, seconds
    3600
    Type
    SOA
    Responsible mailbox
    certificates.usecure.io
    Value
    ns1.landingpagerouter.com
  • TTL, seconds
    60
    Type
    TXT
    Value
    v=spf1 a mx include:spf.mail.user-training.com ~all

DNS records observed

JARM fingerprint

29d29d00000000000042d42d000000dd5c266caaa8baaf93008418f7774284

Certificate

Subject alternative names
  • hellpdesk.net
Issuer
Let's Encrypt / YR2
Serial
5d83e9ea90364caea5c5b581a713c5b4ccd
SHA-256
24c3a54f6606544d8bdf9d460a802d73a15e5c6194a6674344722e1e27ecbf80
Subject
hellpdesk.net
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": 54,
    "malicious": 5,
    "suspicious": 0,
    "undetected": 33
}
Vendor labels
{
    "SOCRadar": "phishing",
    "LevelBlue": "phishing",
    "Gridinsoft": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Popularity
{
    "Alexa": 319973,
    "Statvoo": 319973,
    "Cisco Umbrella": 946552,
    "Cloudflare Radar": 1000000
}
Created
2016-10-13T00:00:00Z
Updated
2026-02-22T00:00:00Z
First seen
2023-10-12T16:45:07Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "103.214.5.132"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns2.landingpagerouter.com"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns1.landingpagerouter.com"
    },
    {
        "ttl": 3600,
        "type": "SOA",
        "rname": "certificates.usecure.io",
        "value": "ns1.landingpagerouter.com"
    },
    {
        "ttl": 60,
        "type": "TXT",
        "value": "v=spf1 a mx include:spf.mail.user-training.com ~all"
    }
]
Dns at
2026-10-26T14:04:34Z
Jarm
29d29d00000000000042d42d000000dd5c266caaa8baaf93008418f7774284
Certificate
{
    "san": [
        "hellpdesk.net"
    ],
    "issuer": "Let's Encrypt / YR2",
    "serial": "5d83e9ea90364caea5c5b581a713c5b4ccd",
    "sha256": "24c3a54f6606544d8bdf9d460a802d73a15e5c6194a6674344722e1e27ecbf80",
    "subject": "hellpdesk.net",
    "valid_to": "2026-12-27T13:34:52Z",
    "valid_from": "2026-09-28T13:34:53Z"
}
Registry data
{
    "status": [
        "client delete prohibited",
        "client renew prohibited",
        "client transfer prohibited",
        "client update prohibited"
    ],
    "events": {
        "expiration": "2027-10-13T16:03:45Z",
        "last changed": "2026-10-14T21:10:43Z",
        "registration": "2016-10-13T16:03:45Z",
        "last update of RDAP database": "2026-10-21T15:08:50Z"
    },
    "registrar": "GoDaddy.com, LLC",
    "registrar_iana_id": "146"
}
Separate source record · 5 malicious + 0 suspicious / 92 · 2026-10-26 13:59:09 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-26T13:59:09Z
fetched_at
2026-10-26T17:39:22Z
stats
{"timeout":0,"harmless":54,"malicious":5,"suspicious":0,"undetected":33}

Spamhaus DBL

phishing domain

URLScan

Malicious

SHA-256 c7627e83a793f4f5c4953d5074b7dca93a42c31cdf9697c250a8f3f5ddf7e49e

Open report
URLScanOriginal source recordObserved: 23 fields

Observed: · Retrieved:

Report ID

01a1790b-5659-734f-8eec-4ad59acc1313

Final URL

https://hellpdesk.net/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://hellpdesk.net/
    From
    http://hellpdesk.net/
    Status
    307

IP address

103.214.5.132

Contacted domains

  • usecure.s3.eu-west-1.amazonaws.com
  • fonts.googleapis.com
  • fonts.gstatic.com

Contacted IP addresses

  • 142.251.14.94
  • 3.5.72.95
  • 2a00:1450:4001:c15::5f
  • 103.214.5.132

Autonomous systems (ASN)

  • 15169
  • 16509
  • 207083

Server countries

  • US
  • IE
  • DE
  • NL

Document hash

07a6e92d6b57607aed8409b29baf0f759ac0a252fc3973982dbeb33d34972096

Script hashes

  • 6bbbd733c0417ff85ee13757607a771cc0f04256d3ed8f8c96723a7fa451ddbc

JavaScript globals

  • clearImmediate
  • setImmediate
  • usecure

Cookies

  • AWSALB
  • AWSALBCORS

TLS session and certificate

Subject alternative names
  • hellpdesk.net
Cipher
AES_256_GCM
Issuer
YR2
Subject
hellpdesk.net
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

3663

Registered domain age, days

3663

Certificate age, days

28

Certificate validity, days

89

Cisco Umbrella rank

946552

Page requests

18

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
-68
Malicious
No
Overall verdict
Tags
  • phishing
Score
100
Brands
  • phishingtest
Malicious
Yes
Categories
  • phishing
URLScan verdict
Tags
  • phishing
Score
100
Brands
  • Phishing Simulation
Malicious
Yes
Categories
  • phishing

HTTP headers

Server
CloudFront
Content-type
text/html; charset=utf-8
Strict-transport-security
max-age=31536000; includeSubDomains; preload
Content-security-policy
default-src 'self';base-uri 'self';font-src 'self' data: https:;form-action 'self';frame-ancestors 'self' https://*.usecure.io https://*.user-training.com;img-src 'self' data: https://*.amazonaws.com
X-frame-options
SAMEORIGIN
X-content-type-options
nosniff
Referrer-policy
no-referrer
Cross-origin-opener-policy
same-origin
Cross-origin-resource-policy
same-origin
Original source fields · JSON
Uuid
01a1790b-5659-734f-8eec-4ad59acc1313
Final url
https://hellpdesk.net/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://hellpdesk.net/",
        "from": "http://hellpdesk.net/",
        "status": 307
    }
]
Ip
103.214.5.132
Contacted domains
[
    "usecure.s3.eu-west-1.amazonaws.com",
    "fonts.googleapis.com",
    "fonts.gstatic.com"
]
Contacted IP addresses
[
    "142.251.14.94",
    "3.5.72.95",
    "2a00:1450:4001:c15::5f",
    "103.214.5.132"
]
Asns
[
    "15169",
    "16509",
    "207083"
]
Countries
[
    "US",
    "IE",
    "DE",
    "NL"
]
Document hash
07a6e92d6b57607aed8409b29baf0f759ac0a252fc3973982dbeb33d34972096
Script hashes
[
    "6bbbd733c0417ff85ee13757607a771cc0f04256d3ed8f8c96723a7fa451ddbc"
]
Globals
[
    "clearImmediate",
    "setImmediate",
    "usecure"
]
Cookies
[
    "AWSALB",
    "AWSALBCORS"
]
Tls
{
    "san": [
        "hellpdesk.net"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "YR2",
    "subject": "hellpdesk.net",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-27T13:34:52Z",
    "valid_from": "2026-09-28T13:34:53Z"
}
Domain age days
3663
Apex age days
3663
Tls age days
28
Tls valid days
89
Umbrella rank
946552
Requests
18
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": -68,
        "malicious": false
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "phishingtest"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "Phishing Simulation"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "CloudFront",
    "content-type": "text/html; charset=utf-8",
    "strict-transport-security": "max-age=31536000; includeSubDomains; preload",
    "content-security-policy": "default-src 'self';base-uri 'self';font-src 'self' data: https:;form-action 'self';frame-ancestors 'self' https://*.usecure.io https://*.user-training.com;img-src 'self' data: https://*.amazonaws.com",
    "x-frame-options": "SAMEORIGIN",
    "x-content-type-options": "nosniff",
    "referrer-policy": "no-referrer",
    "cross-origin-opener-policy": "same-origin",
    "cross-origin-resource-policy": "same-origin"
}
Separate monitor record · 2026-10-26 17:41 UTC

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

record_source
domain_monitor.urlscan
uuid
01a1790b-5659-734f-8eec-4ad59acc1313
score
100
malicious
true
result_at
2026-10-26T17:41:11Z
enriched_at
null
source_timestamps
{"urlscan_result_at":"2026-10-26 18:41:11","urlscan_enriched_at":null}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

32 community references

Open report

Cloudflare Radar

provider verdict: clean

Open report
Cloudflare RadarOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Report ID

fe286905-3227-4070-8a9f-2d8c4700a0b7

Final URL

https://hellpdesk.net/

HTTP response

404

Navigation history

  • URL
    https://hellpdesk.net/
    Status
    404

DOM structure hash

42065dba3b8a7b2130dd66fe299c26c1aa681d7c7f2893f8410bbcd2d2e1770d

Document hash

9dcc361cf979ea9471e1076ab30724c665229614d2d7432dfe9127c8b6d3a443

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    hellpdesk.net
    Type
    A
    Value
    103.214.5.132

DNSSEC valid

No

IP address

103.214.5.132

Registration record

Registrar
GoDaddy.com, LLC
Registered
Updated
Expires
Nameservers
  • ns1.landingpagerouter.com
  • ns2.landingpagerouter.com
Original source fields · JSON
Uuid
fe286905-3227-4070-8a9f-2d8c4700a0b7
Final url
https://hellpdesk.net/
Status
404
History
[
    {
        "url": "https://hellpdesk.net/",
        "status": 404
    }
]
DOM structure hash
42065dba3b8a7b2130dd66fe299c26c1aa681d7c7f2893f8410bbcd2d2e1770d
Document hash
9dcc361cf979ea9471e1076ab30724c665229614d2d7432dfe9127c8b6d3a443
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "hellpdesk.net",
        "type": "A",
        "value": "103.214.5.132"
    }
]
Dnssec valid
false
Ip
103.214.5.132
Registration record
{
    "registrar": "GoDaddy.com, LLC",
    "created": "2016-10-13T16:03:45Z",
    "updated": "2026-10-14T21:10:43Z",
    "expires": "2027-10-13T16:03:45Z",
    "nameservers": [
        "ns1.landingpagerouter.com",
        "ns2.landingpagerouter.com"
    ]
}

Google Safe Browsing

No threat flag

Open report

PhishDestroy DOM

10 / 100 · heuristic score · 2 brand references · 1 classification

Open report
Separate monitor score · 10 / 100 · 2026-10-26T17:42:02Z

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-10-26T17:42:02Z
source_timestamp
2026-10-26 18:42:02
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
hellpdesk.net — Microsoft SSO credential phishing
ai_description
PhishDestroy assesses hellpdesk.net as a credential phishing domain presenting a Microsoft SSO sign-in page to harvest account passwords.
ai_generated_at
2026-10-26T17:42:18Z
ai_generated_by
mimo-flash
interpretation
Narrative generation metadata, separate from provider 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: 17 fields

Mail configuration

SPF record
v=spf1 a mx include:spf.mail.user-training.com ~all
SPF lookups
3

CAA records

Domain
hellpdesk.net

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
2
Archived days
9
Snapshots per day
0.01
Average page size, bytes
652

Crawler rules

Present
Yes

TLS connection

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

Ports

Open ports
  • 22
  • 53
  • 80
  • 443

DNS servers

Nameservers
  • IP address
    103.214.5.132
    Host
    ns2.landingpagerouter.com
  • IP address
    103.214.5.132
    Host
    ns1.landingpagerouter.com
DNS zone
hellpdesk.net

Location

IP address
103.214.5.132
ASN
207083
Organization
HOSTSLIM OU
City
Lelystad
Country
NL

TLS certificate

Issuer
Let's Encrypt / YR2
Subject
hellpdesk.net

DNS records

A
  • 103.214.5.132
NS
  • ns2.landingpagerouter.com
  • ns1.landingpagerouter.com
SOA
Primary nameserver
ns1.landingpagerouter.com
Hostmaster
certificates.usecure.io
Serial
1793033507
Refresh, seconds
3600
Retry, seconds
900
Expiry, seconds
1209600
Minimum TTL, seconds
60
TXT
  • v=spf1 a mx include:spf.mail.user-training.com ~all

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Header value
max-age=31536000; includeSubDomains; preload
Observation
Site is compatible with the HSTS preload list!
Preload compatible
Yes

HTTP security policies

X-Frame-Options
SAMEORIGIN
Referrer-Policy
no-referrer
X-XSS-Protection
0
Permissions-Policy
No
X-Content-Type-Options
nosniff
Content-Security-Policy
default-src 'self';base-uri 'self';font-src 'self' data: https:;form-action 'self';frame-ancestors 'self' https://*.usec
Strict-Transport-Security
max-age=31536000; includeSubDomains; preload
Cross-Origin-Opener-Policy
same-origin
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
same-origin

IP lookup

IP address
103.214.5.132
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.landingpagerouter.com
  • ns2.landingpagerouter.com

HTTP headers

Response headers
Content-type
text/html; charset=utf-8
Strict-transport-security
max-age=31536000; includeSubDomains; preload
Content-security-policy
default-src 'self';base-uri 'self';font-src 'self' data: https:;form-action 'self';frame-ancestors 'self' https://*.usecure.io https://*.user-training.com;img-src 'self' data: https://*.amazonaws.com https://*.usecure.io https://*.user-training.com;object-src 'none';script-src 'self' 'unsafe-inline'
X-frame-options
SAMEORIGIN
X-content-type-options
nosniff
Referrer-policy
no-referrer
Cross-origin-opener-policy
same-origin
Cross-origin-resource-policy
same-origin
Original source fields · JSON
Mail configuration
{
    "spf": "v=spf1 a mx include:spf.mail.user-training.com ~all",
    "spf_lookups": 3
}
Caa records
{
    "domain": "hellpdesk.net"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2025-07-16T15:05:23Z",
    "first": "2021-12-07T07:00:02Z",
    "changes": 2,
    "days_archived": 9,
    "scans_per_day": 0.01,
    "avg_page_bytes": 652
}
Crawler rules
{
    "present": true
}
TLS connection
{
    "alpn": "http/1.1",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        22,
        53,
        80,
        443
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "103.214.5.132",
            "host": "ns2.landingpagerouter.com"
        },
        {
            "ip": "103.214.5.132",
            "host": "ns1.landingpagerouter.com"
        }
    ],
    "zone": "hellpdesk.net"
}
Location
{
    "ip": "103.214.5.132",
    "asn": "207083",
    "org": "HOSTSLIM OU",
    "city": "Lelystad",
    "country": "NL"
}
Ssl
{
    "issuer": "Let's Encrypt / YR2",
    "subject": "hellpdesk.net"
}
DNS records
{
    "A": [
        "103.214.5.132"
    ],
    "NS": [
        "ns2.landingpagerouter.com",
        "ns1.landingpagerouter.com"
    ],
    "SOA": "{\"nsname\": \"ns1.landingpagerouter.com\", \"hostmaster\": \"certificates.usecure.io\", \"serial\": 1793033507, \"refresh\": 3600, \"retry\": 900, \"expire\": 1209600, \"minttl\": 60}",
    "TXT": [
        "v=spf1 a mx include:spf.mail.user-training.com ~all"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=31536000; includeSubDomains; preload",
    "message": "Site is compatible with the HSTS preload list!",
    "compatible": true
}
HTTP security policies
{
    "xFrameOptions": "SAMEORIGIN",
    "referrerPolicy": "no-referrer",
    "xXSSProtection": "0",
    "permissionsPolicy": false,
    "xContentTypeOptions": "nosniff",
    "contentSecurityPolicy": "default-src 'self';base-uri 'self';font-src 'self' data: https:;form-action 'self';frame-ancestors 'self' https://*.usec",
    "strictTransportPolicy": "max-age=31536000; includeSubDomains; preload",
    "crossOriginOpenerPolicy": "same-origin",
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": "same-origin"
}
Get ip
{
    "ip": "103.214.5.132",
    "family": 4
}
Registration record
{
    "registrar": "GoDaddy.com, LLC",
    "created": "2016-10-13T16:03:45Z",
    "updated": "2026-10-14T21:10:43Z",
    "expires": "2027-10-13T16:03:45Z",
    "status": [
        "clientDeleteProhibited https://icann.org/epp",
        "clientRenewProhibited https://icann.org/epp",
        "clientTransferProhibited https://icann.org/epp",
        "clientUpdateProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "ns1.landingpagerouter.com",
        "ns2.landingpagerouter.com"
    ]
}
HTTP headers
{
    "headers": {
        "content-type": "text/html; charset=utf-8",
        "strict-transport-security": "max-age=31536000; includeSubDomains; preload",
        "content-security-policy": "default-src 'self';base-uri 'self';font-src 'self' data: https:;form-action 'self';frame-ancestors 'self' https://*.usecure.io https://*.user-training.com;img-src 'self' data: https://*.amazonaws.com https://*.usecure.io https://*.user-training.com;object-src 'none';script-src 'self' 'unsafe-inline'",
        "x-frame-options": "SAMEORIGIN",
        "x-content-type-options": "nosniff",
        "referrer-policy": "no-referrer",
        "cross-origin-opener-policy": "same-origin",
        "cross-origin-resource-policy": "same-origin"
    }
}

Questions about hellpdesk.net

Is hellpdesk.net legit?

No. PhishDestroy classifies hellpdesk.net as a Phishingtest impersonation page (risk: critical, 100/100); it was first detected on 2026-10-26. VirusTotal: 5/92 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.

Is hellpdesk.net safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on hellpdesk.net. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used hellpdesk.net?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Blocklist matchesOpenPhish · PhishDestroy · no match in the other 10 2
OpenPhish Listed View source
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 10 captures

Primary capture 1 / 10
SourcePrimary capture
Recorded
StateStored capture
Position1 / 10
Open capture Wayback Download
All capture links and hashes (10)

What the capture shows

Automated image analysismimo-v2.6-flash

70%Confidence
Impersonated brand
Microsoft
Scam type
Credential phishing
Page type
Error page
Page language
English
  • No wallet request
  • Asks for logins or passwords

The screenshot shows a white page with a bold Not Found heading and the sentence The requested URL was not found on this server. No logo, form field, button or offer is visible in this capture, while the recorded page title for the domain was Microsoft SSO Sign In.

Look of the page plain white server error page

Analysed capture
hellpdesk.net: Phishing site — Flagged by OpenPhish, Spamhaus DBL, 5/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical).
Social preview card hellpdesk.net: Phishing site — Flagged by OpenPhish, Spamhaus DBL, 5/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical). v 2f26eb4790f2

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Phishingtest report ↗
IP Context Amazon CloudFront shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingphishing-database+2 more
Registrar GoDaddy US(US)
Abuse contactabuse@godaddy.com, abuse@rakar.nl
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for hellpdesk.net →
RegistrationCreated Oct 13, 2016 — Expires Oct 13, 2027
Registrant countryUnited States VirusTotal WHOIS
Registrant80315b2e6ac1a801 VirusTotal WHOIS
WHOIS statusclientDeleteProhibitedclientRenewProhibitedclientTransferProhibitedclientUpdateProhibited
Technical detailsProvenance & timestamps
First DetectedOct 26, 2026
DOM Analysisanalyzed Oct 26, 2026score 10/1002 brand signals
Submitted URLhttp://hellpdesk.net/?… query redacted
Favicon Hash
Case ID
Observed page title
404 Not Found
Automated brand references
Google Microsoft
TLS Certificate
Issued by Let's Encrypt / YR2 · stored validity ends in 61 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
103.214.5.132
Network ASN
AS207083
Organization
HOSTSLIM OU
Observed location
Lelystad, NL
Server header
CloudFront

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • ns1.landingpagerouter.com
  • ns2.landingpagerouter.com

SOA

  • nsname: ns1.landingpagerouter.com
  • hostmaster: certificates.usecure.io
  • serial: 1793033507
  • refresh: 3600
  • retry: 900
  • expire: 1209600
  • minttl: 60

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR2
Valid from
2026-09-28 13:34:53
Valid until
2026-12-27 13:34:52
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint24c3a54f6606544d8bdf9d460a802d73a15e5c6194a6674344722e1e27ecbf80
Certificate names · 1 SAN
  • hellpdesk.net

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

viewdns.info · 103.214.5.132rapiddns.io
Recorded subdomains4

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

  • citrix.hellpdesk.netDomain record
  • staging.hellpdesk.netDomain record
  • testing.hellpdesk.netDomain record
  • www.hellpdesk.netDomain record
Technologies · 4 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

5 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 4 detections
alphaMountain.ai
Forcepoint ThreatSeeker
Gridinsoft
LevelBlue
SOCRadar
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of hellpdesk.net · checked Oct 26, 2026

100
Good
Performance
FCP
0.79 s
First Contentful Paint
LCP
0.79 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
1.39 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://hellpdesk.net/
Final URL: https://hellpdesk.net/
Microsoft SSO Sign In
Response
HTTP 200
HTML body
18.0 KB
Compressed
2.7 KB
Links
13 internal · 0 external
Selected response headers
Server: CloudFront
Content-Type: text/html; charset=utf-8
Content-Encoding: gzip
Security headers present
Strict-Transport-SecurityContent-Security-PolicyX-Frame-OptionsX-Content-Type-OptionsX-XSS-ProtectionReferrer-PolicyCross-Origin-Opener-PolicyCross-Origin-Resource-Policy
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 27
Access-Control-Allow-Origin
*
alt-svc
h3=":443"; ma=86400
Connection
keep-alive
Content-Encoding
gzip
Content-Security-Policy
default-src 'self';base-uri 'self';font-src 'self' data: https:;form-action 'self';frame-ancestors 'self' https://*.usecure.io https://*.user-training.com;img-src 'self' data: https://*.amazonaws.com https://*.usecure.io https://*.user-training.com;object-src 'none';script-src 'self' 'unsafe-inline' 'unsafe-eval';scrip
Content-Type
text/html; charset=utf-8
Cross-Origin-Opener-Policy
same-origin
Cross-Origin-Resource-Policy
same-origin
Date
Mon, 26 Oct 2026 16:15:16 GMT
Etag
W/"482c-qdDsDhsgqsWZ/W8VAFgvuguLRPQ"
origin-agent-cluster
?1
ratelimit-limit
60
ratelimit-policy
60;w=60
ratelimit-remaining
59
ratelimit-reset
60
Referrer-Policy
no-referrer
Server
CloudFront
Strict-Transport-Security
max-age=31536000; includeSubDomains; preload
Transfer-Encoding
chunked
Vary
Accept-Encoding
Via
1.1 2ef9ad1c8e8d306617a72c1e978a7716.cloudfront.net (CloudFront)
X-Content-Type-Options
nosniff
x-dns-prefetch-control
off
x-download-options
noopen
X-Frame-Options
SAMEORIGIN
x-permitted-cross-domain-policies
none
X-XSS-Protection
0

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

Archived
Registration & observation details1

Availability observations

Last reachable observation

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

Stored observation history4

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

  1. VirusTotal · Detection count

    4→5

    Engines added
    SOCRadar
    Engines removed
    None recorded
    Recorded vendor total
    5
  2. Domain monitor · First collection record

    Reachable

  3. Domain monitor · Recorded state

    Unavailable→Reachable

  4. Domain monitor · Recorded state

    Reachable→Unavailable

All retained availability observations3

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
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    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-10-26 17:31:01.000000
    Evidence SHA-256
    22a0dcfa0aaa7a2a1bb4d9769d163522ad2c9990ade9128e251daa404bfdbc3a
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-26 17:31:01
    Evidence reason
  2. 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-10-26 17:31:01.000000
    Evidence SHA-256
    22a0dcfa0aaa7a2a1bb4d9769d163522ad2c9990ade9128e251daa404bfdbc3a
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-26 17:31:01
    Evidence reason
  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-10-25 10:06:24.862259
    Evidence SHA-256
    8895fe784317ce956fd87b3c03d7dee28c93bf969fb14b515b4f932e1c762121
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 10:06:24.862259
    Evidence reason

Threat Response Pipeline

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

Recorded events: 16. 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
    hellpdesk.net detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Blocklist Detection · OTX Community References · Brand Impersonation · Forensic Evidence Collected · Technical Analysis Recorded · VirusTotal detections +1 · Site Came Back Online · Content Observed Unavailable Recorded: 13 of 13
  • Spamhaus DBL
    Spamhaus DBL recorded: phishing domain
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan classified the page as malicious · Score: 100
  • 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: 5/92
  • Blocklist Detection
    Found in blocklists: OpenPhish
  • OTX Community References
    Community publication references on AlienVault OTX: 32. References are not vendor verdicts and are excluded from the evidence score.
  • Brand Impersonation
    Automated brand label: Phishingtest
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, URLQuery, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
  • VirusTotal detections +1
    New detections: +1 (4 → 5): SOCRadar
  • Site Came Back Online
    The domain is responding again; monitoring resumed
  • Content Observed Unavailable
    Monitoring recorded an unavailable response (HTTP 404); the cause was not independently established.
Notification RecordsSent Report Recorded Recorded: 1 of 1
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: GoDaddy.com, LLC. Abuse contacts: 1.
    • abuse@godaddy.com
Publication & AvailabilityDestroyList Published Recorded: 1 of 1

Recorded activity

5 entries
  1. AlienVault OTX

    32 community references

    View source
  2. VirusTotal

    5/92 engine detections

    View source
  3. Abuse report sent

    PD-20261026-104E16 · Receipt 83465

    abuse@godaddy.com
  4. Added to PhishDestroy

    hellpdesk.net

    View source
  5. URLScan

    Page captured

    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.

hellpdesk.net

Evidence & External Reports

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

Were You Affected by This Site?

6 evidence signal groups linked 1 stored notification records Server error
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.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Immediate steps Find reporting contacts

Official reporting routes

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

Even if funds were frozen, they cannot be recovered without an official police report or court order. Submitting a complaint is the only path to potential recovery.

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.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including hellpdesk.net)
  • 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/hellpdesk.net"
  title="PhishDestroy threat report for hellpdesk.net"
  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>