Skip to content

Hostname

shopsky.com

Last fetched

shopsky.com resolves to 173.249.147.254, announced in 173.249.147.0/24 by VPSDATACENTER - Liquid Web, L.L.C in US. shopsky.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 · shopsky.comRouting diversity1.5/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/shopsky.com

Resolution chain

IPv6 resolution

Attribution

liquid

ORIGIN_AS

WHOIS identity

Registrar
iana:2
Registrant organisation
perfect privacy,
Contact emails
ab84c2669x8@networksolutionsprivateregistration.com, cf8s55t59fd@networksolutionsprivateregistration.com, d946m9ar2fh@networksolutionsprivateregistration.com, hf5r33da5g7@networksolutionsprivateregistration.com, hr75a3dn6s6@networksolutionsprivateregistration.com, m58tc8cs33j@networksolutionsprivateregistration.com, nk6js2d26hj@networksolutionsprivateregistration.com, nw8ve4p35y7@networksolutionsprivateregistration.com, q78p48ty2cb@networksolutionsprivateregistration.com, u79w455w7wh@networksolutionsprivateregistration.com, vk9vf5h28kj@networksolutionsprivateregistration.com, ye3n94n46mj@networksolutionsprivateregistration.com

Subdomains

Subdomain
mail.shopsky.com
www.shopsky.com

Showing 2 of 2 subdomains (2 per page).

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

  • ns1.nexcess.net
  • ns2.nexcess.net
  • ns3.nexcess.net
  • ns4.nexcess.net

MX records

  • mail.shopsky.com

SPF policy

  • a: shopsky.com
  • mx: shopsky.com
  • ip: 173.231.200.138
  • ip: 173.249.147.254
  • ip: 198.46.93.157

Threat-feed evidence

History

Related pages

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