Skip to content

Hostname

wheresmysuitcase.com

Last fetched

wheresmysuitcase.com resolves to 104.18.28.94, announced in 104.18.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. wheresmysuitcase.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 · wheresmysuitcase.comRouting diversity2.4/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint5.6/10canon.whisper.security/host/wheresmysuitcase.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:468
Registrant organisation
baggage airling guest services
Contact emails
tcummings@airportbags.com, dataprivacyprotected@1und1.de, 11320389-4cc0-4534-8e82-f7ca6120c792@identity-protect.org, 2d87d3a6-aa88-4803-81cf-6910400f9bf6@identity-protect.org, 887d2d24-ac06-4c4a-bee9-e42e5f188985@identity-protect.org, 8881637b-0eb6-460f-94f1-cb4b130d7774@identity-protect.org, cdcfb395-21f4-4247-b6b4-1e8784e3647f@identity-protect.org, f0a853ad-8ff4-4561-9a47-7151fd141d17@identity-protect.org, owner-8253732@wheresmysuitcase.com.whoisprivacyservice.org

Subdomains

Showing 1 of 1 subdomain (1 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.

Mail and authentication

Nameservers

  • ns-29.awsdns-03.com
  • piper.ns.cloudflare.com
  • trey.ns.cloudflare.com
  • ns-716.awsdns-25.net
  • ns-1497.awsdns-59.org
  • ns-1687.awsdns-18.co.uk

MX records

  • mxa-000f7c01.gslb.pphosted.com
  • mxb-000f7c01.gslb.pphosted.com

SPF policy

  • include: _u.wheresmysuitcase.com._spf.dmarclj.com

Threat-feed evidence

History

Related pages

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