Skip to security report
Analytics Dashboard
Suspicious Domain — Listed on PhishDestroy
Stored PhishDestroy threat listing. VirusTotal analysis stored; no vendor detections were recorded at check time. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
jortcas.com favicon

jortcas.com

In short

PhishDestroy records a blank capture of jortcas.com alongside a VirusTotal domain scan showing no detections across 92 engines.

Review the evidence
Registrar
Hong Kong SAR ChinaDominet (HK)
Resolved IP
Canada172.67.205.94Cloudflare, Inc. · CDN
Registered
Oct 26, 2026
First observed
Oct 29, 2026
PhishDestroy assessment Medium
25/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
Stored PhishDestroy threat listing Young domain: 3 days old
VirusTotal
0 / 92
engine detections ·
Page captures
2
open gallery
Domain age
3 days
registered 2026-10-26 according to WHOIS
Oct 29, 2026 CDN
X Telegram API

Analysis

Medium
Status
Last known active
VirusTotal
0 / 92
Hosting
Canada172.67.205.94Cloudflare, Inc. · CDN
Registrar
Hong Kong SAR ChinaDominet (HK)
Registered
Oct 26, 2026
Page captures
2
Page captures Source results Registration record

PhishDestroy analysis, reviewed version

The captured page for jortcas.com is blank, showing no visible content, branding, or interactive elements in the screenshot. Because the capture returned no rendered content, there is no page purpose or main interaction to describe beyond the empty result itself.

VirusTotal's domain-scoped analysis of jortcas.com reported 0 detections out of 92 engines, with 0 malicious and 0 suspicious verdicts. No individual vendor flags were recorded in this result, so no specific engine names or verdicts apply to this case.

Source evidenceVirusTotal 0 / 92 7 sources

Cloudflare Radar

Suspicious

Open report
Cloudflare RadarOriginal source recordObserved: 12 fields

Observed: · Retrieved:

Report ID

85855041-7414-4c20-8868-f1968837cb90

Final URL

https://jortcas.com/

HTTP response

666

Navigation history

  • URL
    https://jortcas.com/
    Status
    666

DOM structure hash

4a06835d00d712ec4c568b1f0ccf643fb099dec477093d1e3c35bff8ea5ca969

Document hash

58392ab35ad8720610aefff5d72d8a7078a418becf9a15a9c9ea2c3da83f466f

Domain risk categories

  • Newly Seen Domains
  • Security Risks
  • New Domains

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    jortcas.com
    Type
    A
    Value
    104.21.77.72
  • Name
    jortcas.com
    Type
    A
    Value
    172.67.205.94

DNSSEC valid

No

IP address

127.0.1.20

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

Registration record

Registrar
Dominet (HK) Limited
Registered
Updated
Expires
Nameservers
  • wanda.ns.cloudflare.com
  • zod.ns.cloudflare.com
Original source fields · JSON
Uuid
85855041-7414-4c20-8868-f1968837cb90
Final url
https://jortcas.com/
Status
666
History
[
    {
        "url": "https://jortcas.com/",
        "status": 666
    }
]
DOM structure hash
4a06835d00d712ec4c568b1f0ccf643fb099dec477093d1e3c35bff8ea5ca969
Document hash
58392ab35ad8720610aefff5d72d8a7078a418becf9a15a9c9ea2c3da83f466f
Domain risks
[
    "Newly Seen Domains",
    "Security Risks",
    "New Domains"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "jortcas.com",
        "type": "A",
        "value": "104.21.77.72"
    },
    {
        "name": "jortcas.com",
        "type": "A",
        "value": "172.67.205.94"
    }
]
Dnssec valid
false
Ip
127.0.1.20

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

Registration record
{
    "registrar": "Dominet (HK) Limited",
    "created": "2026-10-26T17:57:26Z",
    "updated": "2026-10-26T19:16:08Z",
    "expires": "2027-10-26T17:57:26Z",
    "nameservers": [
        "wanda.ns.cloudflare.com",
        "zod.ns.cloudflare.com"
    ]
}

VirusTotal

0 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
55
Malicious
0
Suspicious
0
Undetected
37

Reputation score

0

Registrar

Dominet (HK) Limited

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    21600
    Type
    NS
    Value
    wanda.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    TXT
    Value
    google-site-verification=3OMcVPdlCWefvS1OZ1Lv4FMpBjLABem_zTNChYH1ZUM
  • TTL, seconds
    300
    Type
    A
    Value
    104.21.77.72
  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    wanda.ns.cloudflare.com
  • TTL, seconds
    21600
    Type
    NS
    Value
    zod.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    172.67.205.94

DNS records observed

JARM fingerprint

27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c

Certificate

Subject alternative names
  • *.jortcas.com
  • jortcas.com
