Hostname
looksharp.com
Last fetched
looksharp.com resolves to 100.24.138.147, announced in 100.24.0.0/13 by AMAZON-AES - Amazon.com, Inc. in US. looksharp.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
- 100.24.138.147
100.24.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 100.28.204.53
100.24.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 100.51.122.112
100.48.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 34.192.105.214
34.192.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.7.198.113
52.4.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.86.217.93
52.86.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 98.87.111.217
98.80.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 98.95.72.57
98.88.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
IPv6 resolution
No AAAA record for looksharp.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:228
- Registrant organisation
- internmatch
- Contact emails
- ryan@internmatch.com, info@domain-contact.org
Subdomains
Showing 4 of 5. View all 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
- ns-445.awsdns-55.com
- ns-882.awsdns-46.net
- ns-1102.awsdns-09.org
- ns-1876.awsdns-42.co.uk
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- aspmx2.googlemail.com
- aspmx3.googlemail.com
SPF policy
- include: spf.braintreegateway.com
- include: _spf.google.com
- include: email.looksharp.com
- include: mktomail.com
- include: sparkpostmail.com
- include: stspg-customer.com
- include: sendgrid.net
Threat-feed evidence
History
Related pages
Pivot from looksharp.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: "looksharp.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.