Skip to content

Hostname

vividcortex.com

Last fetched

vividcortex.com resolves to 13.107.246.73, announced in 13.104.0.0/14 by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in CA. vividcortex.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 · vividcortex.comRouting diversity1.5/10Peering density8.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/vividcortex.com

Resolution chain

IPv6 resolution

Attribution

Azure

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:269
Registrant organisation
baron schwartz
Contact emails
2l2y5k0754@junkemailprevention.com, 4d10149520@nojunkemailaddress.com, 6w54659025@filteredemailaddress.com, info@domain-contact.org, owner-1016434@vividcortex.com.whoisprivacyservice.org, owner-1193497@vividcortex.com.whoisprivacyservice.org, owner-1843599@vividcortex.com.whoisprivacyservice.org, owner-5803747@vividcortex.com.whoisprivacyservice.org, owner-8948340@vividcortex.com.whoisprivacyservice.org, owner-9218289@vividcortex.com.whoisprivacyservice.org, owner-9415671@vividcortex.com.whoisprivacyservice.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-211.awsdns-26.com
  • ns-937.awsdns-53.net
  • ns-1107.awsdns-10.org
  • ns-1823.awsdns-35.co.uk

MX records

  • vividcortex-com.mail.protection.outlook.com

SPF policy

  • include: _spf.google.com
  • include: spf.mandrillapp.com
  • include: _spf.salesforce.com
  • include: stspg-customer.com
  • a: vividcortex.com
  • include: spf.mail.intercom.io

Threat-feed evidence

History

Related pages

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