Skip to content

Hostname

computerarts.co.uk

Last fetched

computerarts.co.uk resolves to 185.113.25.57, announced in 185.113.24.0/22 by future - Future Publishing Ltd in GB. computerarts.co.uk 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 · computerarts.co.ukRouting diversity1.5/10Peering density4.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.3/10canon.whisper.security/host/computerarts.co.uk

Resolution chain

IPv6 resolution

No AAAA record for computerarts.co.uk is recorded in WhisperGraph.

Attribution

future publishing

ORIGIN_AS

WHOIS identity

Registrar
registrar:lexsynergy ltd [tag = lexsynergy]
Registrant organisation
future publishing

Subdomains

Subdomain
forum.computerarts.co.uk
mos.computerarts.co.uk
www.computerarts.co.uk

Showing 3 of 3 subdomains (3 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

  • ns-215.awsdns-26.com
  • ns-885.awsdns-46.net
  • 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
  • ns-1362.awsdns-42.org
  • ns-1909.awsdns-46.co.uk

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

  • include: _spf.google.com

Threat-feed evidence

History

Related pages

Pivot from computerarts.co.uk 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: "computerarts.co.uk"})-[: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.