Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 20/92 engines flagged. malicious: 18. suspicious: 2. Analysis time (as stored): 2026-11-06T04:14:44Z. Retrieved (as stored): 2026-11-06T17:49:39Z. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
programaregularize.org favicon

programaregularize.org

In short

PhishDestroy first recorded programaregularize.org on 2026-11-04. Stored VirusTotal result: 20/92 engines flagged. malicious: 18. suspicious: 2. Analysis time (as stored): 2026-11-06T04:14:44Z. Retrieved (as stored): 2026-11-06T17:49:39Z. Google Safe Browsing flags it.

Review the evidence
Registrar
United StatesDynadot
Resolved IP
Canada188.114.97.1CloudFlare, Inc. · CDN
Registered
Oct 26, 2026
First observed
Nov 4, 2026
PhishDestroy assessment Critical
100/100
Evidence score
First observed Nov 4, 2026 18:57 UTC · PhishDestroy
Risk signals
VirusTotal detections: 20/92 Young domain: 12 days old Google Safe Browsing: threat flag recorded
VirusTotal
20 / 92
engine detections ·
Google Safe Browsing
Flagged
OTX
3
community references
URLScan
Malicious
Page captures
5
open gallery
Domain age
12 days
registered 2026-10-26 according to WHOIS
OTX: 3 refs Nov 4, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded programaregularize.org on 2026-11-04. Stored VirusTotal result: 20/92 engines flagged. malicious: 18. suspicious: 2. Analysis time (as stored): 2026-11-06T04:14:44Z. Retrieved (as stored): 2026-11-06T17:49:39Z. Google Safe Browsing flags it. Risk: critical (100/100). Registrar: Dynadot. Hosting: Cloudflare, Inc. Do not enter credentials or connect a wallet.

Critical
VirusTotal
20 / 92
Hosting
Canada188.114.97.1CloudFlare, Inc. · CDN
Registrar
United StatesDynadot
Registered
Oct 26, 2026
OTX
3 community refs
Page captures
5
Page captures Source results Registration record

Recorded source summary

PhishDestroy stores a record for programaregularize.org. 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 20 / 92 · Google Safe Browsing: flagged · OTX 3 references 6 sources

VirusTotal

20 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
43
Malicious
18
Suspicious
2
Undetected
29

Vendor labels

CRDF
malicious
ESET
suspicious
VIPRE
phishing
G-Data
phishing
Lionic
phishing
Sophos
phishing
CyRadar
phishing
Webroot
malicious
Emsisoft
phishing
Fortinet
phishing
Netcraft
malicious
SOCRadar
phishing
URLQuery
malicious
Kaspersky
phishing
OpenPhish
phishing
Gridinsoft
suspicious
BitDefender
phishing
alphaMountain.ai
phishing
Google Safe Browsing
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Registrar

Dynadot Inc

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3033::6815:108b
  • TTL, seconds
    21600
    Type
    NS
    Value
    charles.ns.cloudflare.com
  • TTL, seconds
    21600
    Type
    NS
    Value
    isla.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    104.21.16.139
  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    charles.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    172.67.212.243
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3037::ac43:d4f3

DNS records observed

JARM fingerprint

27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c

Certificate

Subject alternative names
  • *.programaregularize.org
  • programaregularize.org
Issuer
Let's Encrypt / YE2
Serial
58946b44e2a93fa091bb78d26f040e53ef
SHA-256
d70bc954ce3fd36e446638c1553c37c1ce66e061b293cc388871d27a634b583c
Subject
programaregularize.org
Valid until
Valid from

Registration record

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

Registry data (RDAP)

Status
  • transfer prohibited
