Skip to security report
Analytics Dashboard
Suspicious Domain — Listed on PhishDestroy
Stored PhishDestroy threat listing. Exercise extreme caution — do not enter credentials or personal information.
Domain security and threat intelligence
azulcargo.github.io favicon

azulcargo.github.io

In short

azulcargo.github.io is a Gmail impersonation page detected by PhishDestroy on 2026-10-25. Risk: high (68/100). Registrar: GitHub. Status: Content unavailable. Hosting: Fastly, Inc. Do not enter credentials or connect a wallet.

“Azul Cargo — Acompanhamento de Envios”

Review the evidence
Registrar
GitHub
Resolved IP
185.199.108.153
PhishDestroy assessment High
Availability Content unavailable Content was unavailable in the latest observation Observed HTTP probe
Risk signals
Stored PhishDestroy threat listing Automated brand label: Gmail Scam type: Impersonation
VirusTotal
—
Not recorded
OTX
0
community references
Cloudflare Radar
—
Not recorded
Page captures
3
open gallery
Domain age
—
Not recorded
Reports sent
—
No sent record
Oct 25, 2026 CDN
X Telegram API
Source evidence 5 sources

URLScan

Malicious · engine verdict · score 92

Open report
URLScanOriginal source recordObserved: 19 fields

Observed: · Retrieved:

Report ID

01a17121-74a8-758f-98cb-c9325cedda8f

Final URL

https://azulcargo.github.io/azul-cargo-app/

HTTP response

200

IP address

185.199.110.153

Reverse DNS (PTR)

cdn-185-199-110-153.github.com

Contacted domains

  • cdnjs.cloudflare.com

Contacted IP addresses

  • 104.17.25.14
  • 185.199.110.153

Autonomous systems (ASN)

  • 13335
  • 54113

Server countries

  • US

Document hash

65f1b3e8c084dd60142e9ba08aa542caf2fd364d793717bd845ce2842998ff71

JavaScript globals

  • Chart
  • DO_NOT_EXPORT_CODEPAGE
  • cptable
  • XLSX
  • make_xlsx_lib
  • parseBR
  • prazoDehon
  • diasUteis
  • estaAtrasado
  • statusEfetivo
  • badge
  • showToast
  • setBtnLoading
  • renderCards
  • renderTable
  • dateToSort
  • brToISO
  • applyFilters
  • exportExcel
  • carregarDados
  • renderCharts
  • DATA_URL
  • PER_PAGE
  • DATA
  • filtered
  • page
  • chartStatus
  • chartMes

TLS session and certificate

Subject alternative names
  • *.github.com
  • *.github.io
  • *.githubusercontent.com
  • github.com
  • github.io
  • githubusercontent.com
Cipher
AES_128_GCM
Issuer
YR1
Subject
*.github.io
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

110

Registered domain age, days

110

Certificate age, days

24

Certificate validity, days

89

Page requests

6

Provider verdicts

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

HTTP headers

Server
GitHub.com
Content-type
text/html; charset=utf-8
Strict-transport-security
max-age=31556952
Original source fields · JSON
Uuid
01a17121-74a8-758f-98cb-c9325cedda8f
Final url
https://azulcargo.github.io/azul-cargo-app/
Status
200
Ip
185.199.110.153
Ptr
cdn-185-199-110-153.github.com
Contacted domains
[
    "cdnjs.cloudflare.com"
]
Contacted IP addresses
[
    "104.17.25.14",
    "185.199.110.153"
]
Asns
[
    "13335",
    "54113"
]
Countries
[
    "US"
]
Document hash
65f1b3e8c084dd60142e9ba08aa542caf2fd364d793717bd845ce2842998ff71
Globals
[
    "Chart",
    "DO_NOT_EXPORT_CODEPAGE",
    "cptable",
    "XLSX",
    "make_xlsx_lib",
    "parseBR",
    "prazoDehon",
    "diasUteis",
    "estaAtrasado",
    "statusEfetivo",
    "badge",
    "showToast",
    "setBtnLoading",
    "renderCards",
    "renderTable",
    "dateToSort",
    "brToISO",
    "applyFilters",
    "exportExcel",
    "carregarDados",
    "renderCharts",
    "DATA_URL",
    "PER_PAGE",
    "DATA",
    "filtered",
    "page",
    "chartStatus",
    "chartMes"
]
Tls
{
    "san": [
        "*.github.com",
        "*.github.io",
        "*.githubusercontent.com",
        "github.com",
        "github.io",
        "githubusercontent.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YR1",
    "subject": "*.github.io",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-29T23:44:45Z",
    "valid_from": "2026-09-30T23:44:46Z"
}
Domain age days
110
Apex age days
110
Tls age days
24
Tls valid days
89
Requests
6
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 92,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "GitHub.com",
    "content-type": "text/html; charset=utf-8",
    "strict-transport-security": "max-age=31556952"
}
Separate monitor record · 2026-10-25 04:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a17121-74a8-758f-98cb-c9325cedda8f
score
0
malicious
false
result_at
2026-10-25T04:30:44Z
enriched_at
null
source_timestamps
{"urlscan_result_at":"2026-10-25 05:30:44","urlscan_enriched_at":null}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

