Skip to content

Hostname

hypertec.co.uk

Last fetched

hypertec.co.uk resolves to 20.254.118.4, announced in 20.192.0.0/10 by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in GB. hypertec.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 · hypertec.co.ukRouting diversity1.5/10Peering density8.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.0/10canon.whisper.security/host/hypertec.co.uk

Resolution chain

IPv6 resolution

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

Attribution

Azure

cloud · ORIGIN_AS

WHOIS identity

Registrar
registrar:tucows inc t/a tucows [tag = tucows-ca]
Registrant organisation
hypertec

Subdomains

Subdomain
cloud.hypertec.co.uk
conf.hypertec.co.uk
config.hypertec.co.uk
ftp.hypertec.co.uk
mail.hypertec.co.uk
www.hypertec.co.uk

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

  • 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
  • dns0.star.co.uk
  • dns1.star.co.uk

MX records

  • hypertec-co-uk.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com
  • a: hypertec.co.uk
  • mx: hypertec.co.uk
  • ip: 172.187.252.165
  • ip: 178.62.113.225
  • ip: 51.178.153.192

Threat-feed evidence

History

Related pages

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