Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 12/92 engines flagged. malicious: 11. suspicious: 1. Analysis time (as stored): 2026-11-07T14:40:55Z. Retrieved (as stored): 2026-11-08T02:29:02Z. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
loispay.io favicon

loispay.io

In short

On 2026-11-06, loispay.io displayed a LoisPay-branded homepage. The page presents a headline about transferring money with a QR code in a second, alongside an illustration of a phone, card, and QR code. Navigation links cover Personal, Business, Enterprise, Company, and Developer sections, with Help, language selection, Log In, and Sign Up controls in the header.

“LoisPay - Money Transfer with QR Code”

Review the evidence
Registrar
United StatesGoDaddy
Resolved IP
Germany31.97.217.217Hostinger International Limited
Registered
Oct 4, 2025
First observed
Nov 7, 2026
PhishDestroy assessment Critical
86/100
Evidence score
First observed Nov 7, 2026 13:22 UTC · PhishDestroy
Risk signals
VirusTotal detections: 12/92
VirusTotal
12 / 92
engine detections ·
OTX
2
community references
URLScan
Malicious
engine verdict · score 66
Page captures
3
open gallery
Domain age
399 days
registered 2025-10-04 according to WHOIS
OTX: 2 refs Nov 7, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded loispay.io on 2026-11-07. Stored VirusTotal result: 12/92 engines flagged. malicious: 11. suspicious: 1. Analysis time (as stored): 2026-11-07T14:40:55Z. Retrieved (as stored): 2026-11-08T02:29:02Z. Risk: critical (86/100). Registrar: GoDaddy. Hosting: Hostinger International Limited. Do not enter credentials or connect a wallet.

Critical
VirusTotal
12 / 92
Hosting
Germany31.97.217.217Hostinger International Limited
Registrar
United StatesGoDaddy
Registered
Oct 4, 2025
OTX
2 community refs
Page captures
3
Page captures Source results Registration record

Capture recorded with this analysis · URLScan · 2026-11-06T20:52:09Z
SHA-256: de0bcac6ff2de22b0f874149e9b71886725d0959eede6de9f2668c28bba9f43e

PhishDestroy analysis, reviewed version

On 2026-11-06, loispay.io displayed a LoisPay-branded homepage. The page presents a headline about transferring money with a QR code in a second, alongside an illustration of a phone, card, and QR code. Navigation links cover Personal, Business, Enterprise, Company, and Developer sections, with Help, language selection, Log In, and Sign Up controls in the header.

Below the hero, the page lists key features including QRCode Money Transfer and Make Payment, with a section titled Our Key Features describing seamless QR code transfers. Two buttons offer downloads for Google Play and the Apple Store. A cookie notice at the bottom explains tracking technologies and provides Allow and Decline options with a Privacy & Policy link.

Source evidenceVirusTotal 12 / 92 · OTX 2 references 8 sources

VirusTotal

12 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 12 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
48
Malicious
11
Suspicious
1
Undetected
32

Vendor labels

CRDF
malicious
DNS8
suspicious
VIPRE
malware
Lionic
phishing
Sophos
phishing
CyRadar
phishing
Fortinet
phishing
SOCRadar
phishing
Kaspersky
phishing
Seclookup
malicious
Gridinsoft
phishing
alphaMountain.ai
phishing

Reputation score

0

Popularity ranks

Cisco Umbrella
313568
Cloudflare Radar
200000

Created

Updated

First seen

DNS records

  • TTL, seconds
    3600
    Type
    SOA
    Responsible mailbox
    dns.jomax.net
    Value
    ns63.domaincontrol.com
  • TTL, seconds
    3600
    Type
    NS
    Value
    ns64.domaincontrol.com
  • TTL, seconds
    3600
    Type
    TXT
    Value
    v=spf1 +mx +a +ip4:31.97.217.217 ~all
  • TTL, seconds
    3600
    Type
    TXT
    Value
    google-site-verification=G7umiF3w5GtxvUJQj9Fh2TNFKFOGsyMNGKJL_5bhYZ8
  • TTL, seconds
    600
    Type
    A
    Value
    31.97.217.217
  • TTL, seconds
    3600
    Type
    NS
    Value
    ns63.domaincontrol.com

