Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 13. 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
2hgu1.com favicon

2hgu1.com

In short

PhishDestroy records that 2hgu1.com displayed only a Spanish "Cargando..." loading spinner while its HTML title read "shopify".

“shopify”

Review the evidence
Registrar
United StatesDynadot
Resolved IP
United States107.173.157.165HostPapa
Registered
Oct 27, 2026
First observed
Nov 1, 2026
PhishDestroy assessment Critical
99/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 13/92 Stored blocklist matches: 1 Young domain: 4 days old
VirusTotal
13 / 92
engine detections ·
Blocklist matches
1
OpenPhish
URLScan
Malicious
Cloudflare Radar
Phishing
Page captures
5
open gallery
Domain age
4 days
registered 2026-10-27 according to WHOIS
Nov 1, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy records that 2hgu1.com displayed only a Spanish "Cargando..." loading spinner while its HTML title read "shopify".

Critical
Status
Last known active
VirusTotal
13 / 92
Blocklist matches
1
Hosting
United States107.173.157.165HostPapa
Registrar
United StatesDynadot
Registered
Oct 27, 2026
Page captures
5
Page captures Source results Registration record

PhishDestroy analysis, reviewed version

The captured 2hgu1.com page shows a dark overlay with a centered spinner and the Spanish text "Cargando...", meaning the page was still loading when the screenshot was taken. No shop, form, or other content had rendered, so the main interaction available to a visitor was simply waiting for the loading indicator to finish. The HTML title "shopify" conflicts with this empty loading state, since it suggests a storefront that never appeared in the capture.

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

Source evidenceVirusTotal 13 / 92 7 sources

VirusTotal

13 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
48
Malicious
12
Suspicious
1
Undetected
31

Vendor labels

CRDF
malicious
DNS8
suspicious
Lionic
phishing
Webroot
malicious
Emsisoft
phishing
Fortinet
phishing
Netcraft
malicious
SOCRadar
malicious
LevelBlue
phishing
OpenPhish
phishing
Seclookup
malicious
Gridinsoft
phishing
alphaMountain.ai
phishing

Reputation score

0

Registrar

Dynadot Inc

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    nancy.ns.cloudflare.com
  • TTL, seconds
    21600
    Type
    NS
    Value
    sean.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    107.173.157.165
  • TTL, seconds
    300
    Type
    A
    Value
    23.94.73.138
  • TTL, seconds
    21600
    Type
    NS
    Value
    nancy.ns.cloudflare.com

DNS records observed

JARM fingerprint

2ad2ad0002ad2ad22c42d42d000000307ee0eb468e9fdb5cfcd698a80a67ef

Certificate

Subject alternative names
  • *.2hgu1.com
  • 2hgu1.com
Issuer
Let's Encrypt / YR2
Serial
66cb1ef4dc9ea2f99ef23601e3a4b765093
SHA-256
bd5e24505ef898cc4246fa93b984c4f34fc592a76814846f9299b162dbe132cc
Subject
2hgu1.com
Valid until
Valid from

Registration record

Registrar
Dynadot Inc
Registrar IANA ID
472
Registrar URL
http://www.dynadot.com
Registered
Updated
Expires
Status
  • clientTransferProhibited
Nameservers
  • nancy.ns.cloudflare.com
  • sean.ns.cloudflare.com
DNSSEC
unsigned

Registry data (RDAP)

Status
  • transfer prohibited
