Skip to content

Hostname

doc.lk

Last fetched

doc.lk resolves to 13.213.238.130, announced in 13.212.0.0/15 by AMAZON-02 - Amazon.com, Inc. in SG. doc.lk 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 · doc.lkRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.3/10canon.whisper.security/host/doc.lk

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for doc.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
app.doc.lk
blog.doc.lk
chanit-healthmart.doc.lk
cphm.doc.lk
demo.doc.lk
ext.doc.lk
frame.doc.lk
healthguard-healthmart.doc.lk
healthmart.doc.lk
healthmartsub.doc.lk
homecare.doc.lk
info.doc.lk

Showing 12 of 32. 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-484.awsdns-60.com
  • ns-575.awsdns-07.net
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net
  • ns-1332.awsdns-38.org
  • ns-1763.awsdns-28.co.uk

MX records

  • doc-lk.mail.protection.outlook.com

SPF policy

  • ip: 52.202.192.107/32
  • include: spf.protection.outlook.com

Threat-feed evidence

History

Related pages

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