Issuer
Let's Encrypt / YE2
Serial
5a9d6818bd9cd151502c1508d86aead6c91
SHA-256
b95d5f58c6b08219e3ebd6b0945b8665e65840e75add2af6b3c17100c44200c7
Subject
jortcas.com
Valid until
Valid from

Registration record

Registrar
Dominet (HK) Limited
Registrar IANA ID
3775
Registrar URL
http://www.alibabacloud.com
Registered
Updated
Expires
Status
  • ok
Nameservers
  • ns1.google.com
  • ns2.google.com
  • wanda.ns.cloudflare.com
  • zod.ns.cloudflare.com
DNSSEC
unsigned

Registry data (RDAP)

Status
  • active
Registry events
Expiration
Registration
Registrar expiration
Last RDAP database update
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 55,
    "malicious": 0,
    "suspicious": 0,
    "undetected": 37
}
Reputation
0
Registrar
Dominet (HK) Limited
Created
2026-10-26T17:57:26Z
Expires
2027-10-26T17:57:26Z
Updated
2026-10-26T19:16:08Z
First seen
2026-10-26T19:24:08Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "wanda.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "TXT",
        "value": "google-site-verification=3OMcVPdlCWefvS1OZ1Lv4FMpBjLABem_zTNChYH1ZUM"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.77.72"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "wanda.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "zod.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.205.94"
    }
]
Dns at
2026-10-29T10:53:41Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "*.jortcas.com",
        "jortcas.com"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "5a9d6818bd9cd151502c1508d86aead6c91",
    "sha256": "b95d5f58c6b08219e3ebd6b0945b8665e65840e75add2af6b3c17100c44200c7",
    "subject": "jortcas.com",
    "valid_to": "2027-01-24T18:19:29Z",
    "valid_from": "2026-10-26T18:19:30Z"
}
Registration record
{
    "registrar": "Dominet (HK) Limited",
    "registrar_iana_id": "3775",
    "registrar_url": "http://www.alibabacloud.com",
    "created": "2026-10-26T17:57:26Z",
    "updated": "2026-10-26T17:57:26Z",
    "expires": "2027-10-26T17:57:26Z",
    "status": [
        "ok"
    ],
    "nameservers": [
        "ns1.google.com",
        "ns2.google.com",
        "wanda.ns.cloudflare.com",
        "zod.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "active"
    ],
    "events": {
        "expiration": "2027-10-26T17:57:26Z",
        "registration": "2026-10-26T17:57:26Z",
        "registrar expiration": "2027-10-26T17:57:26Z",
        "last update of RDAP database": "2026-10-26T17:57:26Z"
    }
}
Separate source record · 0 malicious + 0 suspicious / 92 · 2026-10-29 10:39:33 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-29T10:39:33Z
fetched_at
2026-10-29T15:12:40Z
stats
{"timeout":0,"harmless":55,"malicious":0,"suspicious":0,"undetected":37}

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

SHA-256 41a0c999036b94ea9bf56e17c07801c0e8a4cf9bfdba854b05637c0c2410fb15

Open report
URLScanOriginal source recordObserved: 18 fields

Observed: · Retrieved:

Report ID

01a18399-db51-7614-b360-52d6d1016e3b

Final URL

https://jortcas.com/

HTTP response

666

IP address

104.21.77.72

Contacted domains

  • www.google.com

Contacted IP addresses

  • 142.251.156.119
  • 104.21.77.72

Autonomous systems (ASN)

  • 15169
  • 13335

Server countries

  • US

Document hash

c396babd7f49262f18a3a2ec34542c8e314cb4d869875152bb9675a6bb6066ea

Script hashes

  • 0bf32f6f5e0db7af1e5c2bf8701b0dda03b6b9fc7f09c66755a85200506b3a0b

TLS session and certificate

Subject alternative names
  • *.jortcas.com
  • jortcas.com
Cipher
AES_128_GCM
Issuer
YE2
Subject
jortcas.com
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

1

Registered domain age, days

1

Certificate age, days

1

Certificate validity, days

89

Page requests

4

Provider verdicts

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

HTTP headers

Server
cloudflare
Content-type
text/html; charset=utf-8
Original source fields · JSON
Uuid
01a18399-db51-7614-b360-52d6d1016e3b
Final url
https://jortcas.com/
Status
666
Ip
104.21.77.72
Contacted domains
[
    "www.google.com"
]
Contacted IP addresses
[
    "142.251.156.119",
    "104.21.77.72"
]
Asns
[
    "15169",
    "13335"
]
Countries
[
    "US"
]
Document hash
c396babd7f49262f18a3a2ec34542c8e314cb4d869875152bb9675a6bb6066ea
Script hashes
[
    "0bf32f6f5e0db7af1e5c2bf8701b0dda03b6b9fc7f09c66755a85200506b3a0b"
]
Tls
{
    "san": [
        "*.jortcas.com",
        "jortcas.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE2",
    "subject": "jortcas.com",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-24T18:19:29Z",
    "valid_from": "2026-10-26T18:19:30Z"
}
Domain age days
1
Apex age days
1
Tls age days
1
Tls valid days
89
Requests
4
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": -5,
        "malicious": false
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=utf-8"
}
Separate monitor record · 2026-10-30 04:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a18399-db51-7614-b360-52d6d1016e3b
score
0
malicious
false
result_at
2026-10-30T04:30:20Z
enriched_at
null
source_timestamps
{"urlscan_result_at":"2026-10-30 05:30:20","urlscan_enriched_at":null}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

