VirusTotal
3 / 92 engine detections
Open reportfedexdelivery247.live is a FedEx impersonation page detected by PhishDestroy on 2026-10-23. Risk: high (69/100). Registrar: Spaceship. Status: Last known active. Hosting: Namecheap, Inc. PhishDestroy sent 1 abuse report. VirusTotal: 3/92 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.
“FedEx® Tracking”
3 / 92 engine detections
Open reportDBL_PHISH
Scan report
Open reportno community references
Open reportScan report
Open reportNo threat flag
Open reportPage capture
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
PhishDestroy’s intake system flagged fedexdelivery247.live on 2026-10-23 after a fresh URLScan capture returned a malicious verdict and an AI model assigned a high phishing confidence. The recorded page title reads “FedEx® Tracking” and the captured excerpt shows a form prompting visitors to “Enter your tracking number to view details.” An HTTP 200 response was recorded on the same date, confirming the site was reachable at that time.
Typical FedEx‑tracking phishing sites copy the carrier’s branding and present a tracking‑number field to harvest login credentials or personal data. Victims who submit information may have their FedEx account passwords or related details compromised, often leading to further credential‑stealing attacks.
URLScan captured on 2026-10-23 labeled the domain malicious with a 100 % phishing score and identified the FedEx brand. Cloudflare Radar on the same day gave an identical malicious phishing verdict. VirusTotal analysis on 2026-10-23 reported three detections across 92 engines: one malicious and two suspicious, from AlphaMountain.ai, Gridinsoft and LevelBlue. Google Safe Browsing checked on 2026-10-23 did not flag the URL. OTX showed zero pulses on the same date. External blocklists contained no entries, while PhishDestroy’s internal list marks the domain as malicious.
The domain was registered on 2026-10-16 through Spaceship, Inc., giving it a seven‑day age at first sight. At the time of observation it pointed to the IP address 66.29.148.25, which was associated with Namecheap, Inc. in the United States, and presented a Let’s Encrypt TLS 1.3 certificate valid until 2027-01-14. Nameservers were launch1.spaceship.net and launch2.spaceship.net, and MX records referenced mx1.spacemail.com and mx2.spacemail.com.
Anyone who entered a tracking number or credentials should change their FedEx password immediately and review recent account activity. Organizations should block the domain at the firewall, monitor logs for connections to 66.29.148.25, and consider notifying FedEx support of the phishing attempt. No cryptocurrency‑related remediation is required.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 01a1699a-c41d-74ba-81ff-3b2f84cb7f86 |
|---|---|
| Final url | https://fedexdelivery247.live/ |
| Status | 200 |
| Ip | 66.29.148.25 |
| Ptr | server5-2.shared.spaceship.host |
| Contacted IP addresses | [
"66.29.148.25"
] |
| Asns | [
"22612"
] |
| Countries | [
"US"
] |
| Document hash | d6c3b6b13e8d825f79a065b5e1e59c06f7aa4605683bc7d79b522cf6d4bf8012 |
| Tls | {
"san": [
"fedexdelivery247.live",
"www.fedexdelivery247.live"
],
"cipher": "AES_256_GCM",
"issuer": "YR1",
"subject": "fedexdelivery247.live",
"protocol": "TLS 1.3",
"valid_to": "2027-01-14T13:06:41Z",
"valid_from": "2026-10-16T13:06:42Z"
} |
| Domain age days | 7 |
| Apex age days | 7 |
| Tls age days | 7 |
| Tls valid days | 89 |
| Requests | 5 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 98,
"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": "LiteSpeed",
"content-type": "text/html; charset=UTF-8",
"x-powered-by": "PHP/8.2.35"
} |
Observed: · Retrieved:
| Uuid | 4b0d8d5c-9370-4afb-9eb6-320e1fb21042 |
|---|---|
| Final url | https://fedexdelivery247.live/ |
| Status | 200 |
| History | [
{
"url": "https://fedexdelivery247.live/",
"status": 200
}
] |
| DOM structure hash | cb566f3bb77f9e2083e556e429ad3727e5281373d42b24b207edce6573d72d95 |
| Document hash | d6c3b6b13e8d825f79a065b5e1e59c06f7aa4605683bc7d79b522cf6d4bf8012 |
| Phishing v2 | [
"phishing"
] |
| Domain risks | [
"Phishing",
"Security threats",
"Newly Seen Domains",
"Security Risks",
"New Domains",
"CIPA Filter",
"CIPA"
] |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "fedexdelivery247.live",
"type": "A",
"value": "66.29.148.25"
}
] |
| Dnssec valid | true |
| Ip | 66.29.148.25 |
| Verdict | {
"tags": [
"phishing"
],
"malicious": true,
"categories": [
"phishing"
]
} |
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 53,
"malicious": 1,
"suspicious": 2,
"undetected": 36
} |
|---|---|
| Vendor labels | {
"LevelBlue": "phishing",
"Gridinsoft": "suspicious",
"alphaMountain.ai": "suspicious"
} |
| Reputation | 0 |
| Categories | {
"alphaMountain.ai": "Suspicious (alphaMountain.ai)"
} |
| First seen | 2026-10-16T14:14:11Z |
| DNS records | [
{
"ttl": 1800,
"type": "SOA",
"rname": "support.spaceship.com",
"value": "launch1.spaceship.net"
},
{
"ttl": 300,
"type": "A",
"value": "66.29.148.25"
},
{
"ttl": 300,
"type": "MX",
"value": "mx2.spacemail.com",
"priority": 0
},
{
"ttl": 1800,
"type": "TXT",
"value": "v=spf1 include:spf.shared.spaceship.host include:spf.spacemail.com ~all"
},
{
"ttl": 421,
"type": "NS",
"value": "launch2.spaceship.net"
},
{
"ttl": 300,
"type": "MX",
"value": "mx1.spacemail.com",
"priority": 0
},
{
"ttl": 421,
"type": "NS",
"value": "launch1.spaceship.net"
}
] |
| Dns at | 2026-10-17T18:06:53Z |
| Jarm | 3fd3fd15d3fd3fd00042d42d000000038eaaf490bec8dc33757f165ce01762 |
| Certificate | {
"san": [
"fedexdelivery247.live",
"www.fedexdelivery247.live"
],
"issuer": "Let's Encrypt / YR1",
"serial": "5bdd0bc84aa29f63db626ee5ef45e2ec224",
"sha256": "e3a1b1c395747db9f98ba584e1528107807945d45aec9d607691e2f9cda28ee1",
"subject": "fedexdelivery247.live",
"valid_to": "2027-01-14T13:06:41Z",
"valid_from": "2026-10-16T13:06:42Z"
} |
| Registry data | {
"status": [
"client transfer prohibited"
],
"events": {
"last changed": "2026-10-16T13:57:40Z",
"registration": "2026-10-16T13:57:39Z",
"registrar expiration": "2027-10-16T13:57:39Z",
"last update of RDAP database": "2026-10-16T14:14:01Z"
},
"registrar": "Spaceship, Inc.",
"registrar_iana_id": "3862"
} |
| Mail configuration | {
"mx": [
"mx2.spacemail.com",
"mx1.spacemail.com"
],
"spf": "v=spf1 include:spf.shared.spaceship.host include:spf.spacemail.com ~all",
"spf_lookups": 4
} |
|---|---|
| Caa records | {
"domain": "fedexdelivery247.live"
} |
| Protective DNS results | {
"resolvers": 12,
"blocked_by": [
"CloudFlare Family"
],
"blocked_count": 1
} |
| Web archive observations | {
"last": "2026-10-16T23:23:17Z",
"first": "2026-10-16T23:23:17Z",
"changes": 0,
"days_archived": 1,
"avg_page_bytes": 1270
} |
| Page title and metadata | {
"title": "FedEx® Tracking"
} |
| Trackers | {
"requests": 0
} |
| Forms and mixed content | {
"third_party_scripts": 0
} |
| Status | {
"up": true,
"code": 200,
"timings": {
"dns": 4,
"tls": 232,
"wait": 229,
"connect": 231,
"download": 0
},
"response_ms": 696
} |
| TLS connection | {
"alpn": "h2",
"cipher": "TLS_AES_256_GCM_SHA384",
"protocol": "TLSv1.3",
"versions": [
"TLSv1.2",
"TLSv1.3"
],
"authorized": true,
"forward_secrecy": true
} |
| Ports | {
"open": [
21,
80,
443
]
} |
| Carbon | {
"bytes": 2301,
"co2_grams": 0.0001,
"cleaner_than": 95
} |
| Dns server | {
"ns": [
{
"ip": "162.159.27.32",
"host": "launch2.spaceship.net"
},
{
"ip": "162.159.26.38",
"host": "launch1.spaceship.net"
}
],
"zone": "fedexdelivery247.live"
} |
| Location | {
"ip": "66.29.148.25",
"asn": "22612",
"org": "Namecheap, Inc.",
"city": "Los Angeles",
"country": "US"
} |
| Ssl | {
"issuer": "Let's Encrypt / YR1",
"subject": "fedexdelivery247.live"
} |
| DNS records | {
"A": [
"66.29.148.25"
],
"MX": [
"{\"exchange\": \"mx2.spacemail.com\", \"priority\": 0}",
"{\"exchange\": \"mx1.spacemail.com\", \"priority\": 0}"
],
"NS": [
"launch2.spaceship.net",
"launch1.spaceship.net"
],
"SOA": "{\"nsname\": \"launch1.spaceship.net\", \"hostmaster\": \"support.spaceship.com\", \"serial\": 1792159229, \"refresh\": 43200, \"retry\": 3600, \"expire\": 604800, \"minttl\": 3600}",
"TXT": [
"v=spf1 include:spf.shared.spaceship.host include:spf.spacemail.com ~all"
]
} |
| Dnssec | {
"ds": true,
"rrsig": true,
"dnskey": true
} |
| 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
} |
| Get ip | {
"ip": "66.29.148.25",
"family": 4
} |
| Redirects | {
"chain": [
"https://fedexdelivery247.live"
]
} |
| Subdomains | {
"count": 1,
"subdomains": [
"www.fedexdelivery247.live"
]
} |
| HTTP headers | {
"headers": {
"server": "LiteSpeed",
"content-type": "text/html; charset=UTF-8",
"x-powered-by": "PHP/8.2.35"
}
} |
No. PhishDestroy classifies fedexdelivery247.live as a FedEx impersonation page (risk: high, 69/100); it was first detected on 2026-10-23. VirusTotal: 3/92 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on fedexdelivery247.live. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
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.
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
launch1.spaceship.netlaunch2.spaceship.netmx2.spacemail.compriority 0mx1.spacemail.compriority 0Location describes the IP network.
e3a1b1c395747db9f98ba584e1528107807945d45aec9d607691e2f9cda28ee1fedexdelivery247.livewww.fedexdelivery247.liveSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.fedexdelivery247.liveDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of fedexdelivery247.live · checked Oct 23, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
https://fedexdelivery247.live/X-Powered-By: PHP/8.2.35Content-Type: text/html; charset=UTF-8Content-Encoding: gzipServer: LiteSpeedgzip1001text/html; charset=UTF-8Fri, 23 Oct 2026 16:32:17 GMTtimeout=5, max=100LiteSpeedAccept-EncodingPHP/8.2.35LiteSpeedValues retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
fedexdelivery247.live
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Reachable
PD-20261023-8C2457
Page captured
View sourceNo threat flag
View source3/92 engine detections
View sourcefedexdelivery247.live
View sourcePD-20261023-8C2457 Recipient: abuse@spaceship.com If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
fedexdelivery247.live)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.