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

humanres.co.uk

In short

PhishDestroy describes humanres.co.uk, where the captured page returned a Not Found error instead of expected content.

Registrar
Gandi
Resolved IP
Netherlands103.214.5.132HOSTSLIM OU · CDN
Registered
Mar 23, 2017
First observed
Oct 31, 2026
PhishDestroy assessment Critical
95/100
Evidence score
First observed Oct 31, 2026 22:09 UTC · PhishDestroy
VirusTotal detections: 15/92
VirusTotal
engine detections ·
OTX
community references
URLScan
Page captures
open gallery
Domain age
registered 2017-03-23 according to WHOIS
OTX: 4 refs Oct 31, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy describes humanres.co.uk, where the captured page returned a Not Found error instead of expected content.

Critical
VirusTotal
15 / 92
Hosting
Netherlands103.214.5.132HOSTSLIM OU · CDN
Registrar
Gandi
Registered
Mar 23, 2017
OTX
4 community refs
Page captures
9

PhishDestroy analysis, reviewed version

The stored capture of humanres.co.uk shows a plain server error page rather than any interactive content. A bold "Not Found" heading appears at the top, followed by the message "The requested URL was not found on this server." No sign-in form, branding, or interactive control is visible, so the capture records only a static error response with no usable interaction.

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

Source evidenceVirusTotal 15 / 92 · OTX 4 references 7 sources

VirusTotal

15 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 10 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
48
Malicious
12
Suspicious
3
Undetected
29

Vendor labels

CRDF
malicious
DNS8
suspicious
ESET
phishing
VIPRE
phishing
Lionic
phishing
CyRadar
phishing
Webroot
malicious
Fortinet
spam
SOCRadar
phishing
URLQuery
malicious
LevelBlue
phishing
Gridinsoft
suspicious
MalwareURL
phishing
alphaMountain.ai
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Popularity ranks

Alexa
322483
Statvoo
322483
Cloudflare Radar
1000000

First seen

DNS records

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

DNS records observed

JARM fingerprint

29d29d00000000000042d42d000000dd5c266caaa8baaf93008418f7774284

Certificate

Subject alternative names
  • humanres.co.uk
Issuer
Let's Encrypt / YR1
Serial
5238597b38444f075b4f55678cdaa6c1d42
SHA-256
0683e967f9a954a3b0b300ccc2b7a4d42fd26b7c5080f0a0acbecf3755f3a409
Subject
humanres.co.uk
Valid until
Valid from

Registry data (RDAP)

Status
  • active
Registry events
Expiration
Last changed
Registration
Last RDAP database update
Registrar
Gandi
Registrar IANA ID
GANDI
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 48,
    "malicious": 12,
    "suspicious": 3,
    "undetected": 29
}
Vendor labels
{
    "CRDF": "malicious",
    "DNS8": "suspicious",
    "ESET": "phishing",
    "VIPRE": "phishing",
    "Lionic": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Fortinet": "spam",
    "SOCRadar": "phishing",
    "URLQuery": "malicious",
    "LevelBlue": "phishing",
    "Gridinsoft": "suspicious",
    "MalwareURL": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Popularity
{
    "Alexa": 322483,
    "Statvoo": 322483,
    "Cloudflare Radar": 1000000
}
First seen
2023-10-04T23:16:11Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "103.214.5.132"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns1.landingpagerouter.com"
    },
    {
        "ttl": 60,
        "type": "TXT",
        "value": "v=spf1 a mx include:spf.mail.user-training.com ~all"
    },
    {
        "ttl": 3600,
        "type": "SOA",
        "rname": "certificates.usecure.io",
        "value": "ns1.landingpagerouter.com"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns2.landingpagerouter.com"
    }
]
Dns at
2026-10-31T08:59:35Z
Jarm
29d29d00000000000042d42d000000dd5c266caaa8baaf93008418f7774284
Certificate
{
    "san": [
        "humanres.co.uk"
    ],
    "issuer": "Let's Encrypt / YR1",
    "serial": "5238597b38444f075b4f55678cdaa6c1d42",
    "sha256": "0683e967f9a954a3b0b300ccc2b7a4d42fd26b7c5080f0a0acbecf3755f3a409",
    "subject": "humanres.co.uk",
    "valid_to": "2026-12-27T09:48:38Z",
    "valid_from": "2026-09-28T09:48:39Z"
}
Registry data
{
    "status": [
        "active"
    ],
    "events": {
        "expiration": "2027-03-23T15:10:00Z",
        "last changed": "2026-02-22T01:59:57Z",
        "registration": "2017-03-23T15:10:00Z",
        "last update of RDAP database": "2026-06-15T23:16:38Z"
    },
    "registrar": "Gandi",
    "registrar_iana_id": "GANDI"
}
Separate source record · 12 malicious + 3 suspicious / 92 · 2026-10-31 08:59:18 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-31T08:59:18Z
fetched_at
2026-10-31T22:48:52Z
stats
{"timeout":0,"harmless":48,"malicious":12,"suspicious":3,"undetected":29}

