Skip to content

Hostname

springandsummer.lk

Last fetched

springandsummer.lk is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. springandsummer.lk is listed by 1 threat feed; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

Listed by 1 threat feed. Advisory: url-scoped-listing.

Threat feeds listing this
1
Verdict coverage
known-clean
First seen on a feed
Wed, 26 Aug 2026 14:51:26 GMT
Last seen on a feed
Thu, 10 Sep 2026 19:53:23 GMT

Nutrition Label

WHISPER CANON · springandsummer.lkRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings8.0/10WHOIS transparency0.0/10Resolver footprint4.0/10canon.whisper.security/host/springandsummer.lk

Resolution chain

No IPv4 resolution is recorded for springandsummer.lk in WhisperGraph.

IPv6 resolution

No AAAA record for springandsummer.lk is recorded in WhisperGraph.

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for springandsummer.lk. 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
cpanel.springandsummer.lk
mail.springandsummer.lk
webmail.springandsummer.lk
www.springandsummer.lk

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.orbitnet.org
  • ns2.orbitnet.org
  • ns3.orbitnet.org

MX records

  • mail.springandsummer.lk

SPF policy

  • include: websitewelcome.com
  • include: relay.mailchannels.net
  • ip: 50.87.235.85
  • ip: 72.9.156.11
  • ip: 72.9.156.13

Threat-feed evidence

History

Related pages

Pivot from springandsummer.lk 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: "springandsummer.lk"})-[: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.