Skip to content

Hostname

profile.amsterdam

Last fetched

profile.amsterdam resolves to 176.62.170.23, announced in 176.62.160.0/20 by COMBELL-AS - Combell NV in BE. profile.amsterdam 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 · profile.amsterdamRouting diversity1.5/10Peering density2.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/profile.amsterdam

Resolution chain

IPv6 resolution

No AAAA record for profile.amsterdam is recorded in WhisperGraph.

Attribution

combell

ORIGIN_AS

WHOIS identity

Registrar
iana:2288
Registrant organisation
marcel willems
Contact emails
marcel.willems@profile.nl

Subdomains

Showing 1 of 1 subdomain (1 per page).

Mail and authentication

Nameservers

  • nsn1.mijndomein.nl
  • nsn2.mijndomein.nl

SPF policy

  • ip: 2a00:4e40:1:1::7:1/120
  • ip: 188.93.144.85/22
  • a: profile.amsterdam
  • mx: profile.amsterdam
  • include: _spf.relay.mailprotect.be

Threat-feed evidence

History

Related pages

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