URLScan

Malicious

SHA-256 7b7c2d7db3e5ce718fbe0d5c056e3dd2d19b57a6dbb4682daa6b880f44cdaa8f

Open report
URLScanOriginal source recordObserved: 22 fields

Observed: · Retrieved:

Report ID

01a1941a-bf4c-7164-a1e9-281fff59068f

Final URL

https://humanres.co.uk/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://humanres.co.uk/
    From
    http://humanres.co.uk/
    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.110.94
  • 52.92.32.50
  • 2a00:1450:4001:c1f::5f
  • 103.214.5.132

Autonomous systems (ASN)

  • 15169
  • 16509
  • 207083

Server countries

  • US
  • IE
  • DE
  • NL

Document hash

7b7c2d7db3e5ce718fbe0d5c056e3dd2d19b57a6dbb4682daa6b880f44cdaa8f

Script hashes

  • 3085442f6c6a96f3b86ad1ec2ee743804158894546f708ca6eb3b5899c29ec09

JavaScript globals

  • clearImmediate
  • setImmediate
  • usecure

Cookies

  • AWSALBCORS
  • AWSALB

TLS session and certificate

Subject alternative names
  • humanres.co.uk
Cipher
AES_256_GCM
Issuer
YR1
Subject
humanres.co.uk
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

3503

Registered domain age, days

3503

Certificate age, days

33

Certificate validity, days

89

Page requests

18

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
-73
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
01a1941a-bf4c-7164-a1e9-281fff59068f
Final url
https://humanres.co.uk/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://humanres.co.uk/",
        "from": "http://humanres.co.uk/",
        "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.110.94",
    "52.92.32.50",
    "2a00:1450:4001:c1f::5f",
    "103.214.5.132"
]
Asns
[
    "15169",
    "16509",
    "207083"
]
Countries
[
    "US",
    "IE",
    "DE",
    "NL"
]
Document hash
7b7c2d7db3e5ce718fbe0d5c056e3dd2d19b57a6dbb4682daa6b880f44cdaa8f
Script hashes
[
    "3085442f6c6a96f3b86ad1ec2ee743804158894546f708ca6eb3b5899c29ec09"
]
Globals
[
    "clearImmediate",
    "setImmediate",
    "usecure"
]
Cookies
[
    "AWSALBCORS",
    "AWSALB"
]
Tls
{
    "san": [
        "humanres.co.uk"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "YR1",
    "subject": "humanres.co.uk",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-27T09:48:38Z",
    "valid_from": "2026-09-28T09:48:39Z"
}
Domain age days
3503
Apex age days
3503
Tls age days
33
Tls valid days
89
Requests
18
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": -73,
        "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 · date not recorded

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

record_source
domain_monitor.urlscan
uuid
01a193ed-da4c-7175-b170-2c89e775426f
score
null
malicious
null
result_at
null
enriched_at
null
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":null}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

4 community references

Open report

Cloudflare Radar

Scan report

Open report
Cloudflare RadarOriginal source recordObserved: 12 fields

Observed: · Retrieved:

Report ID

f3623498-30a4-48bc-87fd-bdd52b39f6d2

Final URL

https://humanres.co.uk/

HTTP response

404

Navigation history

  • URL
    https://humanres.co.uk/
    Status
    404

DOM structure hash

42065dba3b8a7b2130dd66fe299c26c1aa681d7c7f2893f8410bbcd2d2e1770d

Document hash

9dcc361cf979ea9471e1076ab30724c665229614d2d7432dfe9127c8b6d3a443

Domain risk categories

  • Content Servers
  • Technology

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    humanres.co.uk
    Type
    A
    Value
    103.214.5.132

DNSSEC valid

No

IP address

127.0.1.1

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

Registration record

Registrar
Gandi [Tag = GANDI]
Registered
Updated
Expires
Nameservers
  • ns1.landingpagerouter.com
  • ns2.landingpagerouter.com
Original source fields · JSON
Uuid
f3623498-30a4-48bc-87fd-bdd52b39f6d2
Final url
https://humanres.co.uk/
Status
404
History
[
    {
        "url": "https://humanres.co.uk/",
        "status": 404
    }
]
DOM structure hash
42065dba3b8a7b2130dd66fe299c26c1aa681d7c7f2893f8410bbcd2d2e1770d
Document hash
9dcc361cf979ea9471e1076ab30724c665229614d2d7432dfe9127c8b6d3a443
Domain risks
[
    "Content Servers",
    "Technology"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "humanres.co.uk",
        "type": "A",
        "value": "103.214.5.132"
    }
]
Dnssec valid
false
Ip
127.0.1.1

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

