iblue.team valid
Digital Forensics & Incident Response
- Authority
- 46 reach 0 · trust 10 · quality 21 · freshness 15
- Tier
- listed
- llms.txt
- https://www.iblue.team/llms.txt
- llms-full.txt
- https://www.iblue.team/llms-full.txt
- Sections
- 1
- Links
- 104
- Size
- 16215 bytes
- Registered
- 2020-09-19
- Country
- — Publisher location unknown; CDN address excluded
- Country evidence
- No published address evidence collected yet
- Categories
- Developer tools · Infrastructure
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-27T13:33:24.805Z
- Last checked
- 2026-10-27T13:33:27.662Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-27T13:33:24.828Z. Cached copy · Source on iblue.team
# Digital Forensics & Incident Response
## iBlueTeam
- [Welcome](https://www.iblue.team/readme.md)
- [Independent Investigations - BEC](https://www.iblue.team/general-notes-1/independent-investigations-bec.md): Independent Investigation vs MSP/MSSP Self-Investigation in BEC Matters
- [The Reasonable Investigation Standard](https://www.iblue.team/general-notes-1/the-reasonable-investigation-standard.md)
- [Retaining Original Exhibits](https://www.iblue.team/general-notes-1/retaining-original-exhibits.md): Disclaimer: I'm not a lawyer. Seek legal advice or consult your internal Legal/HR department to understand your organisation's or country's legislative or procedural requirements.
- [Azure Blob storage with NGINX proxy](https://www.iblue.team/general-notes-1/azure-blob-storage-with-nginx-proxy.md): Create an NGINX proxy and stick it in front of your Azure Blob storage so you can use Crowdstrike RTR to its full potential, bypassing restrictive file size limits and artificial bandwidth limitations
- [Install and Configure ZeroTier client](https://www.iblue.team/general-notes-1/install-and-configure-zerotier-client.md): ZeroTier creates secure networks between on-premise, cloud, desktop, and mobile devices.
- [S3FS Fuse and MinIO](https://www.iblue.team/general-notes-1/s3fs-fuse-and-minio.md)
- [Enable nested VT-X/AMD-V](https://www.iblue.team/general-notes-1/enable-nested-vt-x-amd-v.md)
- [mitm proxy](https://www.iblue.team/general-notes-1/mitm-proxy.md)
- [Exploring Volume Shadow Copies Manually](https://www.iblue.team/general-notes-1/exploring-volume-shadow-copies-manually.md): How to explore volume shadow copies manually with opensource tools
- [Resize VMDK/VDI](https://www.iblue.team/general-notes-1/resize-vmdk-vdi.md)
- [Resize VMDK on ESXi](https://www.iblue.team/general-notes-1/resize-vmdk-on-esxi.md): You've created a Linux guest VM on ESXi, but now it's outgrown its original storage requirements and you need to resize it.
- [Convert raw to vmdk](https://www.iblue.team/general-notes-1/convert-raw-to-vmdk-for-virtual-machine.md)
- [Favicon hashing and hunting with Shodan](https://www.iblue.team/general-notes-1/favicon-hashing-and-hunting-with-shodan.md)
- [WinRM/RemotePS](https://www.iblue.team/general-notes-1/winrm-remoteps.md)
- [MinIO/S3/R2 ghost files](https://www.iblue.team/general-notes-1/minio-s3-r2-ghost-files.md): Sometimes a multi-part upload will fail and result in ghost files. Your bucket will indicate it has contents/cannot be deleted, but you can't see anything.
- [Mount E01 containing VMDK/XFS from RHEL system](https://www.iblue.team/general-notes-1/mount-e01-containing-vmdk-xfs-from-rhel-system.md): You're provided with an E01 of a VMDK from a RedHat Enterprise Linux system, which is formatted using XFS and is part of an LVM group.
- [Disk images for various filesystems and configurations](https://www.iblue.team/general-notes-1/disk-images-for-various-filesystems-and-configurations.md)
- [ext4 with LVM and RAID5 (3 disks)](
…Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| belkasoft.com | Belkasoft: Intelligent Software for Digital Forensics and Cyber Incident Response | documentation Cybersecurity | US | 56 | ✓ | ||
| autopsy.com | Autopsy: Digital Forensics | documentation Cybersecurity | US | 56 | ✓ | ||
| archerhall.com | Archerhall: Archerhall | documentation Cybersecurity | — | 46 | ✓ | ||
| cybertriage.com | Cyber Triage: Digital Forensics Specialized For Rapid Incident Response | documentation Cybersecurity | US | 51 | ✓ | ||
| breached.company | Breached Company | transactional Cybersecurity Media | — | 55 | ✓ | ✓ | |
| cynergytech.com | Cynergy Technology | informational Cybersecurity Infrastructure | US | 46 | ✓ | ||
| adfsolutions.com | ADF Solutions | transactional Cybersecurity | — | 51 | ✓ | ||
| crowdertech.com.br | Crowdertech | informational Cybersecurity | BR | 46 | ✓ |
Machine-readable: GET /v1/resolve?q=iblue.team · GET /v1/domain/iblue.team · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage iblue.team, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for iblue.team:
1. POST https://agentwebmap.com/v1/sites/iblue.team/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://iblue.team/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/iblue.team/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/iblue.team).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.