Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
PhishDestroy forensic analysis flagged this domain. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
fedexblack.com favicon

fedexblack.com

In short

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

“FedEx Black”

Review the evidence
Registrar
United StatesWix.com
Resolved IP
United States216.24.57.1Render · CDN
Registered
Oct 15, 2026
First observed
Oct 26, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Server error The latest stored response was inconclusive Observed HTTP probe
Risk signals
Spamhaus DBL: phishing domain Young domain: 16 days old Google Safe Browsing: threat flag recorded
VirusTotal
0 / 92
engine detections ·
Google Safe Browsing
Flagged
URLScan
Malicious
Page captures
11
open gallery
Domain age
16 days
registered 2026-10-15 according to WHOIS
Reports sent
1
view timeline
Oct 26, 2026 1 Report Sent CDN
X Telegram API

Questions about fedexblack.com

Is fedexblack.com legit?

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

Is fedexblack.com safe to connect a wallet?

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

What should I do if I used fedexblack.com?

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

Explore

Source evidenceVirusTotal 0 / 92 · Google Safe Browsing: flagged 8 sources

Cloudflare Radar

Malicious

Open report
Cloudflare RadarOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Report ID

c3e81388-4a0b-4049-8d53-dff309f2f1cf

Final URL

https://fedexblack.com/

HTTP response

200

Navigation history

  • URL
    https://fedexblack.com/
    Status
    200

DOM structure hash

cfbcf594d1b50f26fac0f7b5690411b8f6c4b78e43cfcbe97f54ad5518ed8a01

Document hash

252b4a6c7be18ae592aa9787edf5de97e03893c737f5528470786359a6e8cd45

Domain risk categories

  • New Domains
  • Security Risks
  • Phishing
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    fedexblack.com
    Type
    A
    Value
    216.24.57.1

DNSSEC valid

Yes

IP address

216.24.57.1

Verdict

Tags
  • phishing
Malicious
Yes
Categories
  • phishing

Registration record

Registrar
Wix.com Ltd.
Registered
Updated
Expires
Nameservers
  • ns8.wixdns.net
  • ns9.wixdns.net
Original source fields · JSON
Uuid
c3e81388-4a0b-4049-8d53-dff309f2f1cf
Final url
https://fedexblack.com/
Status
200
History
[
    {
        "url": "https://fedexblack.com/",
        "status": 200
    }
]
DOM structure hash
cfbcf594d1b50f26fac0f7b5690411b8f6c4b78e43cfcbe97f54ad5518ed8a01
Document hash
252b4a6c7be18ae592aa9787edf5de97e03893c737f5528470786359a6e8cd45
Domain risks
[
    "New Domains",
    "Security Risks",
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "fedexblack.com",
        "type": "A",
        "value": "216.24.57.1"
    }
]
Dnssec valid
true
Ip
216.24.57.1
Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
Registration record
{
    "registrar": "Wix.com Ltd.",
    "created": "2026-10-15T05:37:24Z",
    "updated": "2026-10-15T05:37:35Z",
    "expires": "2028-10-15T05:37:24Z",
    "nameservers": [
        "ns8.wixdns.net",
        "ns9.wixdns.net"
    ]
}

Google Safe Browsing

Threat flag recorded

Open report

Spamhaus DBL

phishing domain

URLScan

Malicious

SHA-256 3672ec7fb51f894ba6b287bd761fd8d6556ce657566499eecf1c711845361b6a

Open report
URLScanOriginal source recordObserved: 23 fields

Observed: · Retrieved:

Report ID

01a179f6-fba4-75d5-ac62-7445aa79dbfb

Final URL

https://fedexblack.com/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://fedexblack.com/
    From
    http://fedexblack.com/
    Status
    307

IP address

216.24.57.1

Reverse DNS (PTR)

ip-216-24-57-1.ingress.render.com

Contacted domains

  • media.base44.com

Contacted IP addresses

  • 3.167.69.65
  • 216.24.57.1