Spamhaus DBL

Check recorded; verdict not retained

Open report

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
jortcas.com — Blank Capture Page with Domain Scan Result
ai_description
PhishDestroy records a blank capture of jortcas.com alongside a VirusTotal domain scan showing no detections across 92 engines.
ai_summary
The captured page for jortcas.com is blank, showing no visible content, branding, or interactive elements in the screenshot. Because the capture returned no rendered content, there is no page purpose or main interaction to describe beyond the empty result itself. VirusTotal's domain-scoped analysis of jortcas.com reported 0 detections out of 92 engines, with 0 malicious and 0 suspicious verdicts. No individual vendor flags were recorded in this result, so no specific engine names or verdicts apply to this case.
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-10-29 16:15:00
revision
3c512c3787baee6e2044fc8e1a4891601ad73c7f3e6f5163b2efa2954118de75
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: 15 fields

Mail configuration

SPF lookups
0

CAA records

Domain
jortcas.com

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

TLS connection

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

Ports

Open ports
  • 80
  • 443
  • 8080

DNS servers

Nameservers
  • IP address
    108.162.193.250
    Host
    zod.ns.cloudflare.com
  • IP address
    108.162.192.240
    Host
    wanda.ns.cloudflare.com
DNS zone
jortcas.com

Location

IP address
172.67.205.94
ASN
13335
Organization
Cloudflare, Inc.
City
Toronto
Country
CA

TLS certificate

Issuer
Let's Encrypt / YE2
Subject
jortcas.com

DNS records

A
  • 104.21.77.72
  • 172.67.205.94
NS
  • wanda.ns.cloudflare.com
  • zod.ns.cloudflare.com
SOA
Primary nameserver
wanda.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2418735375
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800
TXT
  • google-site-verification=3OMcVPdlCWefvS1OZ1Lv4FMpBjLABem_zTNChYH1ZUM

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
104.21.77.72
IP version
4

Registration record

Registrar
Dominet (HK) Limited
Registered
Updated
Expires
Status
  • ok https://icann.org/epp
