Skip to content

Hostname

post.how

Last fetched

post.how resolves to 95.216.109.126, announced in 95.216.0.0/16 by HETZNER-AS - Hetzner Online GmbH in FI. post.how 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 · post.howRouting diversity1.5/10Peering density8.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/post.how

Resolution chain

IPv6 resolution

No AAAA record for post.how is recorded in WhisperGraph.

Attribution

hetzner

ORIGIN_AS

WHOIS identity

Registrar
iana:1861
Registrant organisation
inlink
Contact emails
abuse@private.design

Subdomains

Subdomain
autoconfig.post.how
dav.post.how
imap.post.how
mail.post.how
mta-sts.post.how
ns.post.how
pop3.post.how
smtp.post.how
www.post.how

Showing 9 of 9 subdomains (9 per page).

Mail and authentication

Nameservers

  • ns.inlink.ee
  • ns.inlink.eu
  • ns.inlink.ltd
  • ns.inlink.one

MX records

  • mx.inlink.eu

SPF policy

  • redirect: _spf.post.io

Threat-feed evidence

History

Related pages

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