Autonomous systems (ASN)

  • 16509
  • 397273

Server countries

  • US

Document hash

252b4a6c7be18ae592aa9787edf5de97e03893c737f5528470786359a6e8cd45

Script hashes

  • 4ceddaa702ee1d1f032cdd35e846592d7e2636c767a3c6819cdec4121005dd38

JavaScript globals

  • __reactRouterVersion
  • base44SharedInstances

Browser storage keys

  • base44_analytics_session_id

TLS session and certificate

Subject alternative names
  • fedexblack.com
Cipher
AES_128_GCM
Issuer
WE1
Subject
fedexblack.com
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

10

Registered domain age, days

10

Certificate age, days

11

Certificate validity, days

90

Page requests

19

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
100
Malicious
Yes
Overall verdict
Tags
  • phishing
Score
100
Brands
  • fedex
Malicious
Yes
Categories
  • phishing
URLScan verdict
Tags
  • phishing
Score
100
Brands
  • Fedex
Malicious
Yes
Categories
  • phishing

HTTP headers

Server
cloudflare
Content-type
text/html; charset=utf-8
Strict-transport-security
max-age=31536000
X-frame-options
DENY
X-content-type-options
nosniff
Referrer-policy
strict-origin-when-cross-origin
Original source fields · JSON
Uuid
01a179f6-fba4-75d5-ac62-7445aa79dbfb
Final url
https://fedexblack.com/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://fedexblack.com/",
        "from": "http://fedexblack.com/",
        "status": 307
    }
]
Ip
216.24.57.1
Ptr
ip-216-24-57-1.ingress.render.com
Contacted domains
[
    "media.base44.com"
]
Contacted IP addresses
[
    "3.167.69.65",
    "216.24.57.1"
]
Asns
[
    "16509",
    "397273"
]
Countries
[
    "US"
]
Document hash
252b4a6c7be18ae592aa9787edf5de97e03893c737f5528470786359a6e8cd45
Script hashes
[
    "4ceddaa702ee1d1f032cdd35e846592d7e2636c767a3c6819cdec4121005dd38"
]
Globals
[
    "__reactRouterVersion",
    "base44SharedInstances"
]
Storage keys
[
    "base44_analytics_session_id"
]
Tls
{
    "san": [
        "fedexblack.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WE1",
    "subject": "fedexblack.com",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-13T05:39:03Z",
    "valid_from": "2026-10-15T04:39:04Z"
}
Domain age days
10
Apex age days
10
Tls age days
11
Tls valid days
90
Requests
19
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 100,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "fedex"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "Fedex"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=utf-8",
    "strict-transport-security": "max-age=31536000",
    "x-frame-options": "DENY",
    "x-content-type-options": "nosniff",
    "referrer-policy": "strict-origin-when-cross-origin"
}
Separate monitor record · date not recorded

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

record_source
domain_monitor.urlscan
uuid
01a179eb-5655-7213-890f-efd73fe4f52a
score
null
malicious
null
result_at
null
enriched_at
2026-10-27T09:19:29Z
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":"2026-10-27 10:19:29"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

VirusTotal

0 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
53
Malicious
0
Suspicious
0
Undetected
39

Reputation score

0

Registrar

Wix.Com Ltd.

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    3600
    Type
    SOA
    Responsible mailbox
    support.wix.com
    Value
    ns8.wixdns.net
  • TTL, seconds
    21600
    Type
    NS
    Value
    ns9.wixdns.net
  • TTL, seconds
    21600
    Type
    NS
    Value
    ns8.wixdns.net
  • TTL, seconds
    600
    Type
    A
    Value
    216.24.57.1

DNS records observed

JARM fingerprint

27d27d27d00027d00042d43d00041df04c41293ba84f6efe3a613b22f983e6

Certificate

Subject alternative names
  • fedexblack.com