Registry events
Expiration
Last changed
Registration
Registrar expiration
Last RDAP database update
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 43,
    "malicious": 18,
    "suspicious": 2,
    "undetected": 29
}
Vendor labels
{
    "CRDF": "malicious",
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Emsisoft": "phishing",
    "Fortinet": "phishing",
    "Netcraft": "malicious",
    "SOCRadar": "phishing",
    "URLQuery": "malicious",
    "Kaspersky": "phishing",
    "OpenPhish": "phishing",
    "Gridinsoft": "suspicious",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Google Safe Browsing": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Registrar
Dynadot Inc
Created
2026-10-26T16:54:35Z
Expires
2027-10-26T16:54:35Z
Updated
2026-10-26T16:59:18Z
First seen
2026-10-26T17:14:21Z
DNS records
[
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3033::6815:108b"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "charles.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "isla.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.16.139"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "charles.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.212.243"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3037::ac43:d4f3"
    }
]
Dns at
2026-11-02T11:06:39Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "*.programaregularize.org",
        "programaregularize.org"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "58946b44e2a93fa091bb78d26f040e53ef",
    "sha256": "d70bc954ce3fd36e446638c1553c37c1ce66e061b293cc388871d27a634b583c",
    "subject": "programaregularize.org",
    "valid_to": "2027-01-24T16:09:54Z",
    "valid_from": "2026-10-26T16:09:55Z"
}
Registration record
{
    "registrar": "Dynadot Inc",
    "registrar_iana_id": "472",
    "registrar_url": "http://www.dynadot.com",
    "created": "2026-10-26T16:54:35Z",
    "updated": "2026-10-26T16:59:18Z",
    "expires": "2027-10-26T16:54:35Z",
    "status": [
        "addPeriod",
        "clientTransferProhibited"
    ],
    "nameservers": [
        "charles.ns.cloudflare.com",
        "isla.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "transfer prohibited"
    ],
    "events": {
        "expiration": "2027-10-26T16:54:35Z",
        "last changed": "2026-10-26T16:59:19Z",
        "registration": "2026-10-26T16:54:35Z",
        "registrar expiration": "2027-10-26T16:54:35Z",
        "last update of RDAP database": "2026-11-05T08:33:51Z"
    }
}
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
20
denominator
92
malicious
null
suspicious
null
vendors
["alphaMountain.ai","BitDefender","CRDF","CyRadar","ESET","Emsisoft","Forcepoint ThreatSeeker","Fortinet","G-Data","Google Safe Browsing","Gridinsoft","Kaspersky","Lionic","Netcraft","OpenPhish","SOCRadar","Sophos","URLQuery","VIPRE","Webroot"]
observed_at
2026-11-06 04:14:44
checked_at
2026-11-06 18:49:44
fetched_at
2026-11-06 17:49:45
time_basis
as stored; legacy timezone not established

Google Safe Browsing

Threat flag recorded

Open report

URLScan

Malicious

SHA-256 ef38e4ea47b673aa9640d49a627b3bf9ba0e4e066f9aeba851c0234e2b5ac68a

Open report
URLScanOriginal source recordObserved: 20 fields

Observed: · Retrieved:

Report ID

01a19a94-bd95-70af-ac15-c5c144b39f7d

Final URL

https://programaregularize.org/

HTTP response

403

Redirect type

https-only

Redirects

  • To
    https://programaregularize.org/
    From
    http://programaregularize.org/
    Status
    307

IP address

172.67.212.243

Contacted domains

  • challenges.cloudflare.com

Contacted IP addresses

  • 104.18.95.41
  • 104.18.94.41
  • 172.67.212.243

Autonomous systems (ASN)

  • 13335

Linked domains

  • www.cloudflare.com

Document hash

0130a3ea16b21c8c9a665f39c82af17c65d8e6f717acf3ecc5ce95a00b8a6f1f

JavaScript globals

  • onTurnstileSuccess
  • _cf_translation
  • turnstile
  • singleSelectors
  • groupSelectors

TLS session and certificate

Subject alternative names
  • *.programaregularize.org
  • programaregularize.org
Cipher
AES_128_GCM
Issuer
YE2
Subject
programaregularize.org
Protocol
QUIC
Valid until
Valid from

Domain age, days

5

Registered domain age, days

5

Certificate age, days

6

Certificate validity, days

89

Page requests

6

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
94
Malicious
Yes
Overall verdict
Tags
  • phishing
Score
100
Brands
  • genericcloudflare
Malicious
Yes
Categories
  • phishing
URLScan verdict
Tags
  • phishing
Score
100
Brands
  • Generic Cloudflare
Malicious
Yes
Categories
  • phishing

HTTP headers

