Skip to content

Hostname

placetel.com

Last fetched

placetel.com resolves to 35.198.84.207, announced in 35.198.80.0/20 by GOOGLE-CLOUD-PLATFORM - Google LLC in DE. placetel.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 · placetel.comRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/placetel.com

Resolution chain

IPv6 resolution

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

Attribution

Google

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
cisco technology
Contact emails
infosec@cisco.com, info@placetel.de, 607852a3ad0a1258a808f85881a5e4ee-4380362@contact.gandi.net, 0315cb67-b2b8-43f7-a5de-860cb456796d@identity-protect.org

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

  • ns-69.awsdns-08.com
  • ns-764.awsdns-31.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
  • ns-1454.awsdns-53.org
  • ns-1796.awsdns-32.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • include: _spf.google.com
  • ip: 185.79.25.13
  • ip: 185.79.25.137
  • ip: 185.79.26.10
  • ip: 185.79.26.13
  • ip: 185.79.26.14
  • ip: 185.79.27.10
  • ip: 185.79.27.13
  • ip: 185.79.27.14

Threat-feed evidence

History

Related pages

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