Skip to content

Hostname

singersl.com

Last fetched

singersl.com resolves to 45.60.47.4, announced in 45.60.47.0/24 by INCAPSULA - Incapsula Inc in GB. singersl.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 · singersl.comRouting diversity1.5/10Peering density9.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint6.3/10canon.whisper.security/host/singersl.com

Resolution chain

IPv6 resolution

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

Attribution

incapsula

ORIGIN_AS

WHOIS identity

Registrar
iana:2
Registrant organisation
singer (sri lanka) limited.
Contact emails
kapilap@singersl.com, singerit@sri.lanka.net

Subdomains

Subdomain
autodiscover.singersl.com
mail.singersl.com
sinmail.singersl.com
www.singersl.com

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

  • ns1-04.azure-dns.com
  • ns4-04.azure-dns.info
  • ns2-04.azure-dns.net
  • ns0.dialogbb.net
  • ns1.dialogbb.net
  • ns1.dialogsl.net
  • ns2.dialogsl.net
  • ns3-04.azure-dns.org

MX records

  • d225775a.ess.barracudanetworks.com
  • d225775b.ess.barracudanetworks.com

SPF policy

  • ip: 203.189.69.123/32
  • ip: 149.72.82.124/32
  • ip: 123.231.24.14/32
  • ip: 203.189.68.154/32
  • ip: 203.189.68.158/32
  • ip: 54.254.19.35/32
  • ip: 123.231.24.9/32
  • include: amazonses.com
  • include: spf.ess.barracudanetworks.com
  • include: spf.protection.outlook.com
  • a: singersl.com
  • mx: singersl.com
  • include: in-iwc-spf.icewarpcloud.in
  • include: sendgrid.net
  • ip: 185.108.31.216

Threat-feed evidence

History

Related pages

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