Registry events
Expiration
Last changed
Registration
Registrar expiration
Last RDAP database update
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 48,
    "malicious": 12,
    "suspicious": 1,
    "undetected": 31
}
Vendor labels
{
    "CRDF": "malicious",
    "DNS8": "suspicious",
    "Lionic": "phishing",
    "Webroot": "malicious",
    "Emsisoft": "phishing",
    "Fortinet": "phishing",
    "Netcraft": "malicious",
    "SOCRadar": "malicious",
    "LevelBlue": "phishing",
    "OpenPhish": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "phishing",
    "alphaMountain.ai": "phishing"
}
Reputation
0
Registrar
Dynadot Inc
Created
2026-10-27T16:26:24Z
Expires
2027-10-27T16:26:24Z
Updated
2026-10-27T16:32:24Z
First seen
2026-10-27T16:44:44Z
DNS records
[
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "nancy.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "sean.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "107.173.157.165"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "23.94.73.138"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "nancy.ns.cloudflare.com"
    }
]
Dns at
2026-11-01T12:21:35Z
Jarm
2ad2ad0002ad2ad22c42d42d000000307ee0eb468e9fdb5cfcd698a80a67ef
Certificate
{
    "san": [
        "*.2hgu1.com",
        "2hgu1.com"
    ],
    "issuer": "Let's Encrypt / YR2",
    "serial": "66cb1ef4dc9ea2f99ef23601e3a4b765093",
    "sha256": "bd5e24505ef898cc4246fa93b984c4f34fc592a76814846f9299b162dbe132cc",
    "subject": "2hgu1.com",
    "valid_to": "2027-01-25T15:41:03Z",
    "valid_from": "2026-10-27T15:41:04Z"
}
Registration record
{
    "registrar": "Dynadot Inc",
    "registrar_iana_id": "472",
    "registrar_url": "http://www.dynadot.com",
    "created": "2026-10-27T16:26:24Z",
    "updated": "2026-10-27T16:32:24Z",
    "expires": "2027-10-27T16:26:24Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "nancy.ns.cloudflare.com",
        "sean.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "transfer prohibited"
    ],
    "events": {
        "expiration": "2027-10-27T16:26:24Z",
        "last changed": "2026-10-27T16:32:24Z",
        "registration": "2026-10-27T16:26:24Z",
        "registrar expiration": "2027-10-27T16:26:24Z",
        "last update of RDAP database": "2026-10-27T16:36:52Z"
    }
}
Separate source record · 12 malicious + 1 suspicious / 92 · 2026-11-01 12:21:16 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-11-01T12:21:16Z
fetched_at
2026-11-01T12:26:07Z
stats
{"timeout":0,"harmless":48,"malicious":12,"suspicious":1,"undetected":31}

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 15 fields

Observed: · Retrieved:

Report ID

ee96d502-e4dd-44df-b7ae-4737d2586963

Final URL

https://2hgu1.com/

HTTP response

200

Navigation history

  • URL
    https://2hgu1.com/
    Status
    200

DOM structure hash

595f5e66f22b20cb59ef218da3fa955067ff51d7a3a8f1a7107462929ba85794

Document hash

f30ea6ac97e61478266219a07fd34f2fa599ef4dec9745da689a62e1322c43e2

Phishing classifier result

  • phishing

URL risk categories

  • Phishing

Domain risk categories

  • Newly Seen Domains
  • Security Risks
  • Phishing
  • Security threats
  • New Domains
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    2hgu1.com
    Type
    A
    Value
    107.173.157.165
  • Name
    2hgu1.com
    Type
    A
    Value
    23.94.73.138

DNSSEC valid

No

IP address

127.0.1.12

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

Verdict

Tags
  • phishing
Malicious
Yes
Categories
  • phishing

Registration record

Registrar
Dynadot Inc
Registered
Updated
Expires
Nameservers
  • nancy.ns.cloudflare.com
  • sean.ns.cloudflare.com
Original source fields · JSON
Uuid
ee96d502-e4dd-44df-b7ae-4737d2586963
Final url
https://2hgu1.com/
Status
200
History
[
    {
        "url": "https://2hgu1.com/",
        "status": 200
    }
]
DOM structure hash
595f5e66f22b20cb59ef218da3fa955067ff51d7a3a8f1a7107462929ba85794
Document hash
f30ea6ac97e61478266219a07fd34f2fa599ef4dec9745da689a62e1322c43e2
Phishing v2
[
    "phishing"
]
Url risks
[
    "Phishing"
]
Domain risks
[
    "Newly Seen Domains",
    "Security Risks",
    "Phishing",
    "Security threats",
    "New Domains",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "2hgu1.com",
        "type": "A",
        "value": "107.173.157.165"
    },
    {
        "name": "2hgu1.com",
        "type": "A",
        "value": "23.94.73.138"
    }
]
Dnssec valid
false
Ip
127.0.1.12

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

Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
Registration record
{
    "registrar": "Dynadot Inc",
    "created": "2026-10-27T16:26:24Z",
    "updated": "2026-10-27T16:32:24Z",
    "expires": "2027-10-27T16:26:24Z",
    "nameservers": [
        "nancy.ns.cloudflare.com",
        "sean.ns.cloudflare.com"
    ]
}
Separate stored summary: Not recorded · observation date not recorded

This summary differs from the dated scan above. It is retained for provenance and does not override the selected source observation.

verdict
null
categories
[]
observed_at
null
source_path
phishdestroy.technologies.cf_radar
scope
Separate stored summary; an absent observation date is not evidence of a clean scan.

URLScan

Malicious

SHA-256 f30ea6ac97e61478266219a07fd34f2fa599ef4dec9745da689a62e1322c43e2

Open report
URLScanOriginal source recordObserved: 23 fields

