Skip to security report
Domain security and threat intelligence
xfntiy.weebly.com favicon

xfntiy.weebly.com

In short

xfntiy.weebly.com is a Xfinity impersonation page detected by PhishDestroy on 2026-09-11. Risk: critical (100/100). Registrar: Weebly. Status: Content unavailable. Hosting: WEEBLY - Weebly, Inc., US. VirusTotal: 18/89 engines flag it. Do not enter credentials or connect a wallet.

“Home”

Registrar
Weebly
Resolved IP
74.115.51.8
Registered
Mar 29, 2006
PhishDestroy assessment Critical
Availability Content unavailable Content was unavailable in the latest observation Observed · HTTP probe
VirusTotal detections: 18/89 Automated brand label: Xfinity
Sep 11, 2026 CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 18. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
engine detections
Google Safe Browsing
Page captures
open gallery
Domain age
Source evidenceVirusTotal 18 / 89 6 sources

VirusTotal

18 / 89 engine detections

Open report

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

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

Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Phishing

Analysis

Critical
VirusTotal
18 / 89
Page captures
9

PhishDestroy threat report

Overview

xfntiy.weebly.com is a phishing page that impersonates Xfinity. It is hosted as a free Weebly site under a misspelled version of the brand name, with the letters of "xfinity" shuffled to "xfntiy" so it passes a quick glance. PhishDestroy first flagged it on 2026-09-11. On 2026-10-19 the address still resolved, but the root page served no content.

How the scam works

Xfinity impersonation pages usually reach victims through emails or texts about billing problems, account suspensions or service updates. The link leads to a page styled like Xfinity's sign-in or payment screen. Anything typed there, such as the Xfinity username and password, the linked email account, or card details, goes to the operator rather than to Xfinity. The page carried only the generic title "Home," which does not name the brand, but scanners matched its content to Xfinity.

Evidence

On 2026-09-23, 18 of 89 VirusTotal engines flagged the site. They included BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, Emsisoft, G-Data, Ermes and alphaMountain.ai, a mix of vendors that reached the same conclusion independently. urlscan.io returned a malicious verdict and recognized Xfinity as the brand being imitated. That brand match supports our impersonation classification. PhishDestroy lists the site on its blocklist.

Infrastructure

The site sits on Weebly's website builder, served from 74.115.51.8 on Weebly, Inc.'s US network. The 2006-03-29 registration date belongs to the parent weebly.com domain, so it says nothing about when this subdomain was created. A free builder subdomain costs the operator nothing and inherits the platform's reputation. The Let's Encrypt certificate is Weebly's standard platform certificate, so the padlock in the browser is not a sign that the page is legitimate.

What to do

If you entered your Xfinity credentials, change the password right away from Xfinity's official app or by typing the address yourself. Turn on two-step verification and check the account for changed contact details or unfamiliar devices. If the same password protects your email or other accounts, change it there too. If you submitted card details, call your bank to block the card and dispute any charges. Defenders should block the hostname, watch Weebly-hosted links in inbound mail for brand misspellings, and report the page to Weebly for removal.

Collected source details

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

URLScan · 2026-09-11T01:03:02Z

Observed: · Retrieved:

