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

wwllinc.com

In short

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

Review the evidence
Registrar
Wild West Domains
Resolved IP
United States144.172.108.83RouterHosting LLC
Registered
Oct 22, 2026
First observed
Nov 1, 2026
PhishDestroy assessment High
65/100
Evidence score
First observed Oct 31, 2026 23:00 UTC · PhishDestroy
Risk signals
VirusTotal detections: 5/92 Spamhaus DBL: spam domain Young domain: 9 days old
VirusTotal
5 / 92
engine detections ·
OTX
3
community references
URLScan
Malicious
Page captures
6
open gallery
Domain age
9 days
registered 2026-10-22 according to WHOIS · source data differ
OTX: 3 refs Nov 1, 2026
X Telegram API

Questions about wwllinc.com

Is wwllinc.com legit?

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

Is wwllinc.com safe to connect a wallet?

This report does not record which wallet requests wwllinc.com makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.

What should I do if I used wwllinc.com?

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

Explore

Source evidenceVirusTotal 5 / 92 · OTX 3 references 6 sources

VirusTotal

5 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 15 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
53
Malicious
4
Suspicious
1
Undetected
34

Vendor labels

CRDF
malicious
Fortinet
spam
SOCRadar
phishing
Gridinsoft
phishing
alphaMountain.ai
phishing

Reputation score

0

Categories

alphaMountain.ai
Phishing (alphaMountain.ai)

Registrar

Wild West Domains, LLC

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    21600
    Type
    NS
    Value
    ns2.bdm.microsoftonline.com
  • TTL, seconds
    21600
    Type
    NS
    Value
    ns4.bdm.microsoftonline.com
  • TTL, seconds
    3600
    Type
    SOA
    Responsible mailbox
    azuredns-hostmaster.microsoft.com
    Value
    ns1.bdm.microsoftonline.com
  • TTL, seconds
    3600
    Type
    A
    Value
    144.172.108.83
  • TTL, seconds
    3600
    Type
    TXT
    Value
    v=spf1 include:spf.protection.outlook.com -all
  • TTL, seconds
    3600
    Type
    MX
    Value
    wwllinc-com.mail.protection.outlook.com
    Priority
    0
  • TTL, seconds
    21600
    Type
    NS
    Value
    ns3.bdm.microsoftonline.com
  • TTL, seconds
    3600
    Type
    TXT
    Value
    mscid=VuE1co1D+xPMIpl4ShtqGYDLVoXx8S9/kogJszPTbUjPyKXLsCDWphPvAAssIuNlmtJMHE3cmfOGFR1dRBJnqQ==
  • TTL, seconds
    21600
    Type
    NS
    Value
    ns1.bdm.microsoftonline.com

DNS records observed

JARM fingerprint

27d40d40d00040d00042d43d0000003d25bc6207ca8acd9652e99aa3724a08

Certificate

Subject alternative names
  • wwllinc.com
  • www.wwllinc.com
Issuer
Let's Encrypt / YE1
Serial
55fbc15a0e248c7ca95672b9980499cd726
SHA-256
1cfe1c0fd2f60d0f3e2afc27d164eb96854348af52f8751f76b1dcdd611fc0c9
Subject
wwllinc.com
Valid until
Valid from

Registration record

Registrar
Wild West Domains, LLC
Registrar IANA ID
440
Registrar URL
http://www.wildwestdomains.com
Registered
Updated
Expires
Status
  • clientDeleteProhibited
  • clientRenewProhibited
  • clientTransferProhibited
  • clientUpdateProhibited
Nameservers
  • ns1.bdm.microsoftonline.com
  • ns2.bdm.microsoftonline.com
DNSSEC
unsigned

Registry data (RDAP)

Status
  • client delete prohibited
  • client renew prohibited
  • client transfer prohibited
  • client update prohibited
