Skip to content

Hostname

wheresthebus.com

Last fetched

wheresthebus.com resolves to 100.49.106.29, announced in 100.48.0.0/12 by AMAZON-AES - Amazon.com, Inc. in US. wheresthebus.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 · wheresthebus.comRouting diversity1.5/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/wheresthebus.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of wheresthebus.com owner
Contact emails
wheresthebus.com@domainsbyproxy.com, 17b20380-6a40-4de0-b975-2b0995e20162@identity-protect.org, bfcddc8e-3d79-482c-94d6-8764793283f3@identity-protect.org, f5a821f3-3610-4b1b-bc0f-b25a58fe698d@identity-protect.org, owner-9891219@wheresthebus.com.whoisprivacyservice.org

Subdomains

Subdomain
api.wheresthebus.com
mdt.wheresthebus.com
prepro.wheresthebus.com
stage.wheresthebus.com
www.wheresthebus.com

Showing 5 of 7. 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

Sample outbound links

Mail and authentication

Nameservers

  • ns-494.awsdns-61.com
  • ns-814.awsdns-37.net
  • ns-1045.awsdns-02.org
  • ns-1800.awsdns-33.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com
  • wheresthebus-com.mail.protection.outlook.com

SPF policy

  • include: amazonses.com
  • include: _spf.google.com
  • include: mail.zendesk.com

Threat-feed evidence

History

Related pages

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