68 / 100 · heuristic score · 1 brand references · 1 classifications

Open report
Separate monitor score · 10 / 100 · 2026-10-25T07:20:20Z

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

record_source
domain_monitor.dom_analysis
heuristic_score
10
analyzed_at
2026-10-25T07:20:20Z
source_timestamp
2026-10-25 08:20:20
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
VirusTotalOriginal source recordObserved: 12 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
0
Malicious
0
Suspicious
0
Undetected
92

Reputation score

0

Registrar

MarkMonitor Inc.

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    3600
    Type
    A
    Value
    185.199.110.153
  • TTL, seconds
    3600
    Type
    AAAA
    Value
    2606:50c0:8003::153
  • TTL, seconds
    3600
    Type
    CAA
    Value
    sectigo.com
  • TTL, seconds
    3600
    Type
    AAAA
    Value
    2606:50c0:8000::153
  • TTL, seconds
    3600
    Type
    CAA
    Value
    digicert.com
  • TTL, seconds
    3600
    Type
    A
    Value
    185.199.109.153
  • TTL, seconds
    3600
    Type
    AAAA
    Value
    2606:50c0:8001::153
  • TTL, seconds
    3600
    Type
    A
    Value
    185.199.108.153
  • TTL, seconds
    3600
    Type
    A
    Value
    185.199.111.153
  • TTL, seconds
    3600
    Type
    CAA
    Value
    sectigo.com
  • TTL, seconds
    3600
    Type
    CAA
    Value
    letsencrypt.org
  • TTL, seconds
    3600
    Type
    AAAA
    Value
    2606:50c0:8002::153
  • TTL, seconds
    3600
    Type
    CAA
    Value
    digicert.com
  • TTL, seconds
    3600
    Type
    CAA
    Value
    letsencrypt.org

DNS records observed

JARM fingerprint

29d3fd00029d29d00041d41d00041d6b5eefa2404a56c2ced79a0d16afe36c

Certificate

Subject alternative names
  • *.github.com
  • *.github.io
  • *.githubusercontent.com
  • github.com
  • github.io
  • githubusercontent.com
Issuer
Let's Encrypt / YR1
Serial
6a65e5d3279ba564a4de74eb5d64478dbb8
SHA-256
f2f9a159ce50a0a168b3eaeaf2fced5addd49ba38e2bf63248f057a139fc7856
Subject
*.github.io
Valid until
Valid from

Registration record

Registrar
MarkMonitor Inc.
Registrar IANA ID
292
Registrar URL
http://www.markmonitor.com
Registered
Updated
Expires
Status
  • clientDeleteProhibited
  • clientTransferProhibited
  • clientUpdateProhibited