Registry events
Expiration
Last changed
Registration
Last RDAP database update
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 53,
    "malicious": 4,
    "suspicious": 1,
    "undetected": 34
}
Vendor labels
{
    "CRDF": "malicious",
    "Fortinet": "spam",
    "SOCRadar": "phishing",
    "Gridinsoft": "phishing",
    "alphaMountain.ai": "phishing"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
Registrar
Wild West Domains, LLC
Created
2026-10-22T17:51:26Z
Expires
2027-10-22T17:51:26Z
Updated
2026-10-22T17:51:27Z
First seen
2026-10-23T02:33:06Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns2.bdm.microsoftonline.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns4.bdm.microsoftonline.com"
    },
    {
        "ttl": 3600,
        "type": "SOA",
        "rname": "azuredns-hostmaster.microsoft.com",
        "value": "ns1.bdm.microsoftonline.com"
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "144.172.108.83"
    },
    {
        "ttl": 3600,
        "type": "TXT",
        "value": "v=spf1 include:spf.protection.outlook.com -all"
    },
    {
        "ttl": 3600,
        "type": "MX",
        "value": "wwllinc-com.mail.protection.outlook.com",
        "priority": 0
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns3.bdm.microsoftonline.com"
    },
    {
        "ttl": 3600,
        "type": "TXT",
        "value": "mscid=VuE1co1D+xPMIpl4ShtqGYDLVoXx8S9/kogJszPTbUjPyKXLsCDWphPvAAssIuNlmtJMHE3cmfOGFR1dRBJnqQ=="
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns1.bdm.microsoftonline.com"
    }
]
Dns at
2026-10-30T16:59:38Z
Jarm
27d40d40d00040d00042d43d0000003d25bc6207ca8acd9652e99aa3724a08
Certificate
{
    "san": [
        "wwllinc.com",
        "www.wwllinc.com"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "55fbc15a0e248c7ca95672b9980499cd726",
    "sha256": "1cfe1c0fd2f60d0f3e2afc27d164eb96854348af52f8751f76b1dcdd611fc0c9",
    "subject": "wwllinc.com",
    "valid_to": "2027-01-20T17:10:15Z",
    "valid_from": "2026-10-22T17:10:16Z"
}
Registration record
{
    "registrar": "Wild West Domains, LLC",
    "registrar_iana_id": "440",
    "registrar_url": "http://www.wildwestdomains.com",
    "created": "2026-10-22T17:51:26Z",
    "updated": "2026-10-22T17:51:27Z",
    "expires": "2027-10-22T17:51:26Z",
    "status": [
        "clientDeleteProhibited",
        "clientRenewProhibited",
        "clientTransferProhibited",
        "clientUpdateProhibited"
    ],
    "nameservers": [
        "ns1.bdm.microsoftonline.com",
        "ns2.bdm.microsoftonline.com"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "client delete prohibited",
        "client renew prohibited",
        "client transfer prohibited",
        "client update prohibited"
    ],
    "events": {
        "expiration": "2027-10-22T17:51:26Z",
        "last changed": "2026-10-22T17:51:27Z",
        "registration": "2026-10-22T17:51:26Z",
        "last update of RDAP database": "2026-10-30T10:03:30Z"
    }
}
Separate source record · 4 malicious + 1 suspicious / 92 · 2026-10-30 16:59:17 UTC

The summary above and this provider record were collected at different times. Both remain available; malicious and suspicious classifications are shown separately.

record_source
collected_observations.vt
analysis_at
2026-10-30T16:59:17Z
fetched_at
2026-11-01T00:08:56Z
stats
{"timeout":0,"harmless":53,"malicious":4,"suspicious":1,"undetected":34}

Spamhaus DBL

spam domain

URLScan

Malicious

SHA-256 14992a6348a4fe95866bf8190cf633c3a4ddcce3e6f821e958e836eff473e40b

Open report
URLScanOriginal source recordObserved: 21 fields

Observed: · Retrieved:

Report ID

01a18f6f-7064-771a-89b5-25f94670b25b

Final URL

https://wwllinc.com/connect/

HTTP response

200

Redirects

  • To
    https://wwllinc.com/connect/
    From
    https://wwllinc.com/connect/

IP address

144.172.108.83

Reverse DNS (PTR)

83.108.172.144.static.cloudzy.com

Contacted domains

  • challenges.cloudflare.com

Contacted IP addresses

  • 104.18.94.41
  • 2606:4700::6812:5e29
  • 104.18.95.41
  • 144.172.108.83

Autonomous systems (ASN)

  • 13335
  • 14956

Server countries

  • US

Document hash

14992a6348a4fe95866bf8190cf633c3a4ddcce3e6f821e958e836eff473e40b

JavaScript globals

  • ridgeNexus71
  • turnstile

Cookies

  • PHPSESSID

TLS session and certificate

Subject alternative names
  • wwllinc.com
  • www.wwllinc.com
Cipher
AES_128_GCM
Issuer
YE1
Subject
wwllinc.com
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

2187

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

Registered domain age, days

2187

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

Certificate age, days

8

Certificate validity, days

89

Page requests

7

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
96
Malicious
Yes
Overall verdict
Tags
  • phishing
Score
100
Brands
  • microsoft
Malicious
Yes
Categories
  • phishing
URLScan verdict
Tags
  • phishing
Score
100
Brands
  • Microsoft
Malicious
Yes
Categories
  • phishing

HTTP headers

Server
Apache/2.4.58 (Ubuntu)
Content-type
text/html; charset=UTF-8
Original source fields · JSON
Uuid
01a18f6f-7064-771a-89b5-25f94670b25b
Final url
https://wwllinc.com/connect/
Status
200
Redirects
[
    {
        "to": "https://wwllinc.com/connect/",
        "from": "https://wwllinc.com/connect/"
    }
]
Ip
144.172.108.83
Ptr
83.108.172.144.static.cloudzy.com
Contacted domains
[
    "challenges.cloudflare.com"
]
Contacted IP addresses
[
    "104.18.94.41",
    "2606:4700::6812:5e29",
    "104.18.95.41",
    "144.172.108.83"
]
Asns
[
    "13335",
    "14956"
]
Countries
[
    "US"
]
Document hash
14992a6348a4fe95866bf8190cf633c3a4ddcce3e6f821e958e836eff473e40b
Globals
[
    "ridgeNexus71",
    "turnstile"
]
Cookies
[
    "PHPSESSID"
]
Tls
{
    "san": [
        "wwllinc.com",
        "www.wwllinc.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE1",
    "subject": "wwllinc.com",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-20T17:10:15Z",
    "valid_from": "2026-10-22T17:10:16Z"
}
Domain age days
2187

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

Apex age days
2187

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

Tls age days
8
Tls valid days
89
Requests
7
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 96,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "microsoft"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "Microsoft"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "Apache/2.4.58 (Ubuntu)",
    "content-type": "text/html; charset=UTF-8"
}

OTX

3 community references

Open report

Cloudflare Radar

provider verdict: clean

Open report
Cloudflare RadarOriginal source recordObserved: 1 field

Observed: · Retrieved:

Report ID

34e2b3e3-33c7-4eb8-86cf-03e49b84000f
Original source fields · JSON
Uuid
34e2b3e3-33c7-4eb8-86cf-03e49b84000f

Google Safe Browsing

No threat flag

Open report

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

Mail configuration

MX records
  • wwllinc-com.mail.protection.outlook.com
SPF record
v=spf1 include:spf.protection.outlook.com -all
Providers
  • Microsoft 365
SPF lookups
1

CAA records

Domain
wwllinc.com

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
1
Archived days
2
Snapshots per day
0
Average page size, bytes
1164

DNS servers

Nameservers
  • IP address
    13.107.236.208
    Host
    ns1.bdm.microsoftonline.com
  • IP address
    150.171.21.208
    Host
    ns2.bdm.microsoftonline.com
  • IP address
    204.14.183.208
    Host
    ns3.bdm.microsoftonline.com
  • IP address
    208.84.5.208
    Host
    ns4.bdm.microsoftonline.com
DNS zone
wwllinc.com

Location

IP address
144.172.108.83
ASN
14956
Organization
RouterHosting LLC
City
Las Vegas
Country
US

DNS records

A
  • 144.172.108.83
MX
  • Mail server
    wwllinc-com.mail.protection.outlook.com
    Priority
    0
NS
  • ns2.bdm.microsoftonline.com
  • ns3.bdm.microsoftonline.com
  • ns4.bdm.microsoftonline.com
  • ns1.bdm.microsoftonline.com
SOA
Primary nameserver
ns1.bdm.microsoftonline.com
Hostmaster
azuredns-hostmaster.microsoft.com
Serial
1
Refresh, seconds
3600
Retry, seconds
300
Expiry, seconds
2419200
Minimum TTL, seconds
300
TXT
  • v=spf1 include:spf.protection.outlook.com -all
  • mscid=VuE1co1D+xPMIpl4ShtqGYDLVoXx8S9/kogJszPTbUjPyKXLsCDWphPvAAssIuNlmtJMHE3cmfOGFR1dRBJnqQ==

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

IP lookup

IP address
144.172.108.83
IP version
4

Registration record

Registrar
Wild West Domains, LLC
Registered
Updated
Expires
Status
  • clientDeleteProhibited https://icann.org/epp
  • clientRenewProhibited https://icann.org/epp
  • clientTransferProhibited https://icann.org/epp
  • clientUpdateProhibited https://icann.org/epp
Nameservers
  • ns1.bdm.microsoftonline.com
  • ns2.bdm.microsoftonline.com
Original source fields · JSON
Mail configuration
{
    "mx": [
        "wwllinc-com.mail.protection.outlook.com"
    ],
    "spf": "v=spf1 include:spf.protection.outlook.com -all",
    "providers": [
        "Microsoft 365"
    ],
    "spf_lookups": 1
}
Caa records
{
    "domain": "wwllinc.com"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-10-22T20:18:22Z",
    "first": "2021-12-31T06:37:04Z",
    "changes": 1,
    "days_archived": 2,
    "scans_per_day": 0,
    "avg_page_bytes": 1164
}
Dns server
{
    "ns": [
        {
            "ip": "13.107.236.208",
            "host": "ns1.bdm.microsoftonline.com"
        },
        {
            "ip": "150.171.21.208",
            "host": "ns2.bdm.microsoftonline.com"
        },
        {
            "ip": "204.14.183.208",
            "host": "ns3.bdm.microsoftonline.com"
        },
        {
            "ip": "208.84.5.208",
            "host": "ns4.bdm.microsoftonline.com"
        }
    ],
    "zone": "wwllinc.com"
}
Location
{
    "ip": "144.172.108.83",
    "asn": "14956",
    "org": "RouterHosting LLC",
    "city": "Las Vegas",
    "country": "US"
}
DNS records
{
    "A": [
        "144.172.108.83"
    ],
    "MX": [
        "{\"exchange\": \"wwllinc-com.mail.protection.outlook.com\", \"priority\": 0}"
    ],
    "NS": [
        "ns2.bdm.microsoftonline.com",
        "ns3.bdm.microsoftonline.com",
        "ns4.bdm.microsoftonline.com",
        "ns1.bdm.microsoftonline.com"
    ],
    "SOA": "{\"nsname\": \"ns1.bdm.microsoftonline.com\", \"hostmaster\": \"azuredns-hostmaster.microsoft.com\", \"serial\": 1, \"refresh\": 3600, \"retry\": 300, \"expire\": 2419200, \"minttl\": 300}",
    "TXT": [
        "v=spf1 include:spf.protection.outlook.com -all",
        "mscid=VuE1co1D+xPMIpl4ShtqGYDLVoXx8S9/kogJszPTbUjPyKXLsCDWphPvAAssIuNlmtJMHE3cmfOGFR1dRBJnqQ=="
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Get ip
{
    "ip": "144.172.108.83",
    "family": 4
}
Registration record
{
    "registrar": "Wild West Domains, LLC",
    "created": "2026-10-22T17:51:26Z",
    "updated": "2026-10-22T17:51:27Z",
    "expires": "2027-10-22T17:51:26Z",
    "status": [
        "clientDeleteProhibited https://icann.org/epp",
        "clientRenewProhibited https://icann.org/epp",
        "clientTransferProhibited https://icann.org/epp",
        "clientUpdateProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "ns1.bdm.microsoftonline.com",
        "ns2.bdm.microsoftonline.com"
    ]
}
Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 6 captures

Primary capture 1 / 6
SourcePrimary capture
Recorded
StateStored capture
HTTP status200
Final URLhttps://wwllinc.com/connect/
Position1 / 6
Open capture Wayback Download
All capture links and hashes (6)

Domain details

Domain
OTX tags 2026-11all-domainsblocklistcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
Registrar Wild West Domains
Abuse contact["abuse@wildwestdomains.com"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for wwllinc.com →
RegistrationCreated Oct 22, 2026 (9d · Very New!) — Expires Oct 22, 2027
WHOIS statusclientDeleteProhibitedclientRenewProhibitedclientTransferProhibitedclientUpdateProhibited
Technical detailsProvenance & timestamps
First DetectedNov 1, 2026
Submitted URLhttp://wwllinc.com/connect
TLS Certificate
Issued by Let's Encrypt / YE1 · stored validity ends in 80 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
United States144.172.108.83
Network ASN
AS14956
Organization
RouterHosting LLC
Observed location
United StatesLas Vegas, US
Server header
Apache/2.4.58 (Ubuntu)

Nameservers 2

  • ns1.bdm.microsoftonline.com
  • ns2.bdm.microsoftonline.com

SOA

  • nsname: ns1.bdm.microsoftonline.com
  • hostmaster: azuredns-hostmaster.microsoft.com
  • serial: 1
  • refresh: 3600
  • retry: 300
  • expire: 2419200
  • minttl: 300

Registrar abuse contact VirusTotal WHOIS

Mail routing 1 MX record

  • wwllinc-com.mail.protection.outlook.compriority 0

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-10-22 17:10:16
Valid until
2027-01-20 17:10:15
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint1cfe1c0fd2f60d0f3e2afc27d164eb96854348af52f8751f76b1dcdd611fc0c9
Certificate names · 2 SANs
  • wwllinc.com
  • www.wwllinc.com

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

viewdns.info · 144.172.108.83rapiddns.io
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

5 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 5 detections
alphaMountain.ai
CRDF
Fortinet
Gridinsoft
SOCRadar

Captured network requests

Network requests: 7 SHA-256 hashes: 5 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-31 23:07 UTC.

Open this scan on URLScan 01a18f6f-7064-771a-89b5-25f94670b25b ↗

All retained availability observations1

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

  1. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 00:07:13.489829
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

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

Recorded events: 9. 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
    wwllinc.com detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · OTX Community References · Forensic Evidence Collected Recorded: 7 of 7
  • Spamhaus DBL
    Spamhaus DBL recorded: spam domain
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan classified the page as malicious · Score: 100
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • VirusTotal
    Detections recorded on VirusTotal: 5/92
  • 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, stored screenshot
Publication & AvailabilityDestroyList Published Recorded: 1 of 1

Recorded activity

4 entries
  1. AlienVault OTX

    3 community references

    View source
  2. Added to PhishDestroy

    wwllinc.com

    View source
  3. URLScan

    Malicious

    View source
  4. VirusTotal

    5/92 engine detections

    View source
How we investigate & report

Public scans, evidence and abuse channels

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

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

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

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

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

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

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

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

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

Check for cloaking

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

wwllinc.com

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 5 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Open report OTX 3 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 wwllinc.com)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?
  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?
  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?
  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

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/wwllinc.com"
  title="PhishDestroy threat report for wwllinc.com"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>