Hostname
loredz.com
Last fetched
loredz.com resolves to 104.21.23.153, announced in 104.21.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. loredz.com 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.23.153
104.21.16.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.211.176
172.67.208.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
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:2268
- Registrant organisation
- 3bdou
- Contact emails
- loredz.com@namebrightprivacy.com, primeradomain@gmail.com, primotechpro@gmail.com, saazaza@gmail.com, willcswhite@gmail.com, 3kniqwrimzx14xce7bnl@z.o-w-o.info, 3rdye0unaliin56su03c@z.o-w-o.info, 66mjdj0tq0w5138397zi@d.o-w-o.info, cynzwp51wgu5wdhb9v27@d.o-w-o.info
Subdomains
Showing 2 of 2 subdomains (2 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.
Mail and authentication
Nameservers
- aurora.ns.cloudflare.com
- woz.ns.cloudflare.com
- ns1.gbnetdns.com
- ns2.gbnetdns.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
- _dc-mx.e4460c017f09.loredz.com
Threat-feed evidence
History
Related pages
Pivot from loredz.com 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: "loredz.com"})-[: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.