Skip to content

Hostname

bemyguest.com.sg

Last fetched

bemyguest.com.sg resolves to 13.213.111.137, announced in 13.212.0.0/15 by AMAZON-02 - Amazon.com, Inc. in SG. bemyguest.com.sg 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 · bemyguest.com.sgRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint4.6/10canon.whisper.security/host/bemyguest.com.sg

Resolution chain

IPv6 resolution

No AAAA record for bemyguest.com.sg is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:1376
Registrant organisation
silicon dot pte. ltd. (sgnic-org1391154)

Subdomains

Subdomain
agents.bemyguest.com.sg
agents1.bemyguest.com.sg
agentsapidemo.bemyguest.com.sg
agentsdaryle.bemyguest.com.sg
agentsdemo.bemyguest.com.sg
alldreamscambodia.bemyguest.com.sg
angkornationalmuseum.bemyguest.com.sg
api.bemyguest.com.sg
apiapidemo.bemyguest.com.sg
apidemo.bemyguest.com.sg
apidemodashboard.bemyguest.com.sg
apidemowebsite.bemyguest.com.sg

Showing 12 of 59. 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-500.awsdns-62.com
  • ns-664.awsdns-19.net
  • ns-1295.awsdns-33.org
  • ns-1569.awsdns-04.co.uk

MX records

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

SPF policy

  • ip: 54.251.210.11/32
  • ip: 175.41.173.72/32
  • include: _spf.google.com
  • a: bemyguest.com.sg
  • mx: bemyguest.com.sg

Threat-feed evidence

History

Related pages

Pivot from bemyguest.com.sg 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: "bemyguest.com.sg"})-[: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.