Skip to content

Hostname

placenames.website

Last fetched

placenames.website resolves to 64.190.63.222, announced in 64.190.62.0/23 by SEDO-AS - SEDO GmbH in DE. placenames.website 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 · placenames.websiteRouting diversity2.4/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint9.5/10canon.whisper.security/host/placenames.website

Resolution chain

IPv6 resolution

No AAAA record for placenames.website is recorded in WhisperGraph.

Attribution

sedo

ORIGIN_AS

WHOIS identity

Registrar
iana:303
Registrant organisation
privacy protection

Subdomains

Subdomain
hostmaster.placenames.website
mail.placenames.website
wildcard.placenames.website
www.placenames.website

Showing 4 of 4 subdomains (4 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

  • ns1.sedoparking.com
  • ns2.sedoparking.com
  • ns01.trs-dns.com
  • ns10.trs-dns.info
  • firstbytedns.net
  • ns1.firstbytedns.net
  • ns2.firstbytedns.net
  • ns3.firstbytedns.net
  • 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
  • ns01.trs-dns.net
  • ns10.trs-dns.org
  • ns1.firstbytedns.ru
  • ns2.firstbytedns.ru
  • ns3.firstbytedns.ru

MX records

  • mail.placenames.website

Threat-feed evidence

History

Related pages

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