Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 9/92 engines flagged. malicious: 9. suspicious: 0. Analysis time (as stored): 2026-10-24T01:48:08Z. Retrieved (as stored): 2026-10-25T13:27:24Z. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Redirect recorded hentaimam.ioww19.hentaimam.io Details
Domain security and threat intelligence
hentaimam.io favicon

hentaimam.io

In short

PhishDestroy first recorded hentaimam.io on 2026-10-25. Stored VirusTotal result: 9/92 engines flagged. malicious: 9. suspicious: 0. Analysis time (as stored): 2026-10-24T01:48:08Z. Retrieved (as stored): 2026-10-25T13:27:24Z.

Review the evidence
Registrar
CommuniGal Communication
Resolved IP
Netherlands212.92.105.27NForce Entertainment B.V.
Registered
Mar 11, 2026
First observed
Oct 25, 2026
PhishDestroy assessment Critical
91/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 9/92
VirusTotal
9 / 92
engine detections ·
URLQuery
2
detections
OTX
3
community references
URLScan
Malicious
engine verdict · score 47
Page captures
5
open gallery
Domain age
236 days
registered 2026-03-11 according to WHOIS · source data differ
Reports sent
1
view timeline
OTX: 3 refs Oct 25, 2026 1 Report Sent
X Telegram API
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@nforce.com. The latest stored availability evidence still shows the domain reachable; 8 days has elapsed since the first outgoing report.

ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.

Elapsed since first report
8 days
Reports sent
1
Latest case ID
PD-20261025-225803
Current status
HTTP 302 at latest stored check

Analysis

Domain summary

PhishDestroy first recorded hentaimam.io on 2026-10-25. Stored VirusTotal result: 9/92 engines flagged. malicious: 9. suspicious: 0. Analysis time (as stored): 2026-10-24T01:48:08Z. Retrieved (as stored): 2026-10-25T13:27:24Z. Risk: critical (91/100). Registrar: CommuniGal Communication. Status: Last known active. Hosting: NForce Entertainment B.V. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
9 / 92
Hosting
Netherlands212.92.105.27NForce Entertainment B.V.
Registrar
CommuniGal Communication
Registered
Mar 11, 2026
OTX
3 community refs
Page captures
5
Page captures Source results Registration record

Recorded source summary

PhishDestroy stores a record for hentaimam.io. Source observations are dated separately; missing checks do not establish safety.

A reviewed analysis is not available for this text revision. Consult the dated source records below.

Source evidenceVirusTotal 9 / 92 · OTX 3 references 8 sources

VirusTotal

9 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
49
Malicious
9
Suspicious
0
Undetected
34

Vendor labels

Bkav
malicious
G-Data
phishing
Lionic
malicious
Sophos
phishing
Fortinet
malware
Kaspersky
phishing
BitDefender
phishing
alphaMountain.ai
phishing
Forcepoint ThreatSeeker
malicious

Reputation score

0

Categories

Sophos
phishing and fraud
alphaMountain.ai
Phishing (alphaMountain.ai)
Forcepoint ThreatSeeker
malicious web sites

Popularity ranks

Alexa
623161
Statvoo
623161

Created

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    NS
    Value
    ns2.hostresolver.com
  • TTL, seconds
    300
    Type
    A
    Value
    185.150.189.124
  • TTL, seconds
    300
    Type
    TXT
    Value
    dbg: src: ds, acme: false
  • TTL, seconds
    300
    Type
    SOA
    Responsible mailbox
    admin.hentaimam.io
    Value
    ns1.hostresolver.com
  • TTL, seconds
    300
    Type
    NS
    Value
    ns1.hostresolver.com

DNS records observed

JARM fingerprint

15d3fd16d00000000042d3fd15d41dedf6065fb8c7975035175313dd1ae342

Certificate

Subject alternative names
  • *.hentaimam.io
  • hentaimam.io
Issuer
Let's Encrypt / YR2
Serial
6b28d928097cde52c5202700b0d36771ced
SHA-256
8b88968427245a6d41f78ed666a6f5057993cd637eee8cab7dd3532ed94a8b51
Subject
hentaimam.io
Valid until
Valid from

Registry data (RDAP)

Status
  • clientTransferProhibited
Registry events
Expiration
Registration
Registrar expiration
Last RDAP database update
Registrar
Gal Communication (CommuniGal) Ltd.
Registrar IANA ID
418
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 49,
    "malicious": 9,
    "suspicious": 0,
    "undetected": 34
}
Vendor labels
{
    "Bkav": "malicious",
    "G-Data": "phishing",
    "Lionic": "malicious",
    "Sophos": "phishing",
    "Fortinet": "malware",
    "Kaspersky": "phishing",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "malicious"
}
Reputation
0
Categories
{
    "Sophos": "phishing and fraud",
    "alphaMountain.ai": "Phishing (alphaMountain.ai)",
    "Forcepoint ThreatSeeker": "malicious web sites"
}
Popularity
{
    "Alexa": 623161,
    "Statvoo": 623161
}
Created
2026-03-11T00:00:00Z
Updated
2026-03-16T00:00:00Z
First seen
2024-03-06T06:24:10Z
DNS records
[
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns2.hostresolver.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "185.150.189.124"
    },
    {
        "ttl": 300,
        "type": "TXT",
        "value": "dbg: src: ds, acme: false"
    },
    {
        "ttl": 300,
        "type": "SOA",
        "rname": "admin.hentaimam.io",
        "value": "ns1.hostresolver.com"
    },
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns1.hostresolver.com"
    }
]
Dns at
2026-10-24T01:48:37Z
Jarm
15d3fd16d00000000042d3fd15d41dedf6065fb8c7975035175313dd1ae342
Certificate
{
    "san": [
        "*.hentaimam.io",
        "hentaimam.io"
    ],
    "issuer": "Let's Encrypt / YR2",
    "serial": "6b28d928097cde52c5202700b0d36771ced",
    "sha256": "8b88968427245a6d41f78ed666a6f5057993cd637eee8cab7dd3532ed94a8b51",
    "subject": "hentaimam.io",
    "valid_to": "2027-01-13T08:29:33Z",
    "valid_from": "2026-10-15T08:29:34Z"
}
Registry data
{
    "status": [
        "clientTransferProhibited"
    ],
    "events": {
        "expiration": "2027-03-11T05:00:00Z",
        "registration": "2026-03-11T19:16:02Z",
        "registrar expiration": "2027-03-11T05:00:00Z",
        "last update of RDAP database": "2026-10-24T01:48:27Z"
    },
    "registrar": "Gal Communication (CommuniGal) Ltd.",
    "registrar_iana_id": "418"
}
Separate collector summary

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

source
VirusTotal
scope
unknown
result_state
observed
numerator
9
denominator
92
malicious
null
suspicious
null
vendors
["alphaMountain.ai","BitDefender","Bkav","Forcepoint ThreatSeeker","Fortinet","G-Data","Kaspersky","Lionic","Sophos"]
observed_at
2026-10-24 01:48:08
checked_at
2026-10-25 14:27:24
fetched_at
2026-10-25 13:27:25
time_basis
as stored; legacy timezone not established

URLScan

Malicious · engine verdict · score 47

Open report
URLScanOriginal source recordObserved: 17 fields

Observed: · Retrieved:

Report ID

01a1731f-d4f3-778f-a663-a68ee2be0f64

Final URL

http://ww19.hentaimam.io/

HTTP response

200

Redirect type

parent-domain

Redirects

  • To
    https://hentaimam.io/
    From
    http://hentaimam.io/
    Status
    307
  • To
    http://ww19.hentaimam.io/
    From
    https://hentaimam.io/
    Status
    302
  • To
    https://ww19.hentaimam.io/
    From
    http://ww19.hentaimam.io/
    Status
    307
  • To
    http://ww19.hentaimam.io/
    From
    https://ww19.hentaimam.io/
    Status
    307

IP address

208.91.196.145

Contacted domains

  • hentaimam.io

Contacted IP addresses

  • 208.91.196.145
  • 185.150.189.124

Autonomous systems (ASN)

  • 40034
  • 23470

Server countries

  • VG
  • US

Document hash

8f2bfe0930e83fac5390c0423d979f5ddf50a09d9646524f57809e68b067219f

Cookies

  • sid

Domain age, days

0

Differs from the registration date in WHOIS (2026-03-11), which gives 227 days on the scan date 2026-10-25. The two sources disagree; both values are kept as recorded.

Registered domain age, days

1938

Differs from the registration date in WHOIS (2026-03-11), which gives 227 days on the scan date 2026-10-25. The two sources disagree; both values are kept as recorded.

Page requests

2

Provider verdicts

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

HTTP headers

Server
nginx/1.28.0
Content-type
text/html
Via
1.1 google
Original source fields · JSON
Uuid
01a1731f-d4f3-778f-a663-a68ee2be0f64
Final url
http://ww19.hentaimam.io/
Status
200
Redirected
parent-domain
Redirects
[
    {
        "to": "https://hentaimam.io/",
        "from": "http://hentaimam.io/",
        "status": 307
    },
    {
        "to": "http://ww19.hentaimam.io/",
        "from": "https://hentaimam.io/",
        "status": 302
    },
    {
        "to": "https://ww19.hentaimam.io/",
        "from": "http://ww19.hentaimam.io/",
        "status": 307
    },
    {
        "to": "http://ww19.hentaimam.io/",
        "from": "https://ww19.hentaimam.io/",
        "status": 307
    }
]
Ip
208.91.196.145
Contacted domains
[
    "hentaimam.io"
]
Contacted IP addresses
[
    "208.91.196.145",
    "185.150.189.124"
]
Asns
[
    "40034",
    "23470"
]
Countries
[
    "VG",
    "US"
]
Document hash
8f2bfe0930e83fac5390c0423d979f5ddf50a09d9646524f57809e68b067219f
Cookies
[
    "sid"
]
Domain age days
0

Differs from the registration date in WHOIS (2026-03-11), which gives 227 days on the scan date 2026-10-25. The two sources disagree; both values are kept as recorded.

Apex age days
1938

Differs from the registration date in WHOIS (2026-03-11), which gives 227 days on the scan date 2026-10-25. The two sources disagree; both values are kept as recorded.

Requests
2
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 47,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "nginx/1.28.0",
    "content-type": "text/html",
    "via": "1.1 google"
}
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
01a1731f-d4f3-778f-a663-a68ee2be0f64
score
null
malicious
null
result_at
null
enriched_at
2026-10-26T09:18:00Z
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":"2026-10-26 10:18:00"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

3 community references

Open report

Cloudflare Radar

provider verdict: clean

Open report
Cloudflare RadarOriginal source recordObserved: 9 fields

Observed: · Retrieved:

Report ID

177f4804-96e9-4b16-b976-b08e948e1b96

Final URL

http://ww19.hentaimam.io/

HTTP response

307

Navigation history

  • URL
    https://ww19.hentaimam.io/
    Status
    0
  • URL
    https://hentaimam.io/
    Status
    302
  • URL
    http://ww19.hentaimam.io/
    Status
    307

DOM structure hash

a7fe83ec64bb23eb28090598db3d166ed98e52e39d1afbbfd74c579553f93e4e

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    hentaimam.io
    Type
    A
    Value
    212.92.105.23
  • Name
    ww19.hentaimam.io
    Type
    CNAME
    Value
    9145.searchmagnified.com
  • Name
    ww19.hentaimam.io
    Type
    CNAME
    Value
    9145.searchmagnified.com

DNSSEC valid

No

Registration record

Registrar
CommuniGal Communication Ltd.
Registered
Updated
Expires
Nameservers
  • ns1.hostresolver.com
  • ns2.hostresolver.com
Original source fields · JSON
Uuid
177f4804-96e9-4b16-b976-b08e948e1b96
Final url
http://ww19.hentaimam.io/
Status
307
History
[
    {
        "url": "https://ww19.hentaimam.io/",
        "status": 0
    },
    {
        "url": "https://hentaimam.io/",
        "status": 302
    },
    {
        "url": "http://ww19.hentaimam.io/",
        "status": 307
    }
]
DOM structure hash
a7fe83ec64bb23eb28090598db3d166ed98e52e39d1afbbfd74c579553f93e4e
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "hentaimam.io",
        "type": "A",
        "value": "212.92.105.23"
    },
    {
        "name": "ww19.hentaimam.io",
        "type": "CNAME",
        "value": "9145.searchmagnified.com"
    },
    {
        "name": "ww19.hentaimam.io",
        "type": "CNAME",
        "value": "9145.searchmagnified.com"
    }
]
Dnssec valid
false
Registration record
{
    "registrar": "CommuniGal Communication Ltd.",
    "created": "2026-03-11T15:16:02Z",
    "updated": "2026-10-14T01:55:40Z",
    "expires": "2027-03-11T15:16:02Z",
    "nameservers": [
        "ns1.hostresolver.com",
        "ns2.hostresolver.com"
    ]
}

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

88 / 100 · heuristic score · 0 brand references · 0 classifications

Open report
Separate monitor score · 0 / 100 · 2026-10-25T13:30:48Z

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
0
analyzed_at
2026-10-25T13:30:48Z
source_timestamp
2026-10-25 14:30:48
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

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: 16 fields

Mail configuration

SPF lookups
0

CAA records

Domain
hentaimam.io

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
3
Archived days
7
Snapshots per day
0
Average page size, bytes
634

Crawler rules

Present
Yes

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
152
TLS
39
Waiting
72
Connection
152
Download
0
Response time, ms
415

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

DNS servers

Nameservers
  • IP address
    212.92.105.17
    Host
    ns2.hostresolver.com
  • IP address
    104.243.32.66
    Host
    ns1.hostresolver.com
DNS zone
hentaimam.io

Location

IP address
212.92.105.19
ASN
43350
Organization
NForce Entertainment B.V.
City
Roosendaal
Country
NL

TLS certificate

Issuer
Let's Encrypt / YR2
Subject
hentaimam.io

DNS records

A
  • 212.92.105.19
NS
  • ns1.hostresolver.com
  • ns2.hostresolver.com
SOA
Primary nameserver
ns1.hostresolver.com
Hostmaster
admin.hentaimam.io
Serial
2026102504
Refresh, seconds
86400
Retry, seconds
10800
Expiry, seconds
604800
Minimum TTL, seconds
60
TXT
  • dbg: src: ds, acme: false

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

IP lookup

IP address
212.92.105.19
IP version
4

Redirects

Redirect chain
  • https://hentaimam.io

Registration record

Registrar
CommuniGal Communication Ltd.
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • ns1.hostresolver.com
  • ns2.hostresolver.com
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "hentaimam.io"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-10-25T12:55:26Z",
    "first": "2021-12-05T04:25:22Z",
    "changes": 3,
    "days_archived": 7,
    "scans_per_day": 0,
    "avg_page_bytes": 634
}
Crawler rules
{
    "present": true
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 152,
        "tls": 39,
        "wait": 72,
        "connect": 152,
        "download": 0
    },
    "response_ms": 415
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "authorized": true,
    "forward_secrecy": true
}
Dns server
{
    "ns": [
        {
            "ip": "212.92.105.17",
            "host": "ns2.hostresolver.com"
        },
        {
            "ip": "104.243.32.66",
            "host": "ns1.hostresolver.com"
        }
    ],
    "zone": "hentaimam.io"
}
Location
{
    "ip": "212.92.105.19",
    "asn": "43350",
    "org": "NForce Entertainment B.V.",
    "city": "Roosendaal",
    "country": "NL"
}
Ssl
{
    "issuer": "Let's Encrypt / YR2",
    "subject": "hentaimam.io"
}
DNS records
{
    "A": [
        "212.92.105.19"
    ],
    "NS": [
        "ns1.hostresolver.com",
        "ns2.hostresolver.com"
    ],
    "SOA": "{\"nsname\": \"ns1.hostresolver.com\", \"hostmaster\": \"admin.hentaimam.io\", \"serial\": 2026102504, \"refresh\": 86400, \"retry\": 10800, \"expire\": 604800, \"minttl\": 60}",
    "TXT": [
        "dbg: src: ds, acme: false"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Get ip
{
    "ip": "212.92.105.19",
    "family": 4
}
Redirects
{
    "chain": [
        "https://hentaimam.io"
    ]
}
Registration record
{
    "registrar": "CommuniGal Communication Ltd.",
    "created": "2026-03-11T15:16:02Z",
    "updated": "2026-10-14T01:55:40Z",
    "expires": "2027-03-11T15:16:02Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "ns1.hostresolver.com",
        "ns2.hostresolver.com"
    ]
}

Questions about hentaimam.io

Is hentaimam.io legit?

PhishDestroy rates hentaimam.io as critical risk (91/100) from the recorded evidence; it was first recorded on 2026-10-25. Stored VirusTotal result: 9/92 engines flagged. malicious: 9. suspicious: 0. Analysis time (as stored): 2026-10-24T01:48:08Z. Retrieved (as stored): 2026-10-25T13:27:24Z. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is hentaimam.io safe to connect a wallet?

This report does not record which wallet requests hentaimam.io 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 hentaimam.io?

It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority; a report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 5 captures

Stored capture 1 / 5
SourceStored capture
Recorded
StateStored capture
Position1 / 5
Open capture Wayback Download
All capture links and hashes (5)
hentaimam.io: caution — 9/92 VirusTotal engines. PhishDestroy risk score 91/100 (critical).
Social preview card hentaimam.io: caution — 9/92 VirusTotal engines. PhishDestroy risk score 91/100 (critical). v 01efba41ca40

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 47 report ↗
IP Reputation Netherlands212.92.105.27 abuse score 0/100 0 reports checked Oct 25, 2026
OTX tags 2026-10all-domainsblocklistcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar CommuniGal Communication
Abuse contactabuse@nforce.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for hentaimam.io →
Hosting abuse contact abuse@nforce.com NForce Entertainment B.V. · AS43350
RegistrationCreated Mar 11, 2026 (236d) — Expires Mar 11, 2027
Registrant countryCyprus VirusTotal WHOIS
Registrant3495bcf1839c6374fb6ff66ef97c0518s@ VirusTotal WHOIS
WHOIS statusclientTransferProhibited
HTTP Status302 Found (Temporary)
Technical detailsProvenance & timestamps
First DetectedOct 25, 2026
DOM Analysisanalyzed Oct 25, 2026score 88/100
Submitted URLhttp://hentaimam.io/
Favicon Hash
Case ID
TLS Certificate
Issued by Let's Encrypt / YR2 · stored validity ends in 71 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Netherlands212.92.105.27
Network ASN
AS43350
Organization
NForce Entertainment B.V.
Observed location
NetherlandsRoosendaal, NL
Server header
nginx/1.28.0

Nameservers 2

  • ns1.hostresolver.com
  • ns2.hostresolver.com

SOA

  • nsname: ns1.hostresolver.com
  • hostmaster: admin.hentaimam.io
  • serial: 2026102504
  • refresh: 86400
  • retry: 10800
  • expire: 604800
  • minttl: 60

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR2
Valid from
2026-10-15 08:29:34
Valid until
2027-01-13 08:29:33
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint8b88968427245a6d41f78ed666a6f5057993cd637eee8cab7dd3532ed94a8b51
Certificate names · 2 SANs
  • *.hentaimam.io
  • hentaimam.io

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

viewdns.info · 212.92.105.27rapiddns.io

Latest Classified Outcome 2026-11-02 11:06:32 UTC

The site was redirecting visitors elsewhere at the latest check.

Technical details
Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-11-02 11:06:32 UTC
RDAP registration
Observed timeline last reachable: 2026-11-02 11:06:32 UTC last content: 2026-10-26 12:02:23 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Recorded subdomains6

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

  • comww38.hentaimam.ioDomain record
  • random.hentaimam.ioDomain record
  • ww16.hentaimam.ioDomain record
  • ww38.hentaimam.ioDomain record
  • ww6.hentaimam.ioDomain record
  • www.hentaimam.ioDomain record
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

9 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
Bkav
G-Data
Lionic
Sophos
Fortinet
Kaspersky
BitDefender
alphaMountain.ai
Forcepoint ThreatSeeker
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of hentaimam.io · checked Oct 25, 2026

100
Good
Performance
FCP
1.38 s
First Contentful Paint
LCP
1.38 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
1.69 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://hentaimam.io/
Loading...
Response
HTTP 200
HTML body
473 B
Compressed
377 B
Links
0 internal · 0 external
Detected technologies
nginx
Selected response headers
Cache-Control: max-age=0, private, must-revalidate
Content-Type: text/html; charset=utf-8
Server: nginx
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 7
accept-ch
Sec-CH-UA, Sec-CH-UA-Platform, Sec-CH-UA-Platform-Version, Sec-CH-UA-Mobile
Cache-Control
max-age=0, private, must-revalidate
Connection
close
Content-Length
473
Content-Type
text/html; charset=utf-8
Date
Sun, 25 Oct 2026 12:55:09 GMT
Server
nginx

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

Archived
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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

Captured network requests

Network requests: 2 SHA-256 hashes: 2 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-29 01:57 UTC.

Open this scan on URLScan 01a1731f-d4f3-778f-a663-a68ee2be0f64 ↗

Stored observation history9

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

  1. Availability monitor · Recorded state

    redirected

    http_redirect

  2. Availability monitor · Recorded state

    redirected

    http_redirect

  3. Availability monitor · Recorded state

    redirected

    http_redirect

  4. Availability monitor · Recorded state

    redirected

    http_redirect

  5. Availability monitor · Recorded state

    redirected

    http_redirect

Earlier observations 4
  1. Availability monitor · Recorded state

    live_content→redirected

    http_redirect

  2. Availability monitor · Recorded state

    redirected→live_content

    content_served

  3. Availability monitor · Recorded state

    redirected

    http_redirect

  4. Domain monitor · First collection record

    Reachable

All retained availability observations39

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

  1. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 12:06:32.000000
    Evidence SHA-256
    064d42c404f7190399b4f125b99169636c4f7d9b0f9542b5041e54e42748a0f6
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-11-02 12:06:32
    Evidence reason
    redirect
  2. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 12:06:32.000000
    Evidence SHA-256
    064d42c404f7190399b4f125b99169636c4f7d9b0f9542b5041e54e42748a0f6
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-11-02 12:06:32
    Evidence reason
    redirect
  3. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 00:09:41.000000
    Evidence SHA-256
    840cd13e4a6629cf637950a7ca0f32db48e0a4b02691cbec66a460526da5ebe1
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-11-02 00:09:41
    Evidence reason
    redirect
  4. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 00:09:41.000000
    Evidence SHA-256
    840cd13e4a6629cf637950a7ca0f32db48e0a4b02691cbec66a460526da5ebe1
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-11-02 00:09:41
    Evidence reason
    redirect
  5. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 23:20:11.055498
    Evidence SHA-256
    7c023747294077bd6e2ec2b080dc137e75a3ed6faf38dbdfcaa23e6958793fa3
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-01 23:20:11.055498
    Evidence reason
  6. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 12:10:34.000000
    Evidence SHA-256
    9000c03449c4df2d82c37b34bb02ea743cc7cd974191bf12acbdb0c34a67e91d
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-11-01 12:10:34
    Evidence reason
    redirect
  7. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 12:10:34.000000
    Evidence SHA-256
    9000c03449c4df2d82c37b34bb02ea743cc7cd974191bf12acbdb0c34a67e91d
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-11-01 12:10:34
    Evidence reason
    redirect
  8. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 03:54:08.000000
    Evidence SHA-256
    828a5553476bcf050573e5dbb033e1bfe6a6ad097f3758615812801ac2a669fb
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-11-01 03:54:08
    Evidence reason
    redirect
  9. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 03:54:08.000000
    Evidence SHA-256
    828a5553476bcf050573e5dbb033e1bfe6a6ad097f3758615812801ac2a669fb
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-11-01 03:54:08
    Evidence reason
    redirect
  10. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 00:09:04.000000
    Evidence SHA-256
    e998f353add4b925d80961a6887244828ab220f42376b6ef3605da3dd140916a
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-11-01 00:09:04
    Evidence reason
    redirect
  11. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 00:09:04.000000
    Evidence SHA-256
    e998f353add4b925d80961a6887244828ab220f42376b6ef3605da3dd140916a
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-11-01 00:09:04
    Evidence reason
    redirect
  12. 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-31 23:20:09.600237
    Evidence SHA-256
    fdac094cb4b92350d9f20b2c0fc69fdcaa33e7da7eb2d1063ea3f2bc257f29ef
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 23:20:09.600237
    Evidence reason
  13. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:09:42.000000
    Evidence SHA-256
    2c3bcd479344cd0fbefec91fc853f1c23492c380c5b69d1de4fe7c40e71087ea
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-31 12:09:42
    Evidence reason
    redirect
  14. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:09:42.000000
    Evidence SHA-256
    2c3bcd479344cd0fbefec91fc853f1c23492c380c5b69d1de4fe7c40e71087ea
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-31 12:09:42
    Evidence reason
    redirect
  15. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 03:30:49.000000
    Evidence SHA-256
    e97bc28f1f42ed11fd1653305aca437a50554e47f9545801d298d22209cc1783
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-31 03:30:49
    Evidence reason
    redirect
  16. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 03:30:49.000000
    Evidence SHA-256
    e97bc28f1f42ed11fd1653305aca437a50554e47f9545801d298d22209cc1783
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-31 03:30:49
    Evidence reason
    redirect
  17. 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 22:35:15.875079
    Evidence SHA-256
    97b1f1aad91757df55a07aa8eadffa1ea48bf460a07a53a1e786c935a601fca5
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 22:35:15.875079
    Evidence reason
  18. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:07:10.000000
    Evidence SHA-256
    6cbcd4f8bf25c63989e452fc7514491fc4fa628a4221861c88baf25b4b3e0ff5
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-30 12:07:10
    Evidence reason
    redirect
  19. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:07:10.000000
    Evidence SHA-256
    6cbcd4f8bf25c63989e452fc7514491fc4fa628a4221861c88baf25b4b3e0ff5
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-30 12:07:10
    Evidence reason
    redirect
  20. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:07:21.000000
    Evidence SHA-256
    a19e41c90b5139d67b09ffab0dd50198ad57d2fe1c70907d2bc071773c1d6479
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-30 00:07:21
    Evidence reason
    redirect
  21. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:07:21.000000
    Evidence SHA-256
    a19e41c90b5139d67b09ffab0dd50198ad57d2fe1c70907d2bc071773c1d6479
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-30 00:07:21
    Evidence reason
    redirect
  22. 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-29 17:14:29.775349
    Evidence SHA-256
    db74fcc6d756cb36943e7c7745a6a8737aaa6959c4a9679405e4f75391d96929
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-29 17:14:29.775349
    Evidence reason
  23. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 12:07:40.000000
    Evidence SHA-256
    94a330a1b189fc1ab49aa68c6d7bba11cc006c93235c99a57ba99e01f4f61f53
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-29 12:07:40
    Evidence reason
    redirect
  24. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 12:07:40.000000
    Evidence SHA-256
    94a330a1b189fc1ab49aa68c6d7bba11cc006c93235c99a57ba99e01f4f61f53
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-29 12:07:40
    Evidence reason
    redirect
  25. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 03:36:22.000000
    Evidence SHA-256
    939468acaa39c6b0e7a69433bf97aa12c43077afcdafe9ee6100c163357d0cd2
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-29 03:36:22
    Evidence reason
    redirect
  26. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 03:36:22.000000
    Evidence SHA-256
    939468acaa39c6b0e7a69433bf97aa12c43077afcdafe9ee6100c163357d0cd2
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-29 03:36:22
    Evidence reason
    redirect
  27. 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-28 17:03:14.895165
    Evidence SHA-256
    73d1f345e73e3fe3ec20cf30f9fc86221ba9885e7af8cdcc18189657c73b0d4e
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-28 17:03:14.895165
    Evidence reason
  28. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 12:02:19.000000
    Evidence SHA-256
    22dae91fccbf1181bc4856ff39594be8f2dfb7ac9556686ed74eca2e0835bd89
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-28 12:02:19
    Evidence reason
    redirect
  29. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 12:02:19.000000
    Evidence SHA-256
    22dae91fccbf1181bc4856ff39594be8f2dfb7ac9556686ed74eca2e0835bd89
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-28 12:02:19
    Evidence reason
    redirect
  30. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 00:02:51.000000
    Evidence SHA-256
    dd11ae30f593b7e32ca09abe69fc6a4406f552c9932d180b32c5a9f7e4f32776
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-28 00:02:51
    Evidence reason
    redirect
  31. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 00:02:51.000000
    Evidence SHA-256
    dd11ae30f593b7e32ca09abe69fc6a4406f552c9932d180b32c5a9f7e4f32776
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-28 00:02:51
    Evidence reason
    redirect
  32. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:02:54.000000
    Evidence SHA-256
    96c0a969fc39ce6dc717119e5d073795a39ea082744bb38a719063fd1d2de445
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-27 12:02:54
    Evidence reason
    redirect
  33. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:02:54.000000
    Evidence SHA-256
    96c0a969fc39ce6dc717119e5d073795a39ea082744bb38a719063fd1d2de445
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-27 12:02:54
    Evidence reason
    redirect
  34. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 13:02:23.000000
    Evidence SHA-256
    1d851a616b7119f45249f090f30357aa27c1bbc0c2986ca45cd27b5b0791d405
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 13:02:23
    Evidence reason
    alive_content
  35. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 13:02:23.000000
    Evidence SHA-256
    1d851a616b7119f45249f090f30357aa27c1bbc0c2986ca45cd27b5b0791d405
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 13:02:23
    Evidence reason
    alive_content
  36. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 01:19:29.000000
    Evidence SHA-256
    21068534addf99e8e82d653a4ebfd8203646a6eb9c2acde419a2accd5eee22f7
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-26 01:19:29
    Evidence reason
    redirect
  37. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 01:19:29.000000
    Evidence SHA-256
    21068534addf99e8e82d653a4ebfd8203646a6eb9c2acde419a2accd5eee22f7
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-26 01:19:29
    Evidence reason
    redirect
  38. 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-10-25 13:54:40.000000
    Evidence SHA-256
    dc8323a03ff0c730e6959c86a04842efbe05b653b44278a1da9c8e542516e48a
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 13:54:40
    Evidence reason
  39. 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-10-25 13:54:40.000000
    Evidence SHA-256
    dc8323a03ff0c730e6959c86a04842efbe05b653b44278a1da9c8e542516e48a
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 13:54:40
    Evidence reason

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Notifications · recorded
  4. 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
    hentaimam.io 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 Recorded: 7 of 7
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 47
  • 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: 9/92
  • OTX Community References
    Community publication references on AlienVault OTX: 3. References are not vendor verdicts and are excluded from the evidence score.
  • 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.
Notification RecordsSent Report Recorded Recorded: 1 of 1
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: CommuniGal Communication Ltd.. Abuse contacts: 1.
    • abuse@nforce.com
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

5 entries
  1. AlienVault OTX

    3 community references

    View source
  2. Abuse report sent

    PD-20261025-225803 · Receipt 83039

    abuse@nforce.com
  3. Added to PhishDestroy

    hentaimam.io

    View source
  4. URLScan

    Page captured

    View source
  5. VirusTotal

    9/92 engine detections

    View source
How we investigate & report

Public scans, evidence and abuse channels

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

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

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

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

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

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

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

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

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

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

Download all records as JSON

Check for cloaking

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

hentaimam.io

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 9 det. ChainPatrol URLQuery 2 det. SSL Labs Stored certificate dates valid CF Radar Open report OTX 3 refs WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261025-225803 Recipient: abuse@nforce.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 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 hentaimam.io)
  • 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.

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/hentaimam.io"
  title="PhishDestroy threat report for hentaimam.io"
  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>