Observed: · Retrieved:

Report ID

01a19714-576d-738e-8e90-187d7f884149

Final URL

https://2hgu1.com/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://2hgu1.com/
    From
    http://2hgu1.com/
    Status
    307

IP address

23.94.73.138

Reverse DNS (PTR)

capacityform.net

Contacted domains

  • a7nkq.vip

Contacted IP addresses

  • 45.200.17.1
  • 23.94.73.138

Autonomous systems (ASN)

  • 54801
  • 36352

Server countries

  • HK
  • US

Document hash

f30ea6ac97e61478266219a07fd34f2fa599ef4dec9745da689a62e1322c43e2

Script hashes

  • 04a5f825214114fe21cb33567faeccca67bb22a604e7026d0082775f156e97d5
  • f6d1837b6822b528d420edc52cf4c19536df9b69a2740ca51649229ab75a3669
  • 7ebe346311ea5c27d7a39614973c9e5b06e9fcb659839093e10aefc6c4fd2b3d
  • 3b6ff8361fd37335dee32bd0b7f005d12bb460754dc81f526a5bcc230d2c9b8c

JavaScript globals

  • webpackChunkshopify
  • clearImmediate
  • setImmediate

Browser storage keys

  • lang
  • systemConfig

TLS session and certificate

Subject alternative names
  • *.2hgu1.com
  • 2hgu1.com
Cipher
AES_256_GCM
Issuer
YR2
Subject
2hgu1.com
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

4

Registered domain age, days

4

Certificate age, days

4

Certificate validity, days

89

Page requests

12

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
98
Malicious
Yes
Overall verdict
Tags
  • phishing
Score
100
Brands
  • shopify
Malicious
Yes
Categories
  • phishing
URLScan verdict
Tags
  • phishing
Score
100
Brands
  • Shopify
Malicious
Yes
Categories
  • phishing

HTTP headers

Server
nginx
Content-type
text/html
Strict-transport-security
max-age=31536000
Original source fields · JSON
Uuid
01a19714-576d-738e-8e90-187d7f884149
Final url
https://2hgu1.com/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://2hgu1.com/",
        "from": "http://2hgu1.com/",
        "status": 307
    }
]
Ip
23.94.73.138
Ptr
capacityform.net
Contacted domains
[
    "a7nkq.vip"
]
Contacted IP addresses
[
    "45.200.17.1",
    "23.94.73.138"
]
Asns
[
    "54801",
    "36352"
]
Countries
[
    "HK",
    "US"
]
Document hash
f30ea6ac97e61478266219a07fd34f2fa599ef4dec9745da689a62e1322c43e2
Script hashes
[
    "04a5f825214114fe21cb33567faeccca67bb22a604e7026d0082775f156e97d5",
    "f6d1837b6822b528d420edc52cf4c19536df9b69a2740ca51649229ab75a3669",
    "7ebe346311ea5c27d7a39614973c9e5b06e9fcb659839093e10aefc6c4fd2b3d",
    "3b6ff8361fd37335dee32bd0b7f005d12bb460754dc81f526a5bcc230d2c9b8c"
]
Globals
[
    "webpackChunkshopify",
    "clearImmediate",
    "setImmediate"
]
Storage keys
[
    "lang",
    "systemConfig"
]
Tls
{
    "san": [
        "*.2hgu1.com",
        "2hgu1.com"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "YR2",
    "subject": "2hgu1.com",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-25T15:41:03Z",
    "valid_from": "2026-10-27T15:41:04Z"
}
Domain age days
4
Apex age days
4
Tls age days
4
Tls valid days
89
Requests
12
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 98,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "shopify"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "Shopify"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "nginx",
    "content-type": "text/html",
    "strict-transport-security": "max-age=31536000"
}
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
01a19714-576d-738e-8e90-187d7f884149
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

no community references

Open report

Google Safe Browsing

No threat flag

Open report

PhishDestroy DOM

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

Open report
Separate monitor score · 10 / 100 · 2026-11-01T12:41:35Z

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

record_source
domain_monitor.dom_analysis
heuristic_score
10
analyzed_at
2026-11-01T12:41:35Z
source_timestamp
2026-11-01 13:41:35
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
2hgu1.com loading screen with Shopify page title
ai_description
PhishDestroy records that 2hgu1.com displayed only a Spanish "Cargando..." loading spinner while its HTML title read "shopify".
ai_summary
The captured 2hgu1.com page shows a dark overlay with a centered spinner and the Spanish text "Cargando...", meaning the page was still loading when the screenshot was taken. No shop, form, or other content had rendered, so the main interaction available to a visitor was simply waiting for the loading indicator to finish. The HTML title "shopify" conflicts with this empty loading state, since it suggests a storefront that never appeared in the capture. The stored VirusTotal domain result reports 13 detections out of 92 engines. CRDF reported "malicious"; DNS8 reported "suspicious".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-11-01 13:27:56
revision
6b00804844eb341841fe46d2139e08f8c0c8b95f52fa13cda18c1e75248cbcf0
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: 22 fields

