Hostname
trucksfloor.com
Last fetched
trucksfloor.com resolves to 13.127.17.55, announced in 13.126.0.0/15 by AMAZON-02 - Amazon.com, Inc. in IN. trucksfloor.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
- 13.127.17.55
13.126.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 13.127.8.140
13.126.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 13.204.97.200
13.204.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 13.232.103.17
13.232.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 13.235.171.167
13.232.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 13.235.182.113
13.232.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 3.108.111.202
3.108.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 3.7.170.53
3.6.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 43.205.79.86
43.204.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 65.1.30.237
65.0.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 65.2.22.130
65.0.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
IPv6 resolution
No AAAA record for trucksfloor.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:146
- Registrant organisation
- domains by proxy,
Subdomains
Showing 3 of 7. 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-61.awsdns-07.com
- ns-550.awsdns-04.net
- ns-1445.awsdns-52.org
- ns-2011.awsdns-59.co.uk
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
Threat-feed evidence
History
Related pages
Pivot from trucksfloor.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: "trucksfloor.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.