Skip to content

Hostname

posterlounge.no

Last fetched

posterlounge.no resolves to 93.191.49.173, announced in 93.191.48.0/21 by NETBUILD-AS - Net-Build GmbH in DE. posterlounge.no 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 · posterlounge.noRouting diversity1.5/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.0/10canon.whisper.security/host/posterlounge.no

Resolution chain

IPv6 resolution

Attribution

net build

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for posterlounge.no. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Subdomain
gtm.posterlounge.no
hp.posterlounge.no
image.posterlounge.no
pc.posterlounge.no
wildcard.posterlounge.no
www.posterlounge.no

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

Mail and authentication

Nameservers

  • ns1.net-server.de
  • ns2.net-server.de
  • 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

MX records

  • posterlounge-no.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com
  • include: mail.zendesk.com

Threat-feed evidence

History

Related pages

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