Mail configuration

SPF lookups
0

CAA records

Domain
2hgu1.com

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

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

Page title and metadata

Page title
shopify

Trackers

Requests
8

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
2
TLS
357
Waiting
168
Connection
165
Download
0
Response time, ms
692

TLS connection

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

Ports

Open ports
  • 80
  • 443

Carbon estimate

Bytes
757
CO₂, grams
0
Cleaner than, %
95

DNS servers

Nameservers
  • IP address
    172.64.34.84
    Host
    nancy.ns.cloudflare.com
  • IP address
    108.162.193.231
    Host
    sean.ns.cloudflare.com
DNS zone
2hgu1.com

Location

IP address
107.173.157.165
ASN
36352
Organization
HostPapa
City
Santa Clara
Country
US

TLS certificate

Issuer
Let's Encrypt / YR2
Subject
2hgu1.com

DNS records

A
  • 107.173.157.165
  • 23.94.73.138
NS
  • nancy.ns.cloudflare.com
  • sean.ns.cloudflare.com
SOA
Primary nameserver
nancy.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2418733278
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Header value
max-age=31536000
Observation
HSTS header does not include all subdomains.

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
max-age=31536000
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
23.94.73.138
IP version
4

Redirects

Redirect chain
  • https://2hgu1.com

Registration record

Registrar
Dynadot Inc
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • nancy.ns.cloudflare.com
  • sean.ns.cloudflare.com

HTTP headers

Response headers
Server
nginx
Content-type
text/html
Strict-transport-security
max-age=31536000
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "2hgu1.com"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-11-01T12:21:56Z",
    "first": "2026-11-01T12:21:56Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 949
}
Page title and metadata
{
    "title": "shopify"
}
Trackers
{
    "requests": 8
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 2,
        "tls": 357,
        "wait": 168,
        "connect": 165,
        "download": 0
    },
    "response_ms": 692
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1",
        "TLSv1.1",
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Carbon
{
    "bytes": 757,
    "co2_grams": 0,
    "cleaner_than": 95
}
Dns server
{
    "ns": [
        {
            "ip": "172.64.34.84",
            "host": "nancy.ns.cloudflare.com"
        },
        {
            "ip": "108.162.193.231",
            "host": "sean.ns.cloudflare.com"
        }
    ],
    "zone": "2hgu1.com"
}
Location
{
    "ip": "107.173.157.165",
    "asn": "36352",
    "org": "HostPapa",
    "city": "Santa Clara",
    "country": "US"
}
Ssl
{
    "issuer": "Let's Encrypt / YR2",
    "subject": "2hgu1.com"
}
DNS records
{
    "A": [
        "107.173.157.165",
        "23.94.73.138"
    ],
    "NS": [
        "nancy.ns.cloudflare.com",
        "sean.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"nancy.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2418733278, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=31536000",
    "message": "HSTS header does not include all subdomains."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": "max-age=31536000",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "23.94.73.138",
    "family": 4
}
Redirects
{
    "chain": [
        "https://2hgu1.com"
    ]
}
Registration record
{
    "registrar": "Dynadot Inc",
    "created": "2026-10-27T16:26:24Z",
    "updated": "2026-10-27T16:32:24Z",
    "expires": "2027-10-27T16:26:24Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "nancy.ns.cloudflare.com",
        "sean.ns.cloudflare.com"
    ]
}
HTTP headers
{
    "headers": {
        "server": "nginx",
        "content-type": "text/html",
        "strict-transport-security": "max-age=31536000"
    }
}

Questions about 2hgu1.com

Is 2hgu1.com legit?

PhishDestroy records that 2hgu1.com displayed only a Spanish "Cargando..." loading spinner while its HTML title read "shopify".

Is 2hgu1.com safe to connect a wallet?

This report does not record which wallet requests 2hgu1.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 2hgu1.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 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 · 5 captures

Cloudflare Radar 1 / 5 Used in the analysis Source file SHA-256: 57c38c7dfa99d289b8371079ad97a51fcc43ecc947aab46183528ae99462af05 SHA-256 of the prepared copy given to the model: 10cf56e6fa22af9a0d282f406f63b3f29651fff11382a90dc507b75ff938935e
SourceCloudflare Radar
Recorded
StateStored capture
HTTP status200
Final URLhttps://2hgu1.com/
Position1 / 5
Open capture Source Report Wayback Download
All capture links and hashes (5)