DNS records observed

JARM fingerprint

15d3fd16d29d29d00042d43d0000001ae0802418786940cae38f1d9eed5b9b

Certificate

Subject alternative names
  • loispay.io
  • mail.loispay.io
  • www.loispay.io
Issuer
Let's Encrypt / YR2
Serial
5c6a1629b0758479f1c7abd73bb98248fff
SHA-256
6267590fda34f1369406e5d33b2fee1bbd69cc99e0f4d8d2a94012a9a26fbde1
Subject
loispay.io
Valid until
Valid from

Registry data (RDAP)

Status
  • client delete prohibited
  • client renew prohibited
  • client transfer prohibited
  • client update prohibited
  • auto renew period
Registry events
Expiration
Last changed
Registration
Last RDAP database update
Registrar
GoDaddy.com, LLC
Registrar IANA ID
146
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 48,
    "malicious": 11,
    "suspicious": 1,
    "undetected": 32
}
Vendor labels
{
    "CRDF": "malicious",
    "DNS8": "suspicious",
    "VIPRE": "malware",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "phishing",
    "alphaMountain.ai": "phishing"
}
Reputation
0
Popularity
{
    "Cisco Umbrella": 313568,
    "Cloudflare Radar": 200000
}
Created
2025-10-04T00:00:00Z
Updated
2025-10-04T00:00:00Z
First seen
2025-10-06T07:02:32Z
DNS records
[
    {
        "ttl": 3600,
        "type": "SOA",
        "rname": "dns.jomax.net",
        "value": "ns63.domaincontrol.com"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns64.domaincontrol.com"
    },
    {
        "ttl": 3600,
        "type": "TXT",
        "value": "v=spf1 +mx +a +ip4:31.97.217.217 ~all"
    },
    {
        "ttl": 3600,
        "type": "TXT",
        "value": "google-site-verification=G7umiF3w5GtxvUJQj9Fh2TNFKFOGsyMNGKJL_5bhYZ8"
    },
    {
        "ttl": 600,
        "type": "A",
        "value": "31.97.217.217"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns63.domaincontrol.com"
    }
]
Dns at
2026-11-07T14:47:47Z
Jarm
15d3fd16d29d29d00042d43d0000001ae0802418786940cae38f1d9eed5b9b
Certificate
{
    "san": [
        "loispay.io",
        "mail.loispay.io",
        "www.loispay.io"
    ],
    "issuer": "Let's Encrypt / YR2",
    "serial": "5c6a1629b0758479f1c7abd73bb98248fff",
    "sha256": "6267590fda34f1369406e5d33b2fee1bbd69cc99e0f4d8d2a94012a9a26fbde1",
    "subject": "loispay.io",
    "valid_to": "2027-01-18T06:04:37Z",
    "valid_from": "2026-10-20T06:04:38Z"
}
Registry data
{
    "status": [
        "client delete prohibited",
        "client renew prohibited",
        "client transfer prohibited",
        "client update prohibited",
        "auto renew period"
    ],
    "events": {
        "expiration": "2027-10-04T12:24:53Z",
        "last changed": "2026-10-05T20:41:10Z",
        "registration": "2025-10-04T12:24:53Z",
        "last update of RDAP database": "2026-11-04T19:59:55Z"
    },
    "registrar": "GoDaddy.com, LLC",
    "registrar_iana_id": "146"
}
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
12
denominator
92
malicious
null
suspicious
null
vendors
["alphaMountain.ai","CRDF","CyRadar","DNS8","Fortinet","Gridinsoft","Kaspersky","Lionic","Seclookup","SOCRadar","Sophos","VIPRE"]
observed_at
2026-11-07 14:40:55
checked_at
2026-11-08 03:29:02
fetched_at
2026-11-08 02:29:03
time_basis
as stored; legacy timezone not established

Cloudflare Radar

Malicious

Open report
Cloudflare RadarOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Report ID

5bb85a56-0dc2-4e46-beaa-1e9aa2651eb8

Final URL

https://loispay.io/

HTTP response

200

Navigation history

  • URL
    https://loispay.io/
    Status
    200

DOM structure hash

