Hostname
xurl.es
Last fetched
xurl.es resolves to 104.21.49.110, announced in 104.21.48.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. xurl.es is listed by 2 threat feeds; reconciled level MEDIUM.
Threat posture
24threat score (procedure-native scale)
MEDIUMListed by 2 threat feeds. Advisory: popularity-trust-offset.
Categories: Phishing
- Threat feeds listing this
- 2
- Verdict coverage
- malicious-evidenced
- First seen on a feed
- Wed, 26 Aug 2026 14:45:24 GMT
- Last seen on a feed
- Sat, 26 Sep 2026 22:32:45 GMT
Nutrition Label
Resolution chain
- 104.21.49.110
104.21.48.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.162.2
172.67.160.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.96.3
188.114.96.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.97.3
188.114.97.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 217.154.180.96
217.154.180.0/22 · IONOS-AS - IONOS SE · Madrid, ES
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for xurl.es. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.
Subdomains
Showing 3 of 3 subdomains (3 per page).
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Mail and authentication
Nameservers
- celine.ns.cloudflare.com
- thomas.ns.cloudflare.com
- ns.dinahosting.com
- ns.gestiondecuenta.com
- ns2.gestiondecuenta.com
- ns3.gestiondecuenta.com
- ns4.gestiondecuenta.com
MX records
- mail.xurl.es
SPF policy
- a: xurl.es
- mx: xurl.es
- a: priceless-morse.217-154-180-96.plesk.page
Threat-feed evidence
History
Related pages
Pivot from xurl.es into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "xurl.es"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.