Domain details

Domain
IP Reputation United States107.173.157.165 abuse score 0/100 0 reports checked Nov 1, 2026
Registrar Dynadot US(US)
Abuse contactreportabuse@racknerd.com, abuse@dynadot.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for 2hgu1.com →
RegistrationCreated Oct 27, 2026 (4d · Brand New!) — Expires Oct 27, 2027
WHOIS statusclientTransferProhibited
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedNov 1, 2026
DOM Analysisanalyzed Nov 1, 2026score 10/1001 brand signal
Submitted URLhttp://2hgu1.com/
Favicon Hash
Observed page title
shopify
Automated brand references
Shopify
TLS Certificate
Issued by Let's Encrypt / YR2 · stored validity ends in 85 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
United States107.173.157.165
Network ASN
AS36352
Organization
HostPapa
Observed location
United StatesSanta Clara, US
Server header
nginx

Nameservers 2

  • nancy.ns.cloudflare.com
  • sean.ns.cloudflare.com

SOA

  • nsname: nancy.ns.cloudflare.com
  • hostmaster: dns.cloudflare.com
  • serial: 2418733278
  • refresh: 10000
  • retry: 2400
  • expire: 604800
  • minttl: 1800

Registrar abuse contact VirusTotal WHOIS

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR2
Valid from
2026-10-27 15:41:04
Valid until
2027-01-25 15:41:03
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintbd5e24505ef898cc4246fa93b984c4f34fc592a76814846f9299b162dbe132cc
Certificate names · 2 SANs
  • *.2hgu1.com
  • 2hgu1.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 · 107.173.157.165rapiddns.io
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

13 / 92 security vendors flagged this domain
View on VT
Last analyzed
alphaMountain.ai
CRDF
DNS8
Emsisoft
Fortinet
Gridinsoft
LevelBlue
Lionic
Netcraft
OpenPhish
Seclookup
SOCRadar
Webroot
Site Performance Analysis

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

86
Needs Work
Performance
FCP
1.2 s
First Contentful Paint
LCP
2.96 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
35 ms
Total Blocking Time
SI
8.41 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://2hgu1.com/
Final URL: https://2hgu1.com/
shopify
Response
HTTP 200
HTML body
757 B
Compressed
439 B
Links
0 internal · 0 external
Detected technologies
nginx
Selected response headers
Server: nginx
Content-Type: text/html
Security headers present
Strict-Transport-Security
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 9
Accept-Ranges
bytes
Content-Length
757
Content-Type
text/html
Date
Sun, 01 Nov 2026 12:22:17 GMT
Etag
"6ae6d01d-2f5"
Last-Modified
Sun, 01 Nov 2026 05:37:33 GMT
Server
nginx
Strict-Transport-Security
max-age=31536000
X-Cache
MISS from cb2rnsj240709-R60531

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

Archived

Captured network requests

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

Open this scan on URLScan 01a19714-576d-738e-8e90-187d7f884149 ↗

Stored observation history1

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

  1. Domain monitor · First collection record

    Reachable

All retained availability 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
    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 13:29:36.000000
    Evidence SHA-256
    a8b2a0408754d8eabb2419f19445fdbe4569ef0e0de62aa977efc7d9c61a3cfc
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 13:29:36
    Evidence reason
  2. 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 13:29:36.000000
    Evidence SHA-256
    a8b2a0408754d8eabb2419f19445fdbe4569ef0e0de62aa977efc7d9c61a3cfc
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 13:29:36
    Evidence reason
  3. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 13:26:00.186050
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

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

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

Pre-emptive Discovery & IngestionThreat Ingested Recorded: 1 of 1
  • Threat Ingested
    2hgu1.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Blocklist Detection · Automated brand label: Shopify · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 8 of 8
  • 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: 13/92
  • Blocklist Detection
    Found in blocklists: OpenPhish
  • Automated brand label: Shopify
    Collector label, not confirmed by a page check.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

4 entries
  1. URLScan

    Page captured

    View source
  2. Cloudflare Radar

    Phishing

    View source
  3. Added to PhishDestroy

    2hgu1.com

    View source
  4. VirusTotal

    13/92 engine detections

    View source
How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

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

Check for cloaking

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

2hgu1.com

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 13 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 2hgu1.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/2hgu1.com"
  title="PhishDestroy threat report for 2hgu1.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>