Sample summary
The domain resolves to a public hosting or CDN edge, publishes mail-related DNS records and should be reviewed together with SSL, HTTP and DNSSEC signals before drawing conclusions.
Sample report
Domain intelligence example report for DNS, ownership, routing and mail evidence.
This sample shows how OsintNET can structure a domain investigation into evidence layers: DNS records, RDAP/WHOIS context, ASN/BGP routing, SSL certificate clues, SPF, DMARC, DNSSEC and HTTP signals.
Designed for analysts who need clear signals, not scattered tabs.
Evidence table
A report should preserve each observed value, source category, confidence and interpretation so another analyst can reproduce or challenge the finding.
Recommended next steps
Review SPF and DMARC policy strength, confirm DNSSEC status, compare certificate names, inspect HTTP headers and pivot into website risk scanning if the target is authorized.
Common questions
What should a domain intelligence report include?
A useful report should include DNS records, ownership context, ASN and routing clues, SSL certificate evidence, SPF, DMARC, DNSSEC, HTTP posture and clear limitations.
Does this example prove risk?
No. It demonstrates report structure. Real findings should be verified against current records and interpreted in the authorization context.
Continue with the next evidence layer.
SPF, DMARC and DNSSEC checker
Focus on the mail-security and DNS validation layer inside the domain report.
Website risk example report
Continue from domain evidence into headers, TLS, cookies and CORS posture.
Domain Intelligence Guide
Read the methodology behind the sample report.
Start investigation
Use OsintNET to convert public signals into structured evidence.
Pick the module that matches your target and keep each clue connected to its source, confidence and investigation context.