Skip to content

Hostname

redbus.com

Last fetched

redbus.com resolves to 11 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in SG. WHOIS lists iana:1011 as the registrar.

Nutrition Label

WHISPER CANON · redbus.comRouting diversity4.8/10Peering density9.3/10MOAS conflict✓ noneThreat-feed listings6.8/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/redbus.com

Resolution chain

redbus.com resolves to 11 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.

IPPrefixASNOperatorCountry
13.214.253.14513.214.0.0/15AS16509AMAZON-02 - Amazon.com, Inc.SG
18.136.84.16818.136.0.0/16AS16509AMAZON-02 - Amazon.com, Inc.SG
18.143.71.9218.142.0.0/15AS16509AMAZON-02 - Amazon.com, Inc.SG
3.0.33.2113.0.0.0/15AS16509AMAZON-02 - Amazon.com, Inc.SG
3.1.15.1373.0.0.0/15AS16509AMAZON-02 - Amazon.com, Inc.SG
52.220.216.24652.220.0.0/15AS16509AMAZON-02 - Amazon.com, Inc.SG
52.220.239.13052.220.0.0/15AS16509AMAZON-02 - Amazon.com, Inc.SG
52.77.67.18052.77.0.0/16AS16509AMAZON-02 - Amazon.com, Inc.SG
47.130.82.23947.128.0.0/14AS16509AMAZON-02 - Amazon.com, Inc.SG
47.131.162.10447.128.0.0/14AS16509AMAZON-02 - Amazon.com, Inc.SG
54.254.53.13554.254.0.0/17AS16509AMAZON-02 - Amazon.com, Inc.SG

WHOIS identity

Registrar
iana:1011
Organization
ibibo group pte.
Contact emails

Subdomains

43 observed subdomains of redbus.com.

Web-graph footprint

Distinct hostnames that link to or from redbus.com in the public web crawl.

116 sites link to this hostname.

Threat posture

History

Mail and authentication

SPF policy

12 SPF mechanisms authorising senders for redbus.com.

MechanismTarget
SPF_INCLUDE_spf.google.com
SPF_INCLUDEamazonses.com
SPF_INCLUDEspf1.redbus.com
SPF_IP122.15.80.201
SPF_IP13.126.83.17
SPF_IP13.251.58.206
SPF_IP202.54.232.150
SPF_IP209.85.220.69/32
SPF_IP54.240.47.39
SPF_IP54.240.47.40
SPF_IP54.240.47.41
SPF_IP65.1.209.68

Related pages

Pivot deeper into the graph from redbus.com.

Cypher and MCP

Reproduce the resolution chain directly against graph.whisper.security:

MATCH (h:HOSTNAME {name: "redbus.com"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
      -[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.