Nameservers
  • wanda.ns.cloudflare.com
  • zod.ns.cloudflare.com
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "jortcas.com"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1",
        "TLSv1.1",
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443,
        8080
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "108.162.193.250",
            "host": "zod.ns.cloudflare.com"
        },
        {
            "ip": "108.162.192.240",
            "host": "wanda.ns.cloudflare.com"
        }
    ],
    "zone": "jortcas.com"
}
Location
{
    "ip": "172.67.205.94",
    "asn": "13335",
    "org": "Cloudflare, Inc.",
    "city": "Toronto",
    "country": "CA"
}
Ssl
{
    "issuer": "Let's Encrypt / YE2",
    "subject": "jortcas.com"
}
DNS records
{
    "A": [
        "104.21.77.72",
        "172.67.205.94"
    ],
    "NS": [
        "wanda.ns.cloudflare.com",
        "zod.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"wanda.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2418735375, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}",
    "TXT": [
        "google-site-verification=3OMcVPdlCWefvS1OZ1Lv4FMpBjLABem_zTNChYH1ZUM"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "104.21.77.72",
    "family": 4
}
Registration record
{
    "registrar": "Dominet (HK) Limited",
    "created": "2026-10-26T17:57:26Z",
    "updated": "2026-10-26T19:16:08Z",
    "expires": "2027-10-26T17:57:26Z",
    "status": [
        "ok https://icann.org/epp"
    ],
    "nameservers": [
        "wanda.ns.cloudflare.com",
        "zod.ns.cloudflare.com"
    ]
}

Explore

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

Checked, no match

Last checked

Stored Capture · 2 captures

Cloudflare Radar 1 / 2 Used in the analysis Source file SHA-256: e474a175f992442a69e502e42d7748076f7b37bd4715cf7c03ed2b7ff55231c3 SHA-256 of the prepared copy given to the model: cbd7964afd4f4fe91d257f62cb637efc6d375d5ecf52307768f6bc30d044a66e
SourceCloudflare Radar
Recorded
StateStored capture
Final URLhttps://jortcas.com/
Position1 / 2
Open capture Source Report Wayback Download
All capture links and hashes (2)
jortcas.com: under review, risk score 25/100 (medium); not yet listed by external security vendors.
Social preview card jortcas.com: under review, risk score 25/100 (medium); not yet listed by external security vendors. v 1c0919680a35

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context Canada172.67.205.94 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar Dominet (HK) HK(HK)
Abuse contact["domainabuse@service.aliyun.com", "6aacf85c31f44448s@"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for jortcas.com →
RegistrationCreated Oct 26, 2026 (3d · Brand New!) — Expires Oct 26, 2027
Registrant countryUnited States VirusTotal WHOIS
Registrant6aacf85c31f44448s@ VirusTotal WHOIS
WHOIS statusok
HTTP Status301 Moved Permanently
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 29, 2026
Submitted URLhttp://jortcas.com/
Favicon Hash
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 86 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Canada172.67.205.94
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
CanadaToronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 4

  • ns1.google.com
  • ns2.google.com
  • wanda.ns.cloudflare.com
  • zod.ns.cloudflare.com

SOA

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

Registrar abuse contact VirusTotal WHOIS

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-10-26 18:19:30
Valid until
2027-01-24 18:19:29
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintb95d5f58c6b08219e3ebd6b0945b8665e65840e75add2af6b3c17100c44200c7
Certificate names · 2 SANs
  • *.jortcas.com
  • jortcas.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 · 172.67.205.94rapiddns.io

Latest Classified Outcome 2026-10-30 11:00:21 UTC

The site was redirecting visitors elsewhere at the latest check.

Technical details
Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Stale Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-30 11:00:21 UTC
RDAP registration
Observed timeline last reachable: 2026-10-30 11:00:21 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.
Technologies · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response
Requested URL: http://jortcas.com/
Final URL: https://jortcas.com/
HTML body
5.0 KB
Compressed
2.4 KB
Links
0 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html; charset=utf-8
Server: cloudflare
Cache-Control: no-store, no-cache, must-revalidate, max-age=0
CF-Cache-Status: DYNAMIC
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 12
Cache-Control
no-store, no-cache, must-revalidate, max-age=0
CasT-Mode
default
cf-cache-status
DYNAMIC
CF-RAY
a5231c4b1ccbfe50-FRA
Connection
keep-alive
Content-Type
text/html; charset=utf-8
Date
Thu, 29 Oct 2026 15:11:02 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Pragma
no-cache
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=cekRYm64BqGEChkCaT74NiS0Jn6svKw08PIVef0Cx1uhPowLbh4YIS9wRdhYSdzMwQHl%2BzR2f8iOclCAZST5OPXBwh09a1s8Bf%2Fpod6LHjqvoS2D5B6z5oPkWyGh3Q%3D%3D"}]}
Server
cloudflare
Transfer-Encoding
chunked

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

Archived
Registration & observation details2

Availability observations

Last reachable observation
Estimate basis
Currently reachable

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

Captured network requests

Network requests: 4 SHA-256 hashes: 3 URLScan scan:

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

Open this scan on URLScan 01a18399-db51-7614-b360-52d6d1016e3b ↗

Stored observation history1

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

  1. Availability monitor · Recorded state

    redirected

    http_redirect

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_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:00:21.000000
    Evidence SHA-256
    194242862d64b894aed1f1905c6230750db5cfdd1cb48c2d65f0bc28808a6850
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-30 12:00:21
    Evidence reason
    redirect
  2. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:00:21.000000
    Evidence SHA-256
    194242862d64b894aed1f1905c6230750db5cfdd1cb48c2d65f0bc28808a6850
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-30 12:00:21
    Evidence reason
    redirect
  3. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:00:23.000000
    Evidence SHA-256
    da2513c236480670f5d39d56f9d77ef3940c57d980c6d465eceab089f78dea56
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-30 00:00:23
    Evidence reason
    redirect
  4. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:00:23.000000
    Evidence SHA-256
    da2513c236480670f5d39d56f9d77ef3940c57d980c6d465eceab089f78dea56
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-30 00:00:23
    Evidence reason
    redirect
  5. 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-10-29 16:12:44.341460
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

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

Recorded events: 6. 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
    jortcas.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · Cloudflare Radar Report · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 4 of 4
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • 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.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

2 entries
  1. Added to PhishDestroy

    jortcas.com

    View source
  2. VirusTotal

    0/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.

jortcas.com

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

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

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

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
More official reporting routes
FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

Template-based draft • optional AI wording assistance requires separate consent

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including jortcas.com)
  • Communications — emails, texts, phone numbers, usernames the scammer used

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

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

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

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

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

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

Check Any Domain

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

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

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

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

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

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

Request a correction or appeal How PhishDestroy works
Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/jortcas.com"
  title="PhishDestroy threat report for jortcas.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>