16f8e3db31e244469353566add5827f22b4e460eaa8fc56ce4f0f4416ef34c73

Document hash

1571bd6a7ef6620e962699b9d15dcc8d5981276be0cd411bd3a2c25ee4ae4629

Domain risk categories

  • Malware
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
200000

DNS records

  • Name
    loispay.io
    Type
    A
    Value
    31.97.217.217

DNSSEC valid

No

IP address

127.0.1.1

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

Verdict

Tags
  • malware
Malicious
Yes
Categories
  • malware

Registration record

Registrar
GoDaddy.com, LLC
Registered
Updated
Expires
Nameservers
  • ns63.domaincontrol.com
  • ns64.domaincontrol.com
Original source fields · JSON
Uuid
5bb85a56-0dc2-4e46-beaa-1e9aa2651eb8
Final url
https://loispay.io/
Status
200
History
[
    {
        "url": "https://loispay.io/",
        "status": 200
    }
]
DOM structure hash
16f8e3db31e244469353566add5827f22b4e460eaa8fc56ce4f0f4416ef34c73
Document hash
1571bd6a7ef6620e962699b9d15dcc8d5981276be0cd411bd3a2c25ee4ae4629
Domain risks
[
    "Malware",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": "200000"
}
DNS records
[
    {
        "name": "loispay.io",
        "type": "A",
        "value": "31.97.217.217"
    }
]
Dnssec valid
false
Ip
127.0.1.1

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

Verdict
{
    "tags": [
        "malware"
    ],
    "malicious": true,
    "categories": [
        "malware"
    ]
}
Registration record
{
    "registrar": "GoDaddy.com, LLC",
    "created": "2025-10-04T12:24:53Z",
    "updated": "2026-10-05T20:41:10Z",
    "expires": "2027-10-04T12:24:53Z",
    "nameservers": [
        "ns63.domaincontrol.com",
        "ns64.domaincontrol.com"
    ]
}

URLScan

Malicious · engine verdict · score 66

SHA-256 848e2d14c6ce7cb0546df9426dad572ac9b2f95883addc2b983bd8b6579c3177

Open report
URLScanOriginal source recordObserved: 21 fields

Observed: · Retrieved:

Report ID

01a1b2a1-6fd6-71d8-9c43-d25c6589710c

Final URL

http://loispay.io/

HTTP response

200

Redirects

  • To
    https://loispay.io/
    From
    http://loispay.io/
    Status
    307
  • To
    http://loispay.io/
    From
    https://loispay.io/
    Status
    307

IP address

31.97.217.217

Reverse DNS (PTR)

srv1046296.hstgr.cloud

Contacted domains

  • fonts.gstatic.com
  • www.gstatic.com
  • www.google.com
  • fonts.googleapis.com

Contacted IP addresses

  • 142.251.150.120
  • 142.250.217.131
  • 142.251.156.119
  • 142.251.16.95
  • 31.97.217.217

Autonomous systems (ASN)

  • 15169
  • 47583

Server countries

  • US
  • DE

Linked domains

  • play.google.com
  • www.apple.com

Document hash

b33d83f5914ae217467b34d8513513bece7c9a8ce4eeb295e02acc86e10bddb6

Script hashes

  • c7c623258f45ec43ebd096c9966e749bdeb41e27f907a10b26050f7b404a56ed
  • f53abeff0e0481ee16c473c487b669e3b949cf2b0cd6f69f5442567421bf70e2
  • 7964513c5133f6171578ec511c6bbe84bca86f90074e1c04ec16e991fd6521fc
  • ad3e06c9eb14b7829803ecfb340c1c33a6cd76ec98496f0d335ad6e0b9b45d60
  • b708ccca70932606badb02497bea00fabf099a2ad08630549d7bbb49e7eefcf8
  • 5a6b0628f9ab5f37e00198d7ca2ca2fee0ef17308700954ea95b0be21006e219
  • 1471bce6d9dc4db571a2a1695389cf28b361e235adf54c2fadc80f7eb0bc1d4d
  • 222227004ab2ee5c575a18e35c95739331439dff372d6de9784ee3d843b3121a
  • eb3bac9a6140c0f4caccf7ef0517fe5fd0815891f1f815990d20e091372c711c
  • 93d3eb069adde96f4d108dc51a55d57dfb5c70385cd3dc2417d1d6c0a3bc8ef3