Nameservers
  • dns1.p05.nsone.net
  • dns2.p05.nsone.net
  • dns3.p05.nsone.net
  • ns-1622.awsdns-10.co.uk
  • ns-692.awsdns-22.net
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 0,
    "malicious": 0,
    "suspicious": 0,
    "undetected": 92
}
Reputation
0
Registrar
MarkMonitor Inc.
Created
2013-03-08T19:41:10Z
Expires
2027-03-08T19:12:48Z
Updated
2026-08-12T09:08:04Z
First seen
2026-10-25T03:32:47Z
DNS records
[
    {
        "ttl": 3600,
        "type": "A",
        "value": "185.199.110.153"
    },
    {
        "ttl": 3600,
        "type": "AAAA",
        "value": "2606:50c0:8003::153"
    },
    {
        "ttl": 3600,
        "type": "CAA",
        "value": "sectigo.com"
    },
    {
        "ttl": 3600,
        "type": "AAAA",
        "value": "2606:50c0:8000::153"
    },
    {
        "ttl": 3600,
        "type": "CAA",
        "value": "digicert.com"
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "185.199.109.153"
    },
    {
        "ttl": 3600,
        "type": "AAAA",
        "value": "2606:50c0:8001::153"
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "185.199.108.153"
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "185.199.111.153"
    },
    {
        "ttl": 3600,
        "type": "CAA",
        "value": "sectigo.com"
    },
    {
        "ttl": 3600,
        "type": "CAA",
        "value": "letsencrypt.org"
    },
    {
        "ttl": 3600,
        "type": "AAAA",
        "value": "2606:50c0:8002::153"
    },
    {
        "ttl": 3600,
        "type": "CAA",
        "value": "digicert.com"
    },
    {
        "ttl": 3600,
        "type": "CAA",
        "value": "letsencrypt.org"
    }
]
Dns at
2026-10-25T03:32:47Z
Jarm
29d3fd00029d29d00041d41d00041d6b5eefa2404a56c2ced79a0d16afe36c
Certificate
{
    "san": [
        "*.github.com",
        "*.github.io",
        "*.githubusercontent.com",
        "github.com",
        "github.io",
        "githubusercontent.com"
    ],
    "issuer": "Let's Encrypt / YR1",
    "serial": "6a65e5d3279ba564a4de74eb5d64478dbb8",
    "sha256": "f2f9a159ce50a0a168b3eaeaf2fced5addd49ba38e2bf63248f057a139fc7856",
    "subject": "*.github.io",
    "valid_to": "2026-12-29T23:44:45Z",
    "valid_from": "2026-09-30T23:44:46Z"
}
Registration record
{
    "registrar": "MarkMonitor Inc.",
    "registrar_iana_id": "292",
    "registrar_url": "http://www.markmonitor.com",
    "created": "2013-03-08T19:12:48Z",
    "updated": "2025-02-25T20:53:31Z",
    "expires": "2027-03-08T00:00:00Z",
    "status": [
        "clientDeleteProhibited",
        "clientTransferProhibited",
        "clientUpdateProhibited"
    ],
    "nameservers": [
        "dns1.p05.nsone.net",
        "dns2.p05.nsone.net",
        "dns3.p05.nsone.net",
        "ns-1622.awsdns-10.co.uk",
        "ns-692.awsdns-22.net"
    ],
    "dnssec": "unsigned"
}
Website checksOriginal source recordRetrieved: 14 fields

Mail configuration

SPF lookups
0

CAA records

Count
6
Domain
azulcargo.github.io
Allowed issuers
  • sectigo.com
  • digicert.com
  • letsencrypt.org

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

TLS connection

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

Ports

Open ports
  • 80
  • 443

DNS servers

Nameservers
  • IP address
    198.51.44.69
    Host
    dns3.p05.nsone.net
  • IP address
    198.51.45.69
    Host
    dns4.p05.nsone.net
  • IP address
    205.251.197.59
    Host
    ns-1339.awsdns-39.org
  • IP address
    205.251.198.86
    Host
    ns-1622.awsdns-10.co.uk
  • IP address
    205.251.193.137
    Host
    ns-393.awsdns-49.com
  • IP address
    205.251.194.180
    Host
    ns-692.awsdns-22.net
  • IP address
    198.51.44.5
    Host
    dns1.p05.nsone.net
  • IP address
    198.51.45.5
    Host
    dns2.p05.nsone.net
DNS zone
github.io

Location

IP address
2606:50c0:8000::153
ASN
54113
Organization
Fastly, Inc.
City
San Francisco
Country
US

TLS certificate

Issuer
Let's Encrypt / YR1
Subject
*.github.io

DNS records