Issuer
Google Trust Services / WE1
Serial
af11a042fc33710a0e67b07c4b68201a
SHA-256
1cba912af435ea4046771a97bfc6719b4c8e78634b84865480e925121cf48a15
Subject
fedexblack.com
Valid until
Valid from

Registration record

Registrar
Wix.Com Ltd.
Registrar IANA ID
3817
Registrar URL
http://www.wix.com
Registered
Updated
Expires
Status
  • clientTransferProhibited
  • clientUpdateProhibited
Nameservers
  • ns8.wixdns.net
  • ns9.wixdns.net
DNSSEC
signedDelegation

Registry data (RDAP)

Status
  • client transfer prohibited
  • client update prohibited
Registry events
Last changed
Registration
Registrar expiration
Last RDAP database update
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 53,
    "malicious": 0,
    "suspicious": 0,
    "undetected": 39
}
Reputation
0
Registrar
Wix.Com Ltd.
Created
2026-10-15T05:37:24Z
Expires
2028-10-15T05:37:24Z
Updated
2026-10-15T05:37:35Z
First seen
2026-10-15T12:10:52Z
DNS records
[
    {
        "ttl": 3600,
        "type": "SOA",
        "rname": "support.wix.com",
        "value": "ns8.wixdns.net"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns9.wixdns.net"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns8.wixdns.net"
    },
    {
        "ttl": 600,
        "type": "A",
        "value": "216.24.57.1"
    }
]
Dns at
2026-10-24T23:04:22Z
Jarm
27d27d27d00027d00042d43d00041df04c41293ba84f6efe3a613b22f983e6
Certificate
{
    "san": [
        "fedexblack.com"
    ],
    "issuer": "Google Trust Services / WE1",
    "serial": "af11a042fc33710a0e67b07c4b68201a",
    "sha256": "1cba912af435ea4046771a97bfc6719b4c8e78634b84865480e925121cf48a15",
    "subject": "fedexblack.com",
    "valid_to": "2027-01-13T05:39:03Z",
    "valid_from": "2026-10-15T04:39:04Z"
}
Registration record
{
    "registrar": "Wix.Com Ltd.",
    "registrar_iana_id": "3817",
    "registrar_url": "http://www.wix.com",
    "created": "2026-10-15T05:37:24Z",
    "updated": "2026-10-15T05:37:25Z",
    "expires": "2028-10-15T05:37:24Z",
    "status": [
        "clientTransferProhibited",
        "clientUpdateProhibited"
    ],
    "nameservers": [
        "ns8.wixdns.net",
        "ns9.wixdns.net"
    ],
    "dnssec": "signedDelegation"
}
Registry data
{
    "status": [
        "client transfer prohibited",
        "client update prohibited"
    ],
    "events": {
        "last changed": "2026-10-15T22:12:21Z",
        "registration": "2026-10-15T05:37:24Z",
        "registrar expiration": "2028-10-15T05:37:24Z",
        "last update of RDAP database": "2026-10-15T22:12:21Z"
    }
}
Separate source record · 0 malicious + 0 suspicious / 92 · 2026-10-24 23:03:20 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-24T23:03:20Z
fetched_at
2026-10-26T20:43:43Z
stats
{"timeout":0,"harmless":53,"malicious":0,"suspicious":0,"undetected":39}

OTX

no community references

Open report

PhishDestroy DOM

78 / 100 · heuristic score · 1 brand reference · 1 classification

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

Mail configuration

DKIM
  • s1
  • s2
DKIM key size, bits
2048
SPF lookups
0

CAA records

Domain
fedexblack.com

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Trackers

Requests
20

DNS servers

Nameservers
  • IP address
    216.239.34.101
    Host
    ns9.wixdns.net
  • IP address
    216.239.32.101
    Host
    ns8.wixdns.net
DNS zone
fedexblack.com

DNS records

A
  • 216.24.57.1
NS
  • ns8.wixdns.net
  • ns9.wixdns.net