JavaScript globals

  • $
  • jQuery
  • uidEvent
  • bootstrap
  • Swiper
  • SmoothScroll
  • Odometer
  • ___grecaptcha_cfg
  • grecaptcha
  • __recaptcha_api
  • __google_recaptcha_client
  • btnLoadingRefresh
  • setAdSelectInputValue
  • placePhoneCode
  • switcherAjax
  • copyToClipBoard
  • formAjaxRequest
  • itemSearch
  • executeItemSearch
  • makeSearchItemXmlRequest
  • itemSearchResult
  • getAllCountries
  • throwMessage
  • notification
  • validationSession
  • getSessionValue
  • openModalWhenError
  • countrySelect
  • stateSelect
  • property
  • widget
  • approval_status
  • c_user_agent
  • c_ip_address
  • c_browser
  • c_platform
  • s_ipAddress
  • s_browser
  • s_platform
  • s_agent

Cookies

  • XSRF-TOKEN
  • loispay_session

Domain age, days

396

Registered domain age, days

396

Cisco Umbrella rank

317726

Page requests

44

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-2aab354
Score
66
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP headers

Server
Apache
Content-type
text/html; charset=UTF-8
Original source fields · JSON
Uuid
01a1b2a1-6fd6-71d8-9c43-d25c6589710c
Final url
http://loispay.io/
Status
200
Redirects
[
    {
        "to": "https://loispay.io/",
        "from": "http://loispay.io/",
        "status": 307
    },
    {
        "to": "http://loispay.io/",
        "from": "https://loispay.io/",
        "status": 307
    }
]
Ip
31.97.217.217
Ptr
srv1046296.hstgr.cloud
Contacted domains
[
    "fonts.gstatic.com",
    "www.gstatic.com",
    "www.google.com",
    "fonts.googleapis.com"
]
Contacted IP addresses
[
    "142.251.150.120",
    "142.250.217.131",
    "142.251.156.119",
    "142.251.16.95",
    "31.97.217.217"
]
Asns
[
    "15169",
    "47583"
]
Countries
[
    "US",
    "DE"
]
Linked domains
[
    "play.google.com",
    "www.apple.com"
]
Document hash
b33d83f5914ae217467b34d8513513bece7c9a8ce4eeb295e02acc86e10bddb6
Script hashes
[
    "c7c623258f45ec43ebd096c9966e749bdeb41e27f907a10b26050f7b404a56ed",
    "f53abeff0e0481ee16c473c487b669e3b949cf2b0cd6f69f5442567421bf70e2",
    "7964513c5133f6171578ec511c6bbe84bca86f90074e1c04ec16e991fd6521fc",
    "ad3e06c9eb14b7829803ecfb340c1c33a6cd76ec98496f0d335ad6e0b9b45d60",
    "b708ccca70932606badb02497bea00fabf099a2ad08630549d7bbb49e7eefcf8",
    "5a6b0628f9ab5f37e00198d7ca2ca2fee0ef17308700954ea95b0be21006e219",
    "1471bce6d9dc4db571a2a1695389cf28b361e235adf54c2fadc80f7eb0bc1d4d",
    "222227004ab2ee5c575a18e35c95739331439dff372d6de9784ee3d843b3121a",
    "eb3bac9a6140c0f4caccf7ef0517fe5fd0815891f1f815990d20e091372c711c",
    "93d3eb069adde96f4d108dc51a55d57dfb5c70385cd3dc2417d1d6c0a3bc8ef3"
]
Globals
[
    "$",
    "jQuery",
    "uidEvent",
    "bootstrap",
    "Swiper",
    "SmoothScroll",
    "Odometer",
    "___grecaptcha_cfg",
    "grecaptcha",
    "__recaptcha_api",
    "__google_recaptcha_client",
    "btnLoadingRefresh",
    "setAdSelectInputValue",
    "placePhoneCode",
    "switcherAjax",
    "copyToClipBoard",
    "formAjaxRequest",
    "itemSearch",
    "executeItemSearch",
    "makeSearchItemXmlRequest",
    "itemSearchResult",
    "getAllCountries",
    "throwMessage",
    "notification",
    "validationSession",
    "getSessionValue",
    "openModalWhenError",
    "countrySelect",
    "stateSelect",
    "property",
    "widget",
    "approval_status",
    "c_user_agent",
    "c_ip_address",
    "c_browser",
    "c_platform",
    "s_ipAddress",
    "s_browser",
    "s_platform",
    "s_agent"
]
Cookies
[
    "XSRF-TOKEN",
    "loispay_session"
]
Domain age days
396
Apex age days
396
Umbrella rank
317726
Requests
44
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-2aab354"
        ],
        "score": 66,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "Apache",
    "content-type": "text/html; charset=UTF-8"
}
Separate monitor record · 2026-11-08 04:31 UTC

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

