The service uses domain input, public DNS or transport data, and temporary live-test data when requested.
Privacy & Terms
This page explains what data Tehnoguru uses, how the site operates, and the basic rules that apply to checks, monitoring, and portal access.
What this page covers
Inquiry details, invite data, report recipients, and account data are used to deliver monitoring and control portal access.
Only scan or test domains that you own, manage, or are authorised to review.
Data used for checks and tests
The service keeps data collection narrow and tied to the requested check, test, or monitoring activity.
- Public checks use the domain you enter together with related public DNS and transport records.
- Live delivery tests create a temporary address and may retain the delivered message plus technical analysis for the lifetime of the test and operational review.
- Managed onboarding and monitoring use inquiry details, invite data, report recipients, and account-access data.
Cookies and site operation
The current public site uses necessary first-party cookies only.
- csrftoken protects forms and checker actions against cross-site request forgery.
- sessionid keeps signed-in portal sessions active.
- django_language remembers an explicit language choice.
Acceptable use
Only scan or test domains that you own, manage, or are authorised to review. Paid monitoring starts after onboarding and confirmation; it is not instant self-serve checkout.
Portal access and responsibility
Portal access is limited to approved customer users and internal operators. Results are intended to support review and implementation decisions, but final changes still need to be validated in your own environment.
Need a follow-up?
Use the monitoring request path if you need follow-up on privacy, access, or onboarding.
- No analytics or marketing trackers are enabled on the current public site.
- Monitoring activation and billing are handled during onboarding.