Skip to content

Hostname

managedhosting.partners

Last fetched

managedhosting.partners resolves to 13.226.244.111, announced in 13.226.244.0/22 by AMAZON-02 - Amazon.com, Inc. in DE. managedhosting.partners 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 · managedhosting.partnersRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/managedhosting.partners

Resolution chain

IPv6 resolution

No AAAA record for managedhosting.partners is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:81
Registrant organisation
automatem
Contact emails
414fb253239ffbc46033ac8bac6d098d-30551820@contact.gandi.net, jd@automatem.co.nz

Subdomains

Subdomain
00000000.managedhosting.partners
api.managedhosting.partners
au.managedhosting.partners
aus1h2.managedhosting.partners
cdn.managedhosting.partners
dev1.managedhosting.partners
help.managedhosting.partners
mgr.managedhosting.partners
mgr2.managedhosting.partners
mgr3.managedhosting.partners
ns1.managedhosting.partners
ns2.managedhosting.partners

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

  • ns-53.awsdns-06.com
  • ns-872.awsdns-45.net
  • ns-1202.awsdns-22.org
  • ns-2015.awsdns-59.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com

SPF policy

  • ip: 52.65.73.113/32
  • include: _spf.google.com

Threat-feed evidence

History

Related pages

Pivot from managedhosting.partners 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: "managedhosting.partners"})-[: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.