Skip to content

Hostname

converse.sg

Last fetched

converse.sg resolves to 151.101.1.91, announced in 151.101.0.0/22 by FASTLY - Fastly, Inc. in CA. converse.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 · converse.sgRouting diversity1.5/10Peering density8.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/converse.sg

Resolution chain

IPv6 resolution

No AAAA record for converse.sg is recorded in WhisperGraph.

Attribution

Fastly

cdn · ORIGIN_AS, CDN

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for converse.sg. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Subdomain
aws-staging.converse.sg
bo-aws-staging.converse.sg
bo-pentest.converse.sg
bo-prod.converse.sg
pentest.converse.sg
prod.converse.sg
staging.converse.sg
www.converse.sg

Showing 8 of 8 subdomains (8 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.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • ns-v1.nike.com
  • ns-v2.nike.com
  • ns-v3.nike.com
  • ns-v4.nike.com

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

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

Threat-feed evidence

History

Related pages

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