SOA
Primary nameserver
ns8.wixdns.net
Hostmaster
support.wix.com
Serial
2026101505
Refresh, seconds
10800
Retry, seconds
3600
Expiry, seconds
1209600
Minimum TTL, seconds
3600

Technology stack

Technologies
  • HSTS
  • Cloudflare
  • PWA
  • HTTP/3
Original source fields · JSON
Mail configuration
{
    "dkim": [
        "s1",
        "s2"
    ],
    "dkim_bits": 2048,
    "spf_lookups": 0
}
Caa records
{
    "domain": "fedexblack.com"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Trackers
{
    "requests": 20
}
Dns server
{
    "ns": [
        {
            "ip": "216.239.34.101",
            "host": "ns9.wixdns.net"
        },
        {
            "ip": "216.239.32.101",
            "host": "ns8.wixdns.net"
        }
    ],
    "zone": "fedexblack.com"
}
DNS records
{
    "A": [
        "216.24.57.1"
    ],
    "NS": [
        "ns8.wixdns.net",
        "ns9.wixdns.net"
    ],
    "SOA": "{\"nsname\": \"ns8.wixdns.net\", \"hostmaster\": \"support.wix.com\", \"serial\": 2026101505, \"refresh\": 10800, \"retry\": 3600, \"expire\": 1209600, \"minttl\": 3600}"
}
Tech stack
{
    "technologies": [
        "HSTS",
        "Cloudflare",
        "PWA",
        "HTTP/3"
    ]
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Security threats New Domains Phishing Phishing Security Risks
View full Cloudflare Radar report
Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 11 captures

Primary capture 1 / 11
SourcePrimary capture
Recorded
StateStored capture
Position1 / 11
Open capture Wayback Download
All capture links and hashes (11)
fedexblack.com: FedEx impersonation — Flagged by Google Safe Browsing, Spamhaus DBL, 18/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical).
Social preview card fedexblack.com: FedEx impersonation — Flagged by Google Safe Browsing, Spamhaus DBL, 18/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical). v 60d054325bdc

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Fedex report ↗
Google Safe Browsing Flagged Social engineering checked Oct 30, 2026
IP Context United States216.24.57.1 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar Wix.com US(US)
Abuse contactdomain-abuse@wix.com, abuse@render.com, fedexblack.com@wix-domains.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for fedexblack.com →
Hosting abuse contact abuse@render.com Render · AS397273
RegistrationCreated Oct 15, 2026 (16d · Very New!) — Expires Oct 15, 2028
Registrant countryUnited States VirusTotal WHOIS
Registrant1f8f4166599d23eebad3e17ff925af42s@wix-domains.com VirusTotal WHOIS
Time to First Unavailability 4 days
What we count Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedOct 26, 2026
DOM Analysisanalyzed Oct 26, 2026score 78/1001 brand signal
Submitted URLhttp://fedexblack.com/
Favicon Hash
Case ID
Observed page title
FedEx Black
Automated brand references
Fedex
TLS Certificate
Issued by Google Trust Services / WE1 · stored validity ends in 73 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
United States216.24.57.1
Network ASN
AS397273
AS name
RENDER - Render, US
Organization
Render
Observed location
United StatesSan Francisco, US
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • ns8.wixdns.net
  • ns9.wixdns.net

SOA

  • nsname: ns8.wixdns.net
  • hostmaster: support.wix.com
  • serial: 2026101505
  • refresh: 10800
  • retry: 3600
  • expire: 1209600
  • minttl: 3600

Registrar abuse contact VirusTotal WHOIS

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-10-15 04:39:04
Valid until
2027-01-13 05:39:03
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint1cba912af435ea4046771a97bfc6719b4c8e78634b84865480e925121cf48a15
Certificate names · 1 SAN
  • fedexblack.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 · 216.24.57.1rapiddns.io