Registration record
{
    "registrar": "Gandi [Tag = GANDI]",
    "created": "2017-03-23T00:00:00Z",
    "updated": "2026-09-28T00:00:00Z",
    "expires": "2027-03-23T00:00:00Z",
    "nameservers": [
        "ns1.landingpagerouter.com",
        "ns2.landingpagerouter.com"
    ]
}

Google Safe Browsing

No threat flag

Open report

PhishDestroy DOM

10 / 100 · heuristic score · 2 brand references · 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
humanres.co.uk captured page returns a Not Found error
ai_description
PhishDestroy describes humanres.co.uk, where the captured page returned a Not Found error instead of expected content.
ai_summary
The stored capture of humanres.co.uk shows a plain server error page rather than any interactive content. A bold "Not Found" heading appears at the top, followed by the message "The requested URL was not found on this server." No sign-in form, branding, or interactive control is visible, so the capture records only a static error response with no usable interaction. The stored VirusTotal domain result reports 15 detections out of 92 engines. CRDF reported "malicious"; DNS8 reported "suspicious".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-10-31 23:55:03
revision
98a9dcba45b2ef046878205813f0c1d3217162bf4e66b550e2ad6c920c235991
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: 18 fields

Mail configuration

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

CAA records

Domain
humanres.co.uk

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
4
Archived days
9
Snapshots per day
0
Average page size, bytes
821

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
    ns1.landingpagerouter.com
  • IP address
    103.214.5.132
    Host
    ns2.landingpagerouter.com
DNS zone
humanres.co.uk

Location

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

TLS certificate

Issuer
Let's Encrypt / YR1
Subject
humanres.co.uk

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
1793485070
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

Popularity rank

Domain
humanres.co.uk

Subdomains

Count
3
Subdomains
  • staging.humanres.co.uk
  • testing.humanres.co.uk
  • www.humanres.co.uk

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": "humanres.co.uk"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2025-02-06T16:46:35Z",
    "first": "2018-08-10T10:58:51Z",
    "changes": 4,
    "days_archived": 9,
    "scans_per_day": 0,
    "avg_page_bytes": 821
}
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": "ns1.landingpagerouter.com"
        },
        {
            "ip": "103.214.5.132",
            "host": "ns2.landingpagerouter.com"
        }
    ],
    "zone": "humanres.co.uk"
}
Location
{
    "ip": "103.214.5.132",
    "asn": "207083",
    "org": "HOSTSLIM OU",
    "city": "Lelystad",
    "country": "NL"
}
Ssl
{
    "issuer": "Let's Encrypt / YR1",
    "subject": "humanres.co.uk"
}
DNS records
{
    "A": [
        "103.214.5.132"
    ],
    "NS": [
        "ns2.landingpagerouter.com",
        "ns1.landingpagerouter.com"
    ],
    "SOA": "{\"nsname\": \"ns1.landingpagerouter.com\", \"hostmaster\": \"certificates.usecure.io\", \"serial\": 1793485070, \"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
}
Rank
{
    "domain": "humanres.co.uk"
}
Subdomains
{
    "count": 3,
    "subdomains": [
        "staging.humanres.co.uk",
        "testing.humanres.co.uk",
        "www.humanres.co.uk"
    ]
}
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 humanres.co.uk

