Skip to content

Hostname

samuseum.org

Last fetched

samuseum.org is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. samuseum.org 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 · samuseum.orgRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/samuseum.org

Resolution chain

No IPv4 resolution is recorded for samuseum.org in WhisperGraph.

IPv6 resolution

No AAAA record for samuseum.org is recorded in WhisperGraph.

WHOIS identity

Registrar
iana:1068
Registrant organisation
marcus felan
Contact emails
gndvygfmy@whoisprivacyprotect.com, hstwvpjm@whoisprivacyprotect.com, qffwyghh@whoisprivacyprotect.com, rdpdvlvf@whoisprivacyprotect.com, wpgkntvy@whoisprivacyprotect.com, yfhflxjt@whoisprivacyprotect.com, marcus.felan@samuseum.org, polly.vidaurri@samuseum.org

Subdomains

Subdomain
esxi1.samuseum.org
esxi2.samuseum.org
filecloud.samuseum.org
shop.samuseum.org
vcenter.samuseum.org
www.samuseum.org

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

  • dns1.registrar-servers.com
  • dns2.registrar-servers.com

MX records

  • mx1-us1.ppe-hosted.com
  • mx2-us1.ppe-hosted.com

SPF policy

  • ip: 192.124.249.15/32
  • ip: 162.209.11.172/32
  • include: spf.constantcontact.com
  • include: spf-us.letsignit.com
  • include: spf.protection.outlook.com
  • a: dispatch-us.ppe-hosted.com
  • include: outboundmail.blackbaud.net

Threat-feed evidence

History

Related pages

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