Skip to content

Hostname

preventice.com

Last fetched

preventice.com resolves to 13.248.160.137, announced in 13.248.160.0/20 by AMAZON-02 - Amazon.com, Inc. in CA. preventice.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 · preventice.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/preventice.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:299
Registrant organisation
boost information systems dba preventice
Contact emails
domains@preventice.com, itservices@preventice.com, webmaster@bostonscientific.com

Subdomains

Subdomain
autodiscover.preventice.com
ftp.preventice.com
id.preventice.com
mail.preventice.com
mail2.preventice.com
media.preventice.com
mfa.preventice.com
pc.preventice.com
portal.preventice.com
secure.preventice.com
skgfilehub.preventice.com
thanos.preventice.com

Showing 12 of 15. View all subdomains →

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Mail and authentication

Nameservers

  • dns1.cscdns.net
  • dns2.cscdns.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

MX records

  • preventice-com.mail.protection.outlook.com

SPF policy

  • include: _u.preventice.com._spf.smart.ondmarc.com

Threat-feed evidence

History

Related pages

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