Skip to content

Hostname

quandoo.com

Last fetched

quandoo.com resolves to 108.128.138.231, announced in 108.128.0.0/13 by AMAZON-02 - Amazon.com, Inc. in IE. quandoo.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 · quandoo.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/quandoo.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:151
Registrant organisation
philipp magin
Contact emails
finance.it@quandoo.de, info@domain-contact.org

Subdomains

Subdomain
9100-api.quandoo.com
9110-api.quandoo.com
9120-api.quandoo.com
admin.quandoo.com
auth.quandoo.com
autodns.quandoo.com
aws.quandoo.com
b2b.quandoo.com
book-service.quandoo.com
book.quandoo.com
booking-widget.quandoo.com
brewdog.quandoo.com

Showing 12 of 81. View all subdomains →

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

  • ns-318.awsdns-39.com
  • ns-950.awsdns-54.net
  • ns-1242.awsdns-27.org
  • ns-1594.awsdns-07.co.uk

MX records

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

SPF policy

  • include: email.freshservice.com
  • include: _spf.google.com
  • include: aspmx.pardot.com
  • include: _spf.salesforce.com
  • include: indivsurvey.de
  • include: _spf.atlassian.net
  • include: de._spf.fagms.net
  • include: 7294887.spf07.hubspotemail.net
  • include: infosecmail.net

Threat-feed evidence

History

Related pages

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