Server
cloudflare
Content-type
text/html; charset=utf-8
X-frame-options
SAMEORIGIN
Referrer-policy
same-origin
Original source fields · JSON
Uuid
01a19a94-bd95-70af-ac15-c5c144b39f7d
Final url
https://programaregularize.org/
Status
403
Redirected
https-only
Redirects
[
    {
        "to": "https://programaregularize.org/",
        "from": "http://programaregularize.org/",
        "status": 307
    }
]
Ip
172.67.212.243
Contacted domains
[
    "challenges.cloudflare.com"
]
Contacted IP addresses
[
    "104.18.95.41",
    "104.18.94.41",
    "172.67.212.243"
]
Asns
[
    "13335"
]
Linked domains
[
    "www.cloudflare.com"
]
Document hash
0130a3ea16b21c8c9a665f39c82af17c65d8e6f717acf3ecc5ce95a00b8a6f1f
Globals
[
    "onTurnstileSuccess",
    "_cf_translation",
    "turnstile",
    "singleSelectors",
    "groupSelectors"
]
Tls
{
    "san": [
        "*.programaregularize.org",
        "programaregularize.org"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE2",
    "subject": "programaregularize.org",
    "protocol": "QUIC",
    "valid_to": "2027-01-24T16:09:54Z",
    "valid_from": "2026-10-26T16:09:55Z"
}
Domain age days
5
Apex age days
5
Tls age days
6
Tls valid days
89
Requests
6
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 94,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "genericcloudflare"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "Generic Cloudflare"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=utf-8",
    "x-frame-options": "SAMEORIGIN",
    "referrer-policy": "same-origin"
}

OTX

3 community references

Open report

Cloudflare Radar

provider verdict: clean

Open report
Cloudflare RadarOriginal source recordObserved: 1 field

Observed: · Retrieved:

Report ID

b481dd87-03b3-442f-8c05-3c55d3465171
Original source fields · JSON
Uuid
b481dd87-03b3-442f-8c05-3c55d3465171

Spamhaus DBL

Check recorded; verdict not retained

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

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
0
Archived days
1
Average page size, bytes
5384
Original source fields · JSON
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-10-27T01:10:37Z",
    "first": "2026-10-27T01:10:37Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 5384
}

Questions about programaregularize.org

Is programaregularize.org legit?

PhishDestroy rates programaregularize.org as critical risk (100/100) from the recorded evidence; it was first recorded on 2026-11-04. Stored VirusTotal result: 20/92 engines flagged. malicious: 18. suspicious: 2. Analysis time (as stored): 2026-11-06T04:14:44Z. Retrieved (as stored): 2026-11-06T17:49:39Z. Google Safe Browsing flags it. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is programaregularize.org safe to connect a wallet?

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

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

URLScan · 2026-11-02 1 / 5
SourceURLScan · 2026-11-02
Recorded
StateStored capture
HTTP status403
Final URLhttps://programaregularize.org/
Position1 / 5
Open capture Source Report Wayback Download
All capture links and hashes (5)

Domain details

