Skip to content

Hostname

tricog.com

Last fetched

tricog.com resolves to 119.18.49.27, announced in 119.18.49.0/24 by PUBLIC-DOMAIN-REGISTRY - PDR in IN. tricog.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 · tricog.comRouting diversity2.4/10Peering density3.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/tricog.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:146
Registrant organisation
charit bhograj
Contact emails
drcharit@tricog.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-186.awsdns-23.com
  • ns-846.awsdns-41.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-1153.awsdns-16.org
  • ns-1630.awsdns-11.co.uk

MX records

  • inbound-smtp.us-west-2.amazonaws.com
  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com

SPF policy

  • include: _spf.google.com
  • include: spf.sendinblue.com
  • a: tricog.com
  • mx: tricog.com
  • include: 123456.spf03.hubspotemail.net
  • include: servers.mcsv.net
  • include: transmail.net
  • ip: 206.189.139.115

Threat-feed evidence

History

Related pages

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