Skip to content

Hostname

spinneys.com

Last fetched

spinneys.com resolves to 51.104.185.67, announced in 51.104.0.0/15 by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in IE. spinneys.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 · spinneys.comRouting diversity1.5/10Peering density7.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/spinneys.com

Resolution chain

Attribution

Azure

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:2
Registrant organisation
wright, michael attn spinneys.com care of network solutions
Contact emails
a.barakat@spinneys.com, bm4339m52bk@networksolutionsprivateregistration.com, dz3ya7xu4t2@networksolutionsprivateregistration.com, ex3482b53w6@networksolutionsprivateregistration.com, kp9pp3hq3w5@networksolutionsprivateregistration.com, ph9ry83j6u4@networksolutionsprivateregistration.com, vn6f82w532p@networksolutionsprivateregistration.com, michael.wright@spinneys.com, xr8yy6t25w4@networksolutionsprivateregistration.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

  • ns11.worldnic.com
  • ns12.worldnic.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

  • spinneys-com.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com

Threat-feed evidence

History

Related pages

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