Hostname
best-shield.com
Last fetched
best-shield.com resolves to 104.21.88.218, announced in 104.21.80.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. best-shield.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.88.218
104.21.80.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.153.140
172.67.144.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 91.209.253.12
91.209.253.0/24 · CLOUDFLARESPECTRUM - Cloudflare London, LLC · Riyadh, SA
- 91.209.253.13
91.209.253.0/24 · CLOUDFLARESPECTRUM - Cloudflare London, LLC · Riyadh, SA
- 91.209.253.14
91.209.253.0/24 · CLOUDFLARESPECTRUM - Cloudflare London, LLC · Riyadh, SA
- 91.209.253.9
91.209.253.0/24 · CLOUDFLARESPECTRUM - Cloudflare London, LLC · Riyadh, SA
- 91.209.253.10
91.209.253.0/24 · CLOUDFLARESPECTRUM - Cloudflare London, LLC · Riyadh, SA
- 91.209.253.11
91.209.253.0/24 · CLOUDFLARESPECTRUM - Cloudflare London, LLC · Riyadh, SA
- 162.159.143.27
162.159.128.0/19 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.66.3.23
172.66.0.0/22 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:146
- Registrant organisation
- foximedia24 inh. gregor kliglich
- Contact emails
- info@foximedia24.de
Subdomains
Mail and authentication
Nameservers
- donald.ns.cloudflare.com
- leia.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
- smtp.google.com
- bestshield-com01b.mail.protection.outlook.com
SPF policy
- include: secureserver.net
Threat-feed evidence
History
Related pages
Pivot from best-shield.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: "best-shield.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.