Threat Intel Cross-Reference · source references
ScamAdviser Public lookup
A public ScamAdviser lookup is available. Review its current score and warnings at the source; the existence of a lookup page is not itself a malicious verdict.
View on ScamAdviser
Fetched directly from the site by PhishDestroy · cached up to 24 h
Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of fedexblack.com · checked Oct 26, 2026

99
Good
Performance
FCP
1.65 s
First Contentful Paint
LCP
1.73 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
2.89 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
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: http://fedexblack.com/
Final URL: https://fedexblack.com/
FedEx Black
Response
HTTP 200
HTML body
2.9 KB
Compressed
1.2 KB
Links
0 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html; charset=utf-8
CF-Cache-Status: DYNAMIC
Server: cloudflare
Content-Encoding: gzip
Security headers present
Strict-Transport-SecurityX-Frame-OptionsX-Content-Type-OptionsReferrer-Policy
HSTS: observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Favicon fingerprint: d1b15b3bdbd7c234ac6916cff801292d937ae05a18fd36a38037277192cf2df4
Saved response-header values · 18
alt-svc
h3=":443"; ma=86400
cf-cache-status
DYNAMIC
CF-RAY
a50c488e0f4265c7-FRA
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Mon, 26 Oct 2026 20:41:43 GMT
Referrer-Policy
strict-origin-when-cross-origin
rndr-id
2e4f8eab-b35c-4649
Server
cloudflare
Strict-Transport-Security
max-age=31536000
Transfer-Encoding
chunked
Vary
Accept-Encoding
Via
1.1 Caddy
X-Content-Type-Options
nosniff
X-Frame-Options
DENY
x-render-origin-server
uvicorn
x-request-id
65f5c832-97ee-4d3f-ba28-5d808ea30602

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

Archived
Registration & observation details2

Availability observations

Last reachable observation
Last content observation

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: 19 SHA-256 hashes: 19 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 01:56 UTC.

Open this scan on URLScan 01a179f6-fba4-75d5-ac62-7445aa79dbfb ↗

Stored observation history7

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

  1. Domain monitor · Recorded state

    Reachable→Unavailable

  2. Domain monitor · Recorded state

    Unavailable→Reachable

  3. Domain monitor · Recorded state

    Reachable→Unavailable

  4. Availability monitor · Recorded state

    live_content

    content_served

  5. Availability monitor · Recorded state

    live_content

    content_served

Earlier observations 2
  1. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

  2. Domain monitor · First collection record

    Reachable

