Skip to content

Hostname

securityscorecard.io

Last fetched

securityscorecard.io resolves to 13.227.192.106, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. securityscorecard.io 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 · securityscorecard.ioRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint4.6/10canon.whisper.security/host/securityscorecard.io

Resolution chain

IPv6 resolution

No AAAA record for securityscorecard.io is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:1011
Registrant organisation
digital privacy corporation

Subdomains

Subdomain
app.securityscorecard.io
assets.securityscorecard.io
atlas.securityscorecard.io
auth.securityscorecard.io
demo.securityscorecard.io
gsnlink.securityscorecard.io
links.securityscorecard.io
mandrill.securityscorecard.io
meet.securityscorecard.io
mta-sts.securityscorecard.io
platform-api.securityscorecard.io
platform-dev-access.securityscorecard.io

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

  • ns-245.awsdns-30.com
  • ns-846.awsdns-41.net
  • ns-1431.awsdns-50.org
  • ns-1626.awsdns-11.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: %{i}._ip.%{h}._ehlo.%{d}._spf.vali.email

Threat-feed evidence

History

Related pages

Pivot from securityscorecard.io 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: "securityscorecard.io"})-[: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.