Domain
URLScan verdict Malicious score 100 Phishing report ↗
Google Safe Browsing Flagged Social engineering checked Nov 7, 2026
IP Context Canada188.114.97.1 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-11all-domainsblocklistcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
Registrar Dynadot US(US)
Abuse contact["abuse@dynadot.com"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for programaregularize.org →
RegistrationCreated Oct 26, 2026 (12d · Very New!) — Expires Oct 26, 2027
Technical detailsProvenance & timestamps
First DetectedNov 4, 2026
Submitted URLhttps://programaregularize.org/robots.txt
Observed page title
Suspected Phishing | Cloudflare
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 77 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Canada188.114.97.1
Network ASN
AS13335
Organization
CloudFlare, Inc.
Observed location
CanadaToronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • charles.ns.cloudflare.com
  • isla.ns.cloudflare.com

Registrar abuse contact VirusTotal WHOIS

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-10-26 16:09:55
Valid until
2027-01-24 16:09:54
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintd70bc954ce3fd36e446638c1553c37c1ce66e061b293cc388871d27a634b583c
Certificate names · 2 SANs
  • *.programaregularize.org
  • programaregularize.org

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

viewdns.info · 188.114.97.1rapiddns.io

Latest Classified Outcome 2026-11-07 22:35:51 UTC

The domain no longer resolves in DNS.

Technical details
Primary outcome DNS inactive reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Probe Inconclusive 20% 2026-11-07 23:13:54 UTC
RDAP registration
Observed timeline current episode first observed: 2026-11-04 22:33:57 UTC first terminal observation: 2026-11-04 22:33:57 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.
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

20 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 20 detections
CRDF
ESET
VIPRE
G-Data
Lionic
Sophos
CyRadar
Webroot
Emsisoft
Fortinet
Netcraft
SOCRadar
URLQuery
Kaspersky
OpenPhish
Gridinsoft
BitDefender
alphaMountain.ai
Google Safe Browsing
Forcepoint ThreatSeeker
Registration & observation details3

Availability observations

Outcome first observed
Observation window ends
Estimate basis
first_observation_only

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: 6 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-11-04 22:59 UTC.

Open this scan on URLScan 01a19a94-bd95-70af-ac15-c5c144b39f7d ↗

Stored observation history4

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

    dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  3. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

  4. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

Separate monitor HTTP observation

Source: domain_monitor. This stored snapshot does not establish current availability.

Observed · UTC
Recorded HTTP status
No response code recorded
Probe value as recorded
0
Original source timestamp
2026-11-04 08:45:47
All retained availability observations11

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. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    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-07 23:35:51.044000
    Evidence SHA-256
    47a940cdf79d38a054ded6a22282da6ad26877094f3d035a40e3a1ac2b3fe0fb
    Evidence timestamp as recorded
    2026-11-07 23:35:51.044000
  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-07 12:12:44.000000
    Evidence SHA-256
    cacf38f76e48aaeba1308729721d9f39bdfd318a249b6e0d4e901be39f9a3e3a
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-07 12:12:44
    Evidence reason
    timeout
  3. 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 03:51:47.000000
    Evidence SHA-256
    f1871713d9f128d1fdb553e5a57d6b5cb44391515b7ace10fb7b8d93a3d9e38b
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-07 03:51:47
    Evidence reason
    unavailable
  4. 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 00:03:59.000000
    Evidence SHA-256
    12556a81db4e37c6c76c02c59bfc818244b1765274a384b2a2ccf6aad24cce4c
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-07 00:03:59
    Evidence reason
    unavailable
  5. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    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-06 23:34:26.656104
    Evidence SHA-256
    8b02b4b45d1592248a12e7bd74c9b4233b6261658ac38ae3d5c534fba919a2a7
    Evidence timestamp as recorded
    2026-11-06 23:34:26.656104
  6. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    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-06 23:34:26.656104
    Evidence SHA-256
    8b02b4b45d1592248a12e7bd74c9b4233b6261658ac38ae3d5c534fba919a2a7
    Evidence timestamp as recorded
    2026-11-06 23:34:26.656104
  7. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    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-05 23:34:11.592934
    Evidence SHA-256
    078231950172bd801d031befdc6c31ba98ad1d16e90b1161cd4f236bee1aa7c7
    Evidence timestamp as recorded
    2026-11-05 23:34:11.592934
  8. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    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-05 23:34:11.592934
    Evidence SHA-256
    078231950172bd801d031befdc6c31ba98ad1d16e90b1161cd4f236bee1aa7c7
    Evidence timestamp as recorded
    2026-11-05 23:34:11.592934
  9. 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-05 03:29:02.000000
    Evidence SHA-256
    764e691add507d0bc8ea2976b0d9898cd48f27b1444f9a011c15e80eb0d3ed8a
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-05 03:29:02
    Evidence reason
    unavailable
  10. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    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-04 23:33:57.507178
    Evidence SHA-256
    d90f23ef2fceb6cde0c0c3933f7f981919c265f78b9eb9b6f7967fe69561daa5
    Evidence timestamp as recorded
    2026-11-04 23:33:57.507178
  11. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    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-04 23:33:57.507178
    Evidence SHA-256
    d90f23ef2fceb6cde0c0c3933f7f981919c265f78b9eb9b6f7967fe69561daa5
    Evidence timestamp as recorded
    2026-11-04 23:33:57.507178

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
    programaregularize.org detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Google Safe Browsing · OTX Community References · Forensic Evidence Collected Recorded: 7 of 7
  • 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: 20/92
  • Google Safe Browsing
    Listed as unsafe by Google Safe Browsing (Google Transparency Report)
  • 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

5 entries
  1. AlienVault OTX

    3 community references

    View source
  2. Google Safe Browsing

    Threat flag recorded

    View source
  3. VirusTotal

    20/92 engine detections

    View source
  4. Added to PhishDestroy

    programaregularize.org

    View source
  5. URLScan

    Malicious

    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.

programaregularize.org

Evidence & External Reports

Security Analysis
URLScan Malicious VirusTotal 20 det. ChainPatrol URLQuery Google SB Flagged 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 programaregularize.org)
  • 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/programaregularize.org"
  title="PhishDestroy threat report for programaregularize.org"
  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>