Skip to content
Install MCP

Hostname

sdphysio.com

Last fetched

sdphysio.com resolves to 156.38.175.47, announced in 156.38.128.0/17 by Xneelo (Pty) Ltd - Xneelo (Pty) Ltd in ZA. sdphysio.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 · sdphysio.comRouting diversity1.5/10Peering density5.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/sdphysio.com

Resolution chain

IPv6 resolution

No AAAA record for sdphysio.com is recorded in WhisperGraph.

Attribution

xneelo

ORIGIN_AS

WHOIS identity

Registrar
iana:2287
Registrant organisation
register domain
Contact emails
domains@mrsite.co.uk

Subdomains

Subdomain
autodiscover.sdphysio.com
ftp.sdphysio.com
mail.sdphysio.com
pop.sdphysio.com
smtp.sdphysio.com
webmail.sdphysio.com
www.sdphysio.com

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

  • ns2.cbdns.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
  • ns1.cbdns.co.za
  • ns2.cbdns.co.za
  • ns3.cloudbay.co.za

MX records

  • sdphysio-com.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com
  • a: sdphysio.com
  • mx: sdphysio.com
  • include: _spf.cloudbay.co.za
  • ip: 156.38.175.47

Threat-feed evidence

History

Related pages

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