All retained availability observations26

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_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 11:20:09.112163
    Evidence SHA-256
    b5c6551e799cfe4d3cb298004536f14652a7bd27158039d9a8bde93b0611124a
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 11:20:09.112163
    Evidence reason
  2. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 00:54:34.000000
    Evidence SHA-256
    d184a206d28e79778f1e252ff3b9eea4d291418d6f25e7bf5b5eb6c8f001467b
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 00:54:34
    Evidence reason
    unavailable
  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-10-31 00:54:34.000000
    Evidence SHA-256
    d184a206d28e79778f1e252ff3b9eea4d291418d6f25e7bf5b5eb6c8f001467b
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 00:54:34
    Evidence reason
    unavailable
  4. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-30 13:06:07.000000
    Evidence SHA-256
    ac8bcd6be71457e6acab826b51afe9b5f550b28002ef46edf157a1f38c7635e5
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 13:06:07
    Evidence reason
    unavailable
  5. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 13:06:07.000000
    Evidence SHA-256
    ac8bcd6be71457e6acab826b51afe9b5f550b28002ef46edf157a1f38c7635e5
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 13:06:07
    Evidence reason
    unavailable
  6. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-30 05:03:05.462458
    Evidence SHA-256
    bbc8a7612fad967fe6394ef6e3533c42adb354b0403e4f596ca1b553348f1852
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 05:03:05.462458
    Evidence reason
  7. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-30 01:04:24.000000
    Evidence SHA-256
    9c8a99c6ccaa2f9d0c060edfb1a8b2bbbdad0ad9956137721a53ec8316f74797
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 01:04:24
    Evidence reason
    unavailable
  8. 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-30 01:04:24.000000
    Evidence SHA-256
    9c8a99c6ccaa2f9d0c060edfb1a8b2bbbdad0ad9956137721a53ec8316f74797
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 01:04:24
    Evidence reason
    unavailable
  9. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-29 13:02:08.000000
    Evidence SHA-256
    9f9de5e8a6870fc36b706a2a793dcdae7ac0a579327b1af2196da18a15cd6c3a
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-29 13:02:08
    Evidence reason
    unavailable
  10. 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-29 13:02:08.000000
    Evidence SHA-256
    9f9de5e8a6870fc36b706a2a793dcdae7ac0a579327b1af2196da18a15cd6c3a
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-29 13:02:08
    Evidence reason
    unavailable
  11. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-29 05:03:05.313035
    Evidence SHA-256
    e8d7330e223cce20a4540e7f3ccd4cc0f3b8c1f41fa08898b82c337408eae933
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-29 05:03:05.313035
    Evidence reason
  12. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    timeout
    DNS response code
    TIMEOUT
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 04:48:04.000000
    Evidence SHA-256
    bac10e49bf4e005545ea175562d3ce5b5a5559725b3fb5dc549de68848d6f5b8
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 04:48:04
    Evidence reason
    alive_content
  13. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 04:48:04.000000
    Evidence SHA-256
    bac10e49bf4e005545ea175562d3ce5b5a5559725b3fb5dc549de68848d6f5b8
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 04:48:04
    Evidence reason
    alive_content
  14. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 00:03:18.000000
    Evidence SHA-256
    ad18c5fd5ea80740c579c2c3e03173633e8e71b0876e6eebc102f4303bc5dc8f
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 00:03:18
    Evidence reason
    alive_content
  15. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 00:03:18.000000
    Evidence SHA-256
    ad18c5fd5ea80740c579c2c3e03173633e8e71b0876e6eebc102f4303bc5dc8f
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 00:03:18
    Evidence reason
    alive_content
  16. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 12:03:51.000000
    Evidence SHA-256
    61cb7941fe07ea4fabefc0164f781edc22551ef8c25c0f5817ffe8ab53373b3c
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 12:03:51
    Evidence reason
    alive_content
  17. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 12:03:51.000000
    Evidence SHA-256
    61cb7941fe07ea4fabefc0164f781edc22551ef8c25c0f5817ffe8ab53373b3c
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 12:03:51
    Evidence reason
    alive_content
  18. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 00:04:20.000000
    Evidence SHA-256
    81b29d386168f567a4162e1dfbf381a589132048625525c9159d6e73dd095524
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 00:04:20
    Evidence reason
    alive_content
  19. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 00:04:20.000000
    Evidence SHA-256
    81b29d386168f567a4162e1dfbf381a589132048625525c9159d6e73dd095524
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 00:04:20
    Evidence reason
    alive_content
  20. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 21:55:27.687577
    Evidence SHA-256
    3b371534c09b43375628c37562ee3965233ba7e96fa11caf6cc0bea2ef95474d
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-27 21:55:27.687577
    Evidence reason
  21. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:04:25.000000
    Evidence SHA-256
    c2397b7f222895be293f914562d158c459eb5cc171ac01fb10dd9455625cfea5
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 12:04:25
    Evidence reason
    alive_content
  22. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:04:25.000000
    Evidence SHA-256
    c2397b7f222895be293f914562d158c459eb5cc171ac01fb10dd9455625cfea5
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 12:04:25
    Evidence reason
    alive_content
  23. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 21:55:25.115664
    Evidence SHA-256
    33967275c5aca65ff8759ac33f7fc38457f8a476387a2c5fe76e3a7af6bc5b16
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-26 21:55:25.115664
    Evidence reason
  24. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 21:47:54.000000
    Evidence SHA-256
    dd37bf94f01656b9096303b6f8561806c0322e70b098c84a8c5ff3978345afcb
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-26 21:47:54
    Evidence reason
  25. 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-26 21:47:54.000000
    Evidence SHA-256
    dd37bf94f01656b9096303b6f8561806c0322e70b098c84a8c5ff3978345afcb
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-26 21:47:54
    Evidence reason
  26. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 10:06:24.862259
    Evidence SHA-256
    8895fe784317ce956fd87b3c03d7dee28c93bf969fb14b515b4f932e1c762121
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 10:06:24.862259
    Evidence reason