A
  • 185.199.108.153
  • 185.199.111.153
  • 185.199.109.153
  • 185.199.110.153
AAAA
  • 2606:50c0:8000::153
  • 2606:50c0:8003::153
  • 2606:50c0:8002::153
  • 2606:50c0:8001::153

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
default-src 'none'; style-src 'unsafe-inline'; img-src data:; connect-src 'self'
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
2606:50c0:8002::153
IP version
6

HTTP headers

Response headers
Server
GitHub.com
Content-type
text/html; charset=utf-8
Content-security-policy
default-src 'none'; style-src 'unsafe-inline'; img-src data:; connect-src 'self'
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "count": 6,
    "domain": "azulcargo.github.io",
    "issuers": [
        "sectigo.com",
        "digicert.com",
        "letsencrypt.org"
    ]
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_128_GCM_SHA256",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "198.51.44.69",
            "host": "dns3.p05.nsone.net"
        },
        {
            "ip": "198.51.45.69",
            "host": "dns4.p05.nsone.net"
        },
        {
            "ip": "205.251.197.59",
            "host": "ns-1339.awsdns-39.org"
        },
        {
            "ip": "205.251.198.86",
            "host": "ns-1622.awsdns-10.co.uk"
        },
        {
            "ip": "205.251.193.137",
            "host": "ns-393.awsdns-49.com"
        },
        {
            "ip": "205.251.194.180",
            "host": "ns-692.awsdns-22.net"
        },
        {
            "ip": "198.51.44.5",
            "host": "dns1.p05.nsone.net"
        },
        {
            "ip": "198.51.45.5",
            "host": "dns2.p05.nsone.net"
        }
    ],
    "zone": "github.io"
}
Location
{
    "ip": "2606:50c0:8000::153",
    "asn": "54113",
    "org": "Fastly, Inc.",
    "city": "San Francisco",
    "country": "US"
}
Ssl
{
    "issuer": "Let's Encrypt / YR1",
    "subject": "*.github.io"
}
DNS records
{
    "A": [
        "185.199.108.153",
        "185.199.111.153",
        "185.199.109.153",
        "185.199.110.153"
    ],
    "AAAA": [
        "2606:50c0:8000::153",
        "2606:50c0:8003::153",
        "2606:50c0:8002::153",
        "2606:50c0:8001::153"
    ]
}
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": "default-src 'none'; style-src 'unsafe-inline'; img-src data:; connect-src 'self'",
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "2606:50c0:8002::153",
    "family": 6
}
HTTP headers
{
    "headers": {
        "server": "GitHub.com",
        "content-type": "text/html; charset=utf-8",
        "content-security-policy": "default-src 'none'; style-src 'unsafe-inline'; img-src data:; connect-src 'self'"
    }
}

Questions about azulcargo.github.io

Is azulcargo.github.io legit?

No. PhishDestroy classifies azulcargo.github.io as a Gmail impersonation page (risk: high, 68/100); it was first detected on 2026-10-25. Treat the site as unsafe.

Is azulcargo.github.io safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on azulcargo.github.io. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used azulcargo.github.io?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 3 captures

Primary capture 1 / 3
SourcePrimary capture
Recorded
StateStored capture
HTTP statusNot recorded for this capture
Final URLNot recorded for this capture
Position1 / 3
Open capture Wayback Download
All capture links and hashes (3)

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context Fastly shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider GitHub
Abuse contactabuse@github.com
HTTP Status404 Not Found
Technical detailsProvenance & timestamps
First DetectedOct 25, 2026
DOM Analysisanalyzed Oct 25, 2026score 68/1001 brand signal
Submitted URLhttps://azulcargo.github.io/azul-cargo-app/
Favicon Hash
Observed page title
Azul Cargo — Acompanhamento de Envios
Automated brand references
Gmail
TLS Certificate
Issued by Let's Encrypt / YR1 · stored validity ends in 64 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
185.199.108.153
Network ASN
AS54113
Organization
Fastly, Inc.
Observed location
San Francisco, US
Server header
GitHub.com

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR1
Valid from
2026-09-30 23:44:46
Valid until
2026-12-29 23:44:45
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintf2f9a159ce50a0a168b3eaeaf2fced5addd49ba38e2bf63248f057a139fc7856
Certificate names · 6 SANs
  • *.github.com
  • *.github.io
  • *.githubusercontent.com
  • github.com
  • github.io
  • githubusercontent.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 · 185.199.108.153rapiddns.io

