Skip to content

Hostname

hughestelematics.com

Last fetched

hughestelematics.com resolves to 8.38.73.46, announced in 8.32.0.0/12 by LEVEL3 - Level 3 Parent, LLC in US. hughestelematics.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 · hughestelematics.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.2/10canon.whisper.security/host/hughestelematics.com

Resolution chain

IPv6 resolution

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

Attribution

level parent

ORIGIN_AS

WHOIS identity

Registrar
iana:299
Registrant organisation
domain administrator
Contact emails
domainlegalcontact@verizon.com, domainname.cert@one.verizon.com, fredblumer@earthlink.net

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

  • ns1.hughestelematics.com
  • ns2.hughestelematics.com
  • ns3.hughestelematics.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

  • inbound-smtp.us-west-2.amazonaws.com
  • mail-atl.hughestelematics.com
  • mail-pce.hughestelematics.com

SPF policy

  • ip: 199.249.25.0/24
  • ip: 140.108.26.0/24
  • include: hughestelematics.com
  • mx: hughestelematics.com
  • ip: 194.114.84.17
  • ip: 211.151.114.67
  • ip: 70.151.74.68
  • ip: 8.17.66.6
  • ip: 8.38.73.100
  • ip: 8.38.73.40
  • ip: 8.38.73.47

Threat-feed evidence

History

Related pages

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