Is humanres.co.uk legit?

PhishDestroy describes humanres.co.uk, where the captured page returned a Not Found error instead of expected content.

Is humanres.co.uk safe to connect a wallet?

This report does not record which wallet requests humanres.co.uk 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 humanres.co.uk?

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

Last checked

Stored Capture · 9 captures

All capture links and hashes (9)

Domain details

Domain
IP Context Netherlands103.214.5.132 Amazon CloudFront shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
RegistrationCreated Mar 23, 2017 — Expires Mar 23, 2027
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 31, 2026
DOM Analysisanalyzed Oct 31, 2026score 10/1002 brand signals
Submitted URLhttp://humanres.co.uk/?… query redacted
Automated brand references
Google Microsoft
TLS Certificate
Issued by Let's Encrypt / YR1 · stored validity ends in 56 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Netherlands103.214.5.132
Network ASN
AS207083
Organization
HOSTSLIM OU
Observed location
NetherlandsLelystad, 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: 1793485070
  • refresh: 3600
  • retry: 900
  • expire: 1209600
  • minttl: 60

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR1
Valid from
2026-09-28 09:48:39
Valid until
2026-12-27 09:48:38
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint0683e967f9a954a3b0b300ccc2b7a4d42fd26b7c5080f0a0acbecf3755f3a409
Certificate names · 1 SAN
  • humanres.co.uk

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

Recorded subdomains3

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

  • staging.humanres.co.ukDomain record
  • testing.humanres.co.ukDomain record
  • www.humanres.co.ukDomain record
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

15 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 15 detections
alphaMountain.ai
CRDF
CyRadar
DNS8
ESET
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
LevelBlue
Lionic
MalwareURL
SOCRadar
URLQuery
VIPRE
Webroot
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of humanres.co.uk · checked Oct 31, 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.45 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://humanres.co.uk/
Final URL: https://humanres.co.uk/
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
Sat, 31 Oct 2026 22:10:02 GMT
Etag
W/"482c-AE9ZlQHkO0VRiUp9bakO1gIqYfA"
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 ed52b6cbe30df623c9ae923641ddf518.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.

Captured network requests

Network requests: 18 SHA-256 hashes: 17 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-10-31 22:39 UTC.

Open this scan on URLScan 01a1941a-bf4c-7164-a1e9-281fff59068f ↗

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

    Unavailable→Reachable

  2. Domain monitor · Recorded state

    Reachable→Unavailable

All retained availability observations2

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

  1. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 23:15:25.574906
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  2. 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-30 17:14:28.389060
    Evidence SHA-256
    21712fa93c42dbe273472efc1fb1dc4b80cb1c93483cea1c8ffec553fe67c289
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 17:14:28.389060
    Evidence reason

Threat Response Pipeline

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

Recorded events: 11. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested Recorded: 1 of 1
  • Threat Ingested
    humanres.co.uk detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · OTX Community References · Forensic Evidence Collected · Technical Analysis Recorded · Site Came Back Online · Content Observed Unavailable Recorded: 9 of 9
  • 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: 15/92
  • OTX Community References
    Community publication references on AlienVault OTX: 4. References are not vendor verdicts and are excluded from the evidence score.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
  • 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.
Publication & AvailabilityDestroyList Published Recorded: 1 of 1

Recorded activity

4 entries
  1. AlienVault OTX

    4 community references

    View source
  2. URLScan

    Page captured

    View source
  3. Added to PhishDestroy

    humanres.co.uk

    View source
  4. VirusTotal

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

Check for cloaking

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

humanres.co.uk

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

4 evidence signal groups linked Unverified
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Official reporting routes

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.

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 humanres.co.uk)
  • 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

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.

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/humanres.co.uk"
  title="PhishDestroy threat report for humanres.co.uk"
  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>