record_source
domain_monitor.urlscan
uuid
01a1b2a1-6fd6-71d8-9c43-d25c6589710c
score
0
malicious
false
result_at
2026-11-08T04:31:11Z
enriched_at
null
source_timestamps
{"urlscan_result_at":"2026-11-08 05:31:11","urlscan_enriched_at":null}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

2 community references

Open report

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

10 / 100 · heuristic score · 2 brand references · 0 classifications

Open report
Separate monitor score · 10 / 100 · 2026-11-08T02:49:53Z

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-08T02:49:53Z
source_timestamp
2026-11-08 03:49:53
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
loispay.io: LoisPay QR Code Money Transfer and Payment Platform
ai_description
PhishDestroy records loispay.io as a page presenting LoisPay's QR code money transfer and payment features, with app download links and account sign-up options.
ai_summary
On 2026-11-06, loispay.io displayed a LoisPay-branded homepage. The page presents a headline about transferring money with a QR code in a second, alongside an illustration of a phone, card, and QR code. Navigation links cover Personal, Business, Enterprise, Company, and Developer sections, with Help, language selection, Log In, and Sign Up controls in the header. Below the hero, the page lists key features including QRCode Money Transfer and Make Payment, with a section titled Our Key Features describing seamless QR code transfers. Two buttons offer downloads for Google Play and the Apple Store. A cookie notice at the bottom explains tracking technologies and provides Allow and Decline options with a Privacy & Policy link.
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-11-07 14:32:53
revision
bd9ac4a15c4052654686524212f98222807eaabf03a2e05aa3ff424377774440
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: 12 fields

Mail configuration

SPF record
v=spf1 +mx +a +ip4:31.97.217.217 ~all
DKIM
  • default
DMARC
Yes
DKIM key size, bits
2048
SPF lookups
2

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Ports

Open ports
  • 22
  • 25
  • 53
  • 80
  • 110
  • 143
  • 443
  • 587
  • 993
  • 995
  • 3306

DNS servers

Nameservers
  • IP address
    173.201.69.42
    Host
    ns64.domaincontrol.com
  • IP address
    97.74.101.42
    Host
    ns63.domaincontrol.com
DNS zone
loispay.io

Location

IP address
31.97.217.217
ASN
47583
Organization
Hostinger International Limited
City
Frankfurt am Main
Country
DE

TLS certificate

Issuer
Let's Encrypt / YR2
Subject
loispay.io

DNS records

A
  • 31.97.217.217
NS
  • ns64.domaincontrol.com
  • ns63.domaincontrol.com
SOA
Primary nameserver
ns63.domaincontrol.com
Hostmaster
dns.jomax.net
Serial
2025101301
Refresh, seconds
28800
Retry, seconds
7200
Expiry, seconds
604800
Minimum TTL, seconds
600
TXT
  • google-site-verification=G7umiF3w5GtxvUJQj9Fh2TNFKFOGsyMNGKJL_5bhYZ8
  • v=spf1 +mx +a +ip4:31.97.217.217 ~all

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

IP lookup

IP address
31.97.217.217
IP version
4

Popularity rank

Domain
loispay.io

Subdomains

Count
2
Subdomains
  • mail.loispay.io
  • www.loispay.io

Registration record

Registrar
GoDaddy.com, LLC
Registered
Updated
Expires
Status
  • clientDeleteProhibited https://icann.org/epp
  • clientRenewProhibited https://icann.org/epp
  • clientTransferProhibited https://icann.org/epp
  • clientUpdateProhibited https://icann.org/epp
  • autoRenewPeriod https://icann.org/epp
