Skip to content

Hostname

guestdesk.com

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

Google

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:146
Registrant organisation
******** ******** (see notes section below on how to view unmasked data)
Contact emails
********@*****.***, domains@fuelinteractive.com

Subdomains

Subdomain
iqware.guestdesk.com
media.guestdesk.com
reservations.guestdesk.com
search.guestdesk.com
secure.guestdesk.com
support.guestdesk.com
widgets.guestdesk.com
www.guestdesk.com

Showing 8 of 8 subdomains (8 per page).

Mail and authentication

Nameservers

  • jason.ns.cloudflare.com
  • kara.ns.cloudflare.com
  • 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

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com

SPF policy

  • ip: 69.63.135.0/25
  • ip: 69.63.130.197/32
  • ip: 69.63.136.28/32
  • include: amazonses.com
  • include: _spf.google.com
  • include: support.zendesk.com
  • include: sendgrid.net
  • ip: 69.63.133.122

Threat-feed evidence

History

Related pages

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