Hostname
luxhosting.lu
Last fetched
luxhosting.lu resolves to 104.21.75.62, announced in 104.22.111.0/24 by CLOUDFLARENET - Cloudflare, Inc. in CA. luxhosting.lu is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 104.21.75.62
104.22.111.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.215.94
172.68.135.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.96.3
188.117.84.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.96.6
188.117.84.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.97.3
188.117.85.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.97.6
188.117.85.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrant organisation
- networks sarl luxhosting
Subdomains
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Mail and authentication
Nameservers
- cass.ns.cloudflare.com
- kip.ns.cloudflare.com
- roxy.ns.cloudflare.com
- wesley.ns.cloudflare.com
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
MX records
- fallbackmx.spamexperts.eu
- mail.luxhosting.lu
- lastmx.spamexperts.net
- brands-cp.whgi.net
SPF policy
- ip: 194.42.98.15/32
- ip: 194.42.98.17/32
- include: md02.com
- mx: mx2.anti-spam.lu
- mx: mx3.anti-spam.lu
- a: luxhosting.lu
- mx: luxhosting.lu
- ip: 194.147.93.190
- ip: 194.147.93.191
- ip: 194.147.93.203
- ip: 194.147.93.204
Threat-feed evidence
History
Related pages
Pivot from luxhosting.lu 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: "luxhosting.lu"})-[: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.