Skip to content

Hostname

scopesky.com

Last fetched

scopesky.com resolves to 104.21.76.126, announced in 104.21.64.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. scopesky.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 · scopesky.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/scopesky.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:146
Registrant organisation
domains by proxy,
Contact emails
scopesky.com@domainsbyproxy.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

  • dale.ns.cloudflare.com
  • michelle.ns.cloudflare.com
  • 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

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • ip: 44.192.35.0/24
  • ip: 18.235.53.110/32
  • ip: 3.222.0.112/29
  • ip: 3.238.137.128/30
  • ip: 52.203.5.138/32
  • ip: 3.235.255.160/29
  • ip: 34.198.193.174/32
  • ip: 34.202.174.188/32
  • ip: 34.199.167.230/32
  • ip: 3.222.0.24/29
  • ip: 3.91.171.64/28
  • ip: 3.222.0.88/29
  • ip: 54.159.173.91/32
  • ip: 3.219.176.96/29
  • include: _spf.google.com
  • include: fdspfus2.freshemail.io

Threat-feed evidence

History

Related pages

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