Skip to content

Hostname

typesafe.com

Last fetched

typesafe.com resolves to 100.51.126.213, announced in 100.48.0.0/12 by AMAZON-AES - Amazon.com, Inc. in US. typesafe.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 · typesafe.comRouting diversity1.5/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint5.6/10canon.whisper.security/host/typesafe.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:81
Registrant organisation
domains by proxy,
Contact emails
typesafe.com@domainsbyproxy.com, 559b13e18c21b4b7cdb97fb652fdcc95-33440268@contact.gandi.net

Subdomains

Subdomain
blog.typesafe.com
buy.typesafe.com
ci.typesafe.com
conductr.typesafe.com
demo.typesafe.com
downloads.typesafe.com
halo.typesafe.com
info.typesafe.com
inform.typesafe.com
marketing.typesafe.com
moxie.typesafe.com
private-repo.typesafe.com

Showing 12 of 26. 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

Sample outbound links

Mail and authentication

Nameservers

  • ns10.digicertdns.com
  • ns0.dnsmadeeasy.com
  • ns1.dnsmadeeasy.com
  • ns2.dnsmadeeasy.com
  • ns3.dnsmadeeasy.com
  • ns4.dnsmadeeasy.com

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: _spf.google.com
  • include: mktomail.com
  • mx: typesafe.com
  • a: info.typesafe.com

Threat-feed evidence

History

Related pages

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