Skip to content

Hostname

softruck.com

Last fetched

softruck.com resolves to 44.206.158.201, announced in 44.192.0.0/11 by AMAZON-AES - Amazon.com, Inc. in US. softruck.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · softruck.comRouting diversity1.5/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/softruck.com

Resolution chain

IPv6 resolution

No AAAA record for softruck.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:81
Registrant organisation
mathias fonseca
Contact emails
mathias.fonseca@softruck.com, 52ee889a23ab51cab4a05fe323aa2e6f-40156784@contact.gandi.net, cbc9b62fcffad6736fbc60b6c35e8fb4-3957029@contact.gandi.net

Subdomains

Subdomain
agibens.softruck.com
agnprotecaoveicular.softruck.com
ajuda.softruck.com
apiary.softruck.com
app.softruck.com
arrielrastreamento.softruck.com
arroz.softruck.com
assembler.softruck.com
billing.softruck.com
blog.softruck.com
bot-lemao.softruck.com
calamp.softruck.com

Showing 12 of 262. 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.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • ns-246.awsdns-30.com
  • ns-619.awsdns-13.net
  • ns-1495.awsdns-58.org
  • ns-1831.awsdns-36.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

SPF policy

  • include: _spf.google.com
  • a: softruck.com
  • include: sparkpostmail.com
  • include: spf.mail.intercom.io

Threat-feed evidence

History

Related pages

Pivot from softruck.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: "softruck.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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.