Skip to content

Hostname

preservationhall.com

Last fetched

preservationhall.com resolves to 138.197.58.238, announced in 138.197.56.0/22 by DIGITALOCEAN-ASN - DigitalOcean, LLC in US. preservationhall.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 · preservationhall.comRouting diversity1.5/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/preservationhall.com

Resolution chain

IPv6 resolution

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

Attribution

digitalocean

ORIGIN_AS

WHOIS identity

Registrar
iana:2
Registrant organisation
perfect privacy,
Contact emails
cy5q55t49dz@networksolutionsprivateregistration.com, dr9q79t93y2@networksolutionsprivateregistration.com, em6vs8bp99v@networksolutionsprivateregistration.com, info@preservationhall.com, jh8a394e6uz@networksolutionsprivateregistration.com, kq46n5en5ej@networksolutionsprivateregistration.com, nc8ge7t46we@networksolutionsprivateregistration.com, qx9nf2gm4yt@networksolutionsprivateregistration.com, ron@preservationhall.com, ws77e9ry6ab@networksolutionsprivateregistration.com, z33zp22k96x@networksolutionsprivateregistration.com

Subdomains

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • ns89.worldnic.com
  • ns90.worldnic.com

MX records

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

SPF policy

  • include: efax.com
  • include: _spf.google.com
  • mx: preservationhall.com
  • include: _spf.salesforce.com
  • include: 45.55.48.206

Threat-feed evidence

History

Related pages

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