Uuid
01a08dfd-2fb3-70eb-88f2-d7c45bde392d
Final url
https://xfntiy.weebly.com/
Status
200
Redirected
sub-domain
Redirects
[
    {
        "to": "https://www.xfntiy.weebly.com/",
        "from": "http://www.xfntiy.weebly.com/",
        "status": 307
    },
    {
        "to": "http://www.xfntiy.weebly.com/",
        "from": "https://www.xfntiy.weebly.com/",
        "status": 307
    },
    {
        "to": "http://xfntiy.weebly.com/",
        "from": "http://www.xfntiy.weebly.com/",
        "status": 301
    },
    {
        "to": "https://xfntiy.weebly.com/",
        "from": "http://xfntiy.weebly.com/",
        "status": 307
    }
]
Ip
74.115.51.9
Ptr
wildcard.weebly.com
Contacted domains
[
    "cdn2.editmysite.com",
    "cdn11.editmysite.com",
    "ec.editmysite.com",
    "www.gstatic.com",
    "www.google.com",
    "cdn3.editmysite.com",
    "ssl.google-analytics.com",
    "fonts.googleapis.com",
    "www.xfntiy.weebly.com"
]
Contacted IP addresses
[
    "142.251.20.94",
    "34.218.174.111",
    "142.251.156.119",
    "192.178.183.97",
    "151.101.1.46",
    "151.101.193.46",
    "192.178.183.95",
    "74.115.51.9"
]
Asns
[
    "15169",
    "16509",
    "54113",
    "27647"
]
Countries
[
    "US"
]
Document hash
53a9dfadda35e11f075d474cc531cf6ba3f06cd2a332c5cd7efdcd99dd2079dc
Script hashes
[
    "397452d9f6a2ea6a2135b45c9e40139c68ac6661f3bab4413e7299586ccb408a",
    "5a630b41e7c3d34392bcb150a5731b6261bc6314d71d5db8407a646af15bf8af",
    "b6353ca52760aba4e7547ae9861db68158dc2af0f4febece55e5c775ee4449f5",
    "f75570c56743e8c705cb06f5f1f9b1f8f2cc13119f5e2acda2f3bb8d987de94a",
    "446f48f512ecc0b771af3c21a3036de3a1c5740d1e6bdbb61448834326d0c738",
    "c4cd233d3d6b0f184e99d5017e521b4c6f9106d3e546864a8ba516189b934311",
    "cfbf67a85c039719090cff2c4718de99203b1ced78cfb8fae5f7240d2f1570b7"
]
Globals
[
    "Weebly",
    "STATIC_BASE",
    "ASSETS_BASE",
    "STYLE_PREFIX",
    "$",
    "jQuery",
    "_W",
    "publishedWBJP",
    "RECAPTCHA_PUBLIC_KEY",
    "INVISIBLE_RECAPTCHA_PUBLIC_KEY",
    "_",
    "Mustache",
    "jQBrowser",
    "PlatformElement",
    "whenThemeCSSLoaded",
    "isThemeCSSLoaded",
    "blogCommentDisplayForm",
    "YTPlayer",
    "VimeoPlayer",
    "Sd",
    "Rd",
    "Cd",
    "videojs",
    "_V_",
    "jsonrpc",
    "getCartCount",
    "getCartNavElement",
    "reportCartNavElement",
    "initPublishedFlyoutMenus",
    "flyoutMenusRefreshable",
    "initEditorFlyoutMenus",
    "refreshNavCondense",
    "disableFlyouts",
    "FlyoutMenu",
    "objectify",
    "mejs",
    "MediaElement",
    "MediaElementPlayer",
    "require",
    "platformElementRequire"
]
Cookies
[
    "__cf_bm",
    "_snow_ses.99cc",
    "_snow_id.99cc",
    "sp"
]
Storage keys
[
    "modernizr",
    "snowplowOutQueue_snowday__wn_post2"
]
Tls
{
    "san": [
        "*.weebly.com",
        "weebly.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE2",
    "subject": "weebly.com",
    "protocol": "TLS 1.3",
    "valid_to": "2026-11-06T20:20:53Z",
    "valid_from": "2026-08-08T20:20:54Z"
}
Domain age days
0
Apex age days
4916
Tls age days
33
Tls valid days
89
Requests
39
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 98,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "xfinity"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "Xfinity"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=UTF-8"
}
Cloudflare Radar · 2026-09-11T10:01:19Z

Observed: · Retrieved:

Uuid
68157e3a-7007-4bdd-b716-93e06f2edaf0
Final url
https://xfntiy.weebly.com/
Status
200
History
[
    {
        "url": "https://xfntiy.weebly.com/",
        "status": 200
    }
]
DOM structure hash
ee70d21003fdd54e26a95feaef09aa24a99310c10ba9733103a73a5ee010b7b1
Document hash
05402db8919414d47de0ddf413d8c7ce4215a72d98861b299c843e1e730e438e
Url risks
[
    "Phishing"
]
Domain risks
[
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "xfntiy.weebly.com",
        "type": "A",
        "value": "74.115.51.9"
    },
    {
        "name": "xfntiy.weebly.com",
        "type": "A",
        "value": "74.115.51.8"
    }
]
Dnssec valid
false
Ip
74.115.51.9
Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
Registration record
{
    "registrar": "MarkMonitor Inc.",
    "created": "2006-03-29T00:25:07Z",
    "updated": "2026-08-10T19:04:53Z",
    "expires": "2032-03-28T23:25:07Z",
    "nameservers": [
        "ns-123.awsdns-15.com",
        "ns-1500.awsdns-59.org",
        "ns-1797.awsdns-32.co.uk",
        "ns-646.awsdns-16.net"
    ]
}
VirusTotal · 2026-10-16T18:25:00Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 45,
    "malicious": 19,
    "suspicious": 0,
    "undetected": 28
}
Vendor labels
{
    "ESET": "phishing",
    "Ermes": "phishing",
    "VIPRE": "malware",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "Webroot": "malicious",
    "ZeroFox": "malicious",
    "Emsisoft": "phishing",
    "Fortinet": "phishing",
    "Netcraft": "malicious",
    "URLQuery": "malicious",
    "Kaspersky": "phishing",
    "LevelBlue": "phishing",
    "Gridinsoft": "phishing",
    "MalwareURL": "phishing",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Created
2006-03-29T00:00:00Z
Updated
2026-03-30T00:00:00Z
First seen
2026-09-10T17:25:55Z
DNS records
[
    {
        "ttl": 3600,
        "type": "A",
        "value": "74.115.51.8"
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "74.115.51.9"
    }
]
Dns at
2026-10-16T18:30:13Z
Jarm
27d40d40d00040d00042d43d00041df04c41293ba84f6efe3a613b22f983e6
Certificate
{
    "san": [
        "*.weebly.com",
        "weebly.com"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "537be20737256ed93d00e736e0c91ccf99d",
    "sha256": "0ab63db1f470cfa51bc6372a78a47a8db5f315e8e14c970970e78d8f6ccd9281",
    "subject": "weebly.com",
    "valid_to": "2027-01-04T19:46:47Z",
    "valid_from": "2026-10-06T19:46:48Z"
}

Questions about xfntiy.weebly.com

Is xfntiy.weebly.com legit?

No. PhishDestroy classifies xfntiy.weebly.com as a Xfinity impersonation page (risk: critical, 100/100); it was first detected on 2026-09-11. VirusTotal: 18/89 engines flag it. Treat the site as unsafe.

Is xfntiy.weebly.com safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on xfntiy.weebly.com. 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 xfntiy.weebly.com?

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 · 9 captures

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Xfinity report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar (base domain) Weebly
Registration (base domain)weebly.com · Created Mar 29, 2006 — Expires Mar 28, 2032
HTTP Status404 Not Found
Technical detailsProvenance & timestamps
First DetectedSep 11, 2026
DOM Analysisanalyzed Sep 11, 2026score 93/1001 brand signal
Submitted URLhttp://xfntiy.weebly.com/
Observed page title
Home
Automated brand references
Xfinity
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 15 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
74.115.51.8
Network ASN
AS27647
Organization
Weebly, Inc.
Observed location
Oakland, US
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 4

  • ns-123.awsdns-15.com
  • ns-1500.awsdns-59.org
  • ns-1797.awsdns-32.co.uk
  • ns-646.awsdns-16.net

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-08-08 20:20:54
Valid until
2026-11-06 20:20:53
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-11 10:02:07 UTC
Collection source
PhishDestroy collector
Certificate fingerprint9f07f6a9d3d9a7e775e4fbb006342835f96f7bb95121877d4e458dfa52b48bfb
Certificate names · 1 SAN
  • weebly.com

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

Latest Classified Outcome 2026-10-22 10:07:28 UTC

Primary outcome Inactive reason: Http No Content 70% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Root path has no content Content: Absent At Root DNS: Resolved Registration: Unknown
Latest HTTP observation Inactive Http No Content 70% 2026-10-22 10:07:28 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-14 22:09:11 UTC current episode first observed: 2026-10-15 10:08:15 UTC observed RIP window: 2026-10-14 22:09:11 UTC → 2026-10-15 10:08:15 UTC · 11.98h midpoint estimate ≈ 2026-10-15 04:08:43 UTC · precision medium · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 8 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

18 / 89 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 18 detections
alphaMountain.ai
BitDefender
Ermes
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Google Safe Browsing
Gridinsoft
Kaspersky
LevelBlue
Lionic
MalwareURL
Netcraft
Sophos
VIPRE
Webroot

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of xfntiy.weebly.com · checked Sep 11, 2026

55
Needs Work
Performance
FCP
3.49s
First Contentful Paint
LCP
11.42s
Largest Contentful Paint
CLS
0.006
Cumulative Layout Shift
TBT
373ms
Total Blocking Time
SI
5.73s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details8

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
11.98
Estimate basis
Bounded by observations
Estimate precision
Medium

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=cloudflare

Browser
Home
Crawler
404 - Page Not Found
xfntiy.weebly.com
Saved result
Cloaked / Filtered
Stored observation history22

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. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  3. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  4. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  5. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

Earlier observations 17
  1. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  2. Availability monitor · Recorded state

    Unknown→protected

    captcha · challenge

  3. Availability monitor · Recorded state

    Unknown→protected

    captcha · challenge

  4. Availability monitor · Recorded state

    Unknown→protected

    captcha · challenge

  5. Availability monitor · Recorded state

    Unknown→protected

    captcha · challenge

  6. Availability monitor · Recorded state

    Unknown→protected

    captcha · challenge

  7. Availability monitor · Recorded state

    Unknown→protected

    captcha · challenge

  8. Availability monitor · Recorded state

    Unknown→protected

    captcha · challenge

  9. Availability monitor · Recorded state

    Unknown→protected

    captcha · challenge

  10. Availability monitor · Recorded state

    Unknown→protected

    captcha · challenge

  11. Availability monitor · Recorded state

    Unknown→protected

    captcha · challenge

  12. Availability monitor · Recorded state

    protected

    captcha · challenge

  13. VirusTotal · Detection count

    19→18

  14. VirusTotal · Detection count

    18→19

  15. VirusTotal · Detection count

    10→18

  16. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

  17. Availability monitor · First collection record

    Reachable

Recorded activity

4 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    18/89 engine detections

    View source
  3. URLScan

    Page captured

    View source
  4. Added to PhishDestroy

    xfntiy.weebly.com

    View source

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

4 evidence signal groups linked 0 stored notification records Content unavailable

Listed domains receive at least one abuse report; this entry has no retained notification history.

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.

Official reporting routes

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 →

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

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 xfntiy.weebly.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

Stay Informed, Stay Safe

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

Live Threat Feed Appeal This Listing
About this reportSources, observation dates and corrections

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

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

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

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/xfntiy.weebly.com"
  title="PhishDestroy threat report for xfntiy.weebly.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>