Skip to content

Hostname

trulucks.com

Last fetched

trulucks.com resolves to 138.197.224.156, announced in 138.197.224.0/22 by DIGITALOCEAN-ASN - DigitalOcean, LLC in US. trulucks.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 · trulucks.comRouting diversity1.5/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint9.0/10canon.whisper.security/host/trulucks.com

Resolution chain

IPv6 resolution

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

Attribution

digitalocean

ORIGIN_AS

WHOIS identity

Registrar
iana:291
Registrant organisation
progressive networking solutio
Contact emails
trulucks.com-registrant@directnicwhoiscompliance.com, hostinfo@pronetworking.com, trulucks.com@dnic.jewellaprivacy.com

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-244.awsdns-30.com
  • ns0.dnsmadeeasy.com
  • ns1.dnsmadeeasy.com
  • ns2.dnsmadeeasy.com
  • ns3.dnsmadeeasy.com
  • ns4.dnsmadeeasy.com
  • ns-634.awsdns-15.net
  • 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
  • ns-1302.awsdns-34.org
  • ns-1625.awsdns-11.co.uk

MX records

  • mx1-us1.ppe-hosted.com
  • mx2-us1.ppe-hosted.com

SPF policy

  • include: spf.mandrillapp.com
  • a: dispatch-us.ppe-hosted.com
  • a: webmail.trulucks.com
  • include: servers.mcsv.net
  • include: mailgun.org
  • ip: 199.58.213.157
  • ip: 199.58.213.158
  • ip: 72.47.193.54

Threat-feed evidence

History

Related pages

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