Latest Classified Outcome 2026-10-25 11:49:52 UTC

No phishing content was served at the latest check.

Technical details
Primary outcome Inactive reason: Http No Content 70% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Unreachable Content: Unknown DNS: Stale Registration: Unknown
Latest HTTP observation Inactive Http No Content 70% 2026-10-25 11:49:52 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-25 03:37:25 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
Stored Capture Evidence 1 snapshot

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

Archived HTTP response HTTP 200
Requested URL: https://azulcargo.github.io/azul-cargo-app/
Azul Cargo — Acompanhamento de Envios
Response
HTTP 200
HTML body
25.4 KB
Compressed
7.2 KB
Links
0 internal · 0 external
Selected response headers
Server: GitHub.com
Content-Type: text/html; charset=utf-8
Cache-Control: max-age=600
Content-Encoding: gzip
Security headers present
Strict-Transport-Security
HSTS: observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 24
Accept-Ranges
bytes
Access-Control-Allow-Origin
*
Age
0
Cache-Control
max-age=600
Connection
keep-alive
Content-Encoding
gzip
Content-Length
7489
Content-Type
text/html; charset=utf-8
Date
Sun, 25 Oct 2026 03:33:39 GMT
Etag
W/"6add5719-6587"
Expires
Sun, 25 Oct 2026 03:43:39 GMT
Last-Modified
Sun, 25 Oct 2026 01:10:49 GMT
Server
GitHub.com
Strict-Transport-Security
max-age=31556952
Vary
Accept-Encoding
Via
1.1 varnish
X-Cache
MISS
X-Cache-Hits
0
X-Fastly-Request-ID
aef2561aa7c965b24c69ee17c639b87c5c2b7249
x-github-edge-region
fra
X-GitHub-Request-Id
8BF0:1BF991:198FA67:19D53B1:6ADD7893
x-proxy-cache
MISS
X-Served-By
cache-ber1080038-BER
X-Timer
S1792899219.304883,VS0,VE131

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

Archived
Registration & observation details1

Availability observations

Last reachable observation

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

Check for cloaking

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

Page titles differ

http_other: raw=http_404; http=404; via=http_proxy; server=GitHub.com

Browser
Azul Cargo — Acompanhamento de Envios
Crawler
Site not found · GitHub Pages
azulcargo.github.io
Stored observation history2

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

    Unknown→inactive

    http_no_content

  2. Domain monitor · First collection record

    Reachable

All retained availability observations4

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_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 12:49:52.000000
    Evidence SHA-256
    50c6ef774fe147e331360930f59722e387905769125616ddae4b60bab9bbc5f7
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-25 12:49:52
    Evidence reason
    http_other
  2. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 12:49:52.000000
    Evidence SHA-256
    50c6ef774fe147e331360930f59722e387905769125616ddae4b60bab9bbc5f7
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-25 12:49:52
    Evidence reason
    http_other
  3. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 04:37:25.000000
    Evidence SHA-256
    728e40954cc5e037c2dcca3cdbf43c7374b30016fa403efd7e12e070351df7cd
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 04:37:25
    Evidence reason
  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-10-25 04:37:25.000000
    Evidence SHA-256
    728e40954cc5e037c2dcca3cdbf43c7374b30016fa403efd7e12e070351df7cd
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 04:37:25
    Evidence reason

Recorded activity

2 entries
  1. Added to PhishDestroy

    azulcargo.github.io

    View source
  2. URLScan

    Page captured

    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

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal ChainPatrol URLQuery SSL Labs Stored certificate dates valid 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?

3 evidence signal groups linked Content unavailable
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.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
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 →.

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.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

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 azulcargo.github.io)
  • Communications — emails, texts, phone numbers, usernames the scammer used

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

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

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

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

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

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

Check Any Domain

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

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

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

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

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

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

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

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/azulcargo.github.io"
  title="PhishDestroy threat report for azulcargo.github.io"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>