Skip to content

Hostname

fph.org.uk

Last fetched

fph.org.uk resolves to 188.94.77.115, announced in 188.94.77.0/24 by HAHOSTING - High Availability Hosting Limited in GB. fph.org.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 · fph.org.ukRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint6.6/10canon.whisper.security/host/fph.org.uk

Resolution chain

IPv6 resolution

No AAAA record for fph.org.uk is recorded in WhisperGraph.

Attribution

high availability

ORIGIN_AS

WHOIS identity

Registrar
registrar:godaddy.com, llc. [tag = godaddy]
Registrant organisation
joint faculty of public health of the royal colleges of physicians of the united kingdom

Subdomains

Subdomain
careers.fph.org.uk
cpd.fph.org.uk
eportfolio.fph.org.uk
eportfoliotest.fph.org.uk
intranet.fph.org.uk
link.fph.org.uk
mail.fph.org.uk
www.fph.org.uk

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

  • ns10.dnsmadeeasy.com
  • ns11.dnsmadeeasy.com
  • ns12.dnsmadeeasy.com
  • ns13.dnsmadeeasy.com
  • ns14.dnsmadeeasy.com
  • ns15.dnsmadeeasy.com
  • ns-166-c.gandi.net
  • ns-203-a.gandi.net
  • ns-224-b.gandi.net

MX records

  • eu-smtp-inbound-1.mimecast.com
  • eu-smtp-inbound-2.mimecast.com
  • fph-org-uk.mail.protection.outlook.com

SPF policy

  • ip: 205.201.136.114/32
  • ip: 109.204.119.162/32
  • include: _netblocks.mimecast.com
  • include: spf.protection.outlook.com
  • include: spf.exclaimer.net
  • include: servers.mcsv.net

Threat-feed evidence

History

Related pages

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