Threat Response Pipeline

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

Recorded events: 18. 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
    fedexblack.com detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · Google Safe Browsing · Cloudflare Radar: Malicious · Automated brand label: FedEx · Forensic Evidence Collected · Technical Analysis Recorded · Content Observed Unavailable · Site Came Back Online · Content Observed Unavailable Recorded: 13 of 13
  • Spamhaus DBL
    Spamhaus DBL recorded: phishing domain
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan classified the page as malicious · Score: 100
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • Google Safe Browsing
    Listed as unsafe by Google Safe Browsing (Google Transparency Report)
  • Cloudflare Radar: Malicious
    Cloudflare Radar classified this domain as Security threats, New Domains, Phishing, Security Risks
  • Automated brand label: FedEx
    Collector label, not confirmed by a page check.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, URLQuery, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
  • Content Observed Unavailable
    Monitoring recorded an unavailable response; the cause was not independently established.
  • Site Came Back Online
    The domain is responding again; monitoring resumed
  • Content Observed Unavailable
    Monitoring recorded an unavailable response (HTTP 200); the cause was not independently established.
Notification RecordsSent Report Recorded Recorded: 1 of 1
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: Wix.com Ltd.. Abuse contacts: 1.
    • domain-abuse@wix.com
Publication & AvailabilityDestroyList Published · Content Observed Unavailable · Time to First Unavailability Recorded: 3 of 3
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Content Observed Unavailable
    The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
  • Time to First Unavailability
    Hours from detection to the first unavailable observation: 98

Recorded activity

6 entries
  1. Google Safe Browsing

    Threat flag recorded

    View source
  2. Abuse report sent

    PD-20261026-6D9564 · Receipt 83529

    domain-abuse@wix.com
  3. URLScan

    Page captured

    View source
  4. Wayback Machine

    Page archived

    View source
  5. Added to PhishDestroy

    fedexblack.com

    View source
  6. 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.

fedexblack.com

Evidence & External Reports

Security Analysis
URLScan Malicious VirusTotal ChainPatrol URLQuery Report stored Google SB Flagged SSL Labs Stored certificate dates valid CF Radar Malicious WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261026-6D9564 Recipient: domain-abuse@wix.com
PDF notice generated Notice text archived (859 characters)
Abuse notice text as sent to the provider 
AUP & Terms of Service Violations:
Acceptable Use Policy: Active phishing operations targeting internet users directly violate standard AUP provisions prohibiting fraud and deceptive practices.
Terms of Service: Material breach of service terms regarding malicious use, providing contractual justification for immediate suspension.
Applicable Legal Framework (US):
18 U.S.C. § 1343 - Wire Fraud
18 U.S.C. § 1030 - Computer Fraud and Abuse Act (CFAA)
15 U.S.C. § 45 - FTC Act (Deceptive Practices)
Federal laws prohibit wire fraud, computer fraud, and deceptive business practices.
Investigation Notice: We fully respect your internal investigation processes and discretion. Prompt remediation protects innocent users while mitigating regulatory compliance scrutiny, legal liability, and brand reputation risks associated with ongoing malicious infrastructure.
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 1 stored notification records Server error
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 fedexblack.com)
  • Communications — emails, texts, phone numbers, usernames the scammer used

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

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

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

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

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

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

Check Any Domain

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

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

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

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

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

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

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

Embed This Report

Share this threat intelligence on your website or blog

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