Hostname
lootsmart.com
Last fetched
lootsmart.com resolves to 104.21.63.35, announced in 104.22.12.0/24 by CLOUDFLARENET - Cloudflare, Inc. in CA. lootsmart.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.63.35
104.22.12.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.234.24.211
172.235.118.0/23 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.239.57.117
172.240.19.0/24 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.67.169.112
172.68.23.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
No AAAA record for lootsmart.com is recorded in WhisperGraph.
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:1068
- Registrant organisation
- benchmark brands,
- Contact emails
- amn@benchmarkbrands.com, lootsmart.com@protecteddomainservices.com, 228e64aa12c24df6b845489d6047b61b.protect@withheldforprivacy.com
Subdomains
| Subdomain |
|---|
| airbuddy.lootsmart.com |
| g7smartwatch.lootsmart.com |
| kingcomfort.lootsmart.com |
| kingcomfortpromo.lootsmart.com |
| safemask.lootsmart.com |
| smartwatchpromo.lootsmart.com |
| www.lootsmart.com |
Showing 7 of 7 subdomains (7 per page).
Mail and authentication
Nameservers
- ed.ns.cloudflare.com
- ruth.ns.cloudflare.com
- dns101.registrar-servers.com
- dns102.registrar-servers.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
- mx.plingest.com
- mx.zoho.eu
- mx2.zoho.eu
- mx3.zoho.eu
SPF policy
- include: zoho.eu
Threat-feed evidence
History
Related pages
Pivot from lootsmart.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: "lootsmart.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.