Skip to content

Hostname

vet-ct.com

Last fetched

vet-ct.com resolves to 108.128.209.185, announced in 108.128.0.0/13 by AMAZON-02 - Amazon.com, Inc. in IE. vet-ct.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 · vet-ct.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/vet-ct.com

Resolution chain

IPv6 resolution

No AAAA record for vet-ct.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of vet-ct.com owner
Contact emails
victoriajohnsonimaging@gmail.com, 16eddf27-42ad-4e48-9e03-f3003f20a5e8@identity-protect.org, 3359423a-614e-423c-8cc2-99270395549c@identity-protect.org, 5934b1e0-2de2-4db5-ac43-8e17ff8a52b1@identity-protect.org, 79c41cb7-aeea-4e56-9223-18a8b4e272a3@identity-protect.org, 8c120dd6-dac2-4a35-ae86-b4cebf77f744@identity-protect.org, ab3c6697-fba2-4743-bf7b-94cb3fc6d994@identity-protect.org, bb11c21a-b3c5-4fa6-ba77-c4b496af9933@identity-protect.org

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-279.awsdns-34.com
  • ns-748.awsdns-29.net
  • ns-1103.awsdns-09.org
  • ns-1543.awsdns-00.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: amazonses.com
  • include: ciphr247.com
  • include: _spf.google.com
  • include: spf.mandrillapp.com
  • mx: vet-ct.com
  • include: 5345458.spf10.hubspotemail.net
  • ip: 54.228.184.18

Threat-feed evidence

History

Related pages

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