Nameservers
  • ns63.domaincontrol.com
  • ns64.domaincontrol.com
Original source fields · JSON
Mail configuration
{
    "spf": "v=spf1 +mx +a +ip4:31.97.217.217 ~all",
    "dkim": [
        "default"
    ],
    "dmarc": true,
    "dkim_bits": 2048,
    "spf_lookups": 2
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Ports
{
    "open": [
        22,
        25,
        53,
        80,
        110,
        143,
        443,
        587,
        993,
        995,
        3306
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "173.201.69.42",
            "host": "ns64.domaincontrol.com"
        },
        {
            "ip": "97.74.101.42",
            "host": "ns63.domaincontrol.com"
        }
    ],
    "zone": "loispay.io"
}
Location
{
    "ip": "31.97.217.217",
    "asn": "47583",
    "org": "Hostinger International Limited",
    "city": "Frankfurt am Main",
    "country": "DE"
}
Ssl
{
    "issuer": "Let's Encrypt / YR2",
    "subject": "loispay.io"
}
DNS records
{
    "A": [
        "31.97.217.217"
    ],
    "NS": [
        "ns64.domaincontrol.com",
        "ns63.domaincontrol.com"
    ],
    "SOA": "{\"nsname\": \"ns63.domaincontrol.com\", \"hostmaster\": \"dns.jomax.net\", \"serial\": 2025101301, \"refresh\": 28800, \"retry\": 7200, \"expire\": 604800, \"minttl\": 600}",
    "TXT": [
        "google-site-verification=G7umiF3w5GtxvUJQj9Fh2TNFKFOGsyMNGKJL_5bhYZ8",
        "v=spf1 +mx +a +ip4:31.97.217.217 ~all"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Get ip
{
    "ip": "31.97.217.217",
    "family": 4
}
Rank
{
    "domain": "loispay.io"
}
Subdomains
{
    "count": 2,
    "subdomains": [
        "mail.loispay.io",
        "www.loispay.io"
    ]
}
Registration record
{
    "registrar": "GoDaddy.com, LLC",
    "created": "2025-10-04T12:24:53Z",
    "updated": "2026-10-05T20:41:10Z",
    "expires": "2027-10-04T12:24:53Z",
    "status": [
        "clientDeleteProhibited https://icann.org/epp",
        "clientRenewProhibited https://icann.org/epp",
        "clientTransferProhibited https://icann.org/epp",
        "clientUpdateProhibited https://icann.org/epp",
        "autoRenewPeriod https://icann.org/epp"
    ],
    "nameservers": [
        "ns63.domaincontrol.com",
        "ns64.domaincontrol.com"
    ]
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Malware Security threats Malware
View full Cloudflare Radar report

Questions about loispay.io

Is loispay.io legit?

PhishDestroy rates loispay.io as critical risk (86/100) from the recorded evidence; it was first recorded on 2026-11-07. Stored VirusTotal result: 12/92 engines flagged. malicious: 11. suspicious: 1. Analysis time (as stored): 2026-11-07T14:40:55Z. Retrieved (as stored): 2026-11-08T02:29:02Z. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is loispay.io safe to connect a wallet?

This report does not record which wallet requests loispay.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 loispay.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 · 3 captures

URLScan · 2026-11-06 1 / 3 Used in the analysis Source file SHA-256: de0bcac6ff2de22b0f874149e9b71886725d0959eede6de9f2668c28bba9f43e SHA-256 of the prepared copy given to the model: 82a80b04332ca14c768efc390dd3d3ba82726f804c75086131300438c1bd00cb
SourceURLScan · 2026-11-06
Recorded
StateStored capture
HTTP status200
Final URLhttp://loispay.io/
Position1 / 3
Open capture Source Report Wayback Download
All capture links and hashes (3)

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 66 report ↗
IP Reputation Germany31.97.217.217 abuse score 0/100 0 reports checked Nov 7, 2026
OTX tags 2026-11all-domainsblocklistcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
Registrar GoDaddy US(US)
Abuse contact["fb6ff66ef97c0518s@"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for loispay.io →
RegistrationCreated Oct 4, 2025 — Expires Oct 4, 2027
Registrant countryUnited States VirusTotal WHOIS
Registrant3495bcf1839c6374fb6ff66ef97c0518s@ VirusTotal WHOIS
WHOIS statusclientDeleteProhibitedclientRenewProhibitedclientTransferProhibitedclientUpdateProhibitedautoRenewPeriod
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedNov 7, 2026
DOM Analysisanalyzed Nov 8, 2026score 10/1002 brand signals
Submitted URLhttp://loispay.io/
Observed page title
LoisPay - Money Transfer with QR Code
Automated brand references
Across Apple
TLS Certificate
Issued by Let's Encrypt / YR2 · stored validity ends in 71 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Germany31.97.217.217
Network ASN
AS47583
Organization
Hostinger International Limited
Observed location
GermanyFrankfurt am Main, DE
Server header
Apache

Nameservers 2

  • ns64.domaincontrol.com
  • ns63.domaincontrol.com

SOA

  • nsname: ns63.domaincontrol.com
  • hostmaster: dns.jomax.net
  • serial: 2025101301
  • refresh: 28800
  • retry: 7200
  • expire: 604800
  • minttl: 600

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR2
Valid from
2026-10-20 06:04:38
Valid until
2027-01-18 06:04:37
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint6267590fda34f1369406e5d33b2fee1bbd69cc99e0f4d8d2a94012a9a26fbde1
Certificate names · 3 SANs
  • loispay.io
  • mail.loispay.io
  • www.loispay.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 · 31.97.217.217rapiddns.io
Recorded subdomains2

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

  • mail.loispay.ioDomain record
  • www.loispay.ioDomain record
Technologies · 6 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

12 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
CRDF
DNS8
VIPRE
Lionic
Sophos
CyRadar
Fortinet
SOCRadar
Kaspersky
Seclookup
Gridinsoft
alphaMountain.ai

Captured network requests

Network requests: 44 SHA-256 hashes: 43 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-07 13:28 UTC.

Open this scan on URLScan 01a1b2a1-6fd6-71d8-9c43-d25c6589710c ↗

All retained availability observations5

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_probeunknown
    Observation source
    current_http_probe
    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-08 01:36:22.000000
    Evidence SHA-256
    d19de71d92a113de7ca6156b71e28dce7a76ae3184dde18dbc9251c94ec32723
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-08 01:36:22
    Evidence reason
    timeout
  2. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-08 01:36:22.000000
    Evidence SHA-256
    d19de71d92a113de7ca6156b71e28dce7a76ae3184dde18dbc9251c94ec32723
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-08 01:36:22
    Evidence reason
    timeout
  3. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-07 23:22:04.326583
    Evidence SHA-256
    19ed99e260d67463304cd035997394a09991119b8c1f635f2967c41ae291fdce
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-07 23:22:04.326583
    Evidence reason
  4. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    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-07 14:24:26.000000
    Evidence SHA-256
    6aab93b4b9497a0d7fc91edfd957b1eb60f344dda95f3f5215f84602100fa778
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-07 14:24:26
    Evidence reason
  5. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-07 14:24:26.000000
    Evidence SHA-256
    6aab93b4b9497a0d7fc91edfd957b1eb60f344dda95f3f5215f84602100fa778
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-07 14:24:26
    Evidence reason

Threat Response Pipeline

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

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
    loispay.io detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · OTX Community References · Cloudflare Radar: Malicious · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 8 of 8
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 66
  • 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: 12/92
  • OTX Community References
    Community publication references on AlienVault OTX: 2. References are not vendor verdicts and are excluded from the evidence score.
  • Cloudflare Radar: Malicious
    Cloudflare Radar classified this domain as Malware, Security threats
  • 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 Recorded: 1 of 1

Recorded activity

4 entries
  1. AlienVault OTX

    2 community references

    View source
  2. VirusTotal

    12/92 engine detections

    View source
  3. Added to PhishDestroy

    loispay.io

    View source
  4. URLScan

    Malicious · engine verdict · score 66

    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.

loispay.io

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 12 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Malicious OTX 2 refs 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?

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

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

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

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