Skip to content

Hostname

mbs.ac.uk

Last fetched

mbs.ac.uk resolves to 18.135.205.191, announced in 18.132.0.0/14 by AMAZON-02 - Amazon.com, Inc. in GB. mbs.ac.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 · mbs.ac.ukRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.5/10canon.whisper.security/host/mbs.ac.uk

Resolution chain

IPv6 resolution

No AAAA record for mbs.ac.uk is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrant organisation
rob clarke kilburn building
Contact emails
rob.clarke@manchester.ac.uk

Subdomains

Subdomain
admbs.mbs.ac.uk
alumni.mbs.ac.uk
app.mbs.ac.uk
archive.mbs.ac.uk
autodiscover.mbs.ac.uk
avwqr374.mbs.ac.uk
cliptest-ip-2.mbs.ac.uk
cliptest-ip.mbs.ac.uk
connect.mbs.ac.uk
dev.mbs.ac.uk
dom01.mbs.ac.uk
domino.mbs.ac.uk

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

  • ns4.ja.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
  • edns-joule-001.net.its.manchester.ac.uk
  • edns-reynolds-001.net.its.manchester.ac.uk
  • ns1.manchester.ac.uk
  • ns2.manchester.ac.uk

MX records

  • mxa-0053d701.gslb.pphosted.com
  • mxb-0053d701.gslb.pphosted.com

SPF policy

  • include: %{ir}.%{v}.%{d}.spf.has.pphosted.com

Threat-feed evidence

History

Related pages

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