Everything we get asked. In one place.

Three things: First, we build custom — firewall, network, cameras, servers exactly the way your business needs them, instead of selling flat-rate packages. Second, you talk directly to the people who know your infrastructure. Third, we don't stop after installation — with full service including monitoring, maintenance and hardware replacement. Over 300 switches are running at our customers today.

Primarily SMBs and mid-sized companies — from office locations through retail and manufacturing to corporate groups with multiple sites. We build what each business really needs: from a single network cabinet to complete site infrastructure with firewall, WiFi and video surveillance.

Honestly, it depends on the scope — a single network cabinet is a different story than a complete site with firewall, WiFi and cameras. That's why we start with a free, no-obligation initial consultation: we look at your situation and you get a concrete offer without hidden line items. You know exactly what it costs before anything starts.

It gets replaced. With a full-service agreement, we take care of the complete replacement of defective devices — so your business doesn't stand still. On top of that, continuous monitoring lets us fix many problems before you even notice them.

Yes. We start with an inventory: what's installed, what works, where the risks are. Then we document your infrastructure cleanly and modernize step by step — no big bang and no downtime for your business.

Our servers are in Bratislava (Slovakia) and Belgrade (Serbia). Both locations are built redundantly and monitored continuously, and there is a recovery plan for the worst case. Bratislava is inside the EU — if your data should not leave the EU area, we plan for that accordingly.

Yes. Alongside infrastructure, we develop custom software — from monitoring systems to AI-powered object detection for camera systems. The interplay is our advantage: hardware, network and software from a single source, without interface ping-pong between multiple providers.

An office network is built for laptops, printers and email, not for machine controllers that have run on the same operating system for years. Production floors add dust, temperature swings and vibration that standard network hardware is not built to handle. NDVDL plans the production network and the office network as separate areas with their own hardware.

Through dedicated VLANs for machines and office IT, plus a firewall that controls traffic between the two areas. That way a problem in the office network, such as an infected email, cannot spread unchecked into the machine controllers.

Metal racking, steel structures and the sheer size of the hall weaken the signal in spots that are often overlooked during planning. NDVDL maps the hall's actual geometry and places access points where scanners, tablets and forklifts genuinely operate.

Access is set up specifically for each maintenance case and closed again afterwards, rather than staying open indefinitely. That keeps a record of which vendor had access to which controller and when.

Yes, NDVDL connects machine controllers and sensors to existing ERP or MES software without replacing those systems. The controller needs to provide an interface for the data exchange.

No, NDVDL has no office in Vienna and instead supports companies in Vienna, Lower Austria and Slovakia through on-site visits and remote support. The company is registered in Bratislava.

It's usually steel racking reflecting or blocking the signal, combined with access points that weren't placed for the racking and aisle layout. On top of that, poorly configured roaming often means devices lose connection when moving between access points instead of handing off smoothly.

Access point placement is planned around the actual racking height, aisle width and materials rather than a fixed grid. Roaming is then configured so handheld scanners and MDE devices stay connected while moving through the aisles.

Standard office equipment isn't built for cold and condensation and fails more often in those conditions. NDVDL uses hardware suited to the conditions for these areas and separates the segment from the rest of the network.

Sites are linked via VPN or SD-WAN so warehouse management and TMS work from the same data across all locations. The right option depends on the number and location of sites and the available internet connection.

Yes, that falls under systems integration: existing warehouse management and transport management systems are connected to customer systems through interfaces or EDI. Existing software stays in use rather than being replaced.

Cameras on a company site often capture drivers, hauliers and third-party staff who aren't employed by the business – that calls for careful planning of capture zones and notices. NDVDL advises on setting up camera systems at gates, ramps and the yard in line with data protection requirements.

Through a VPN that connects every branch to head office using the same configuration. NDVDL sets this up so a change at head office, such as a new firewall rule, applies automatically to every location instead of having to be repeated store by store.

Yes – sharing a network is usually why they fail together. An overloaded or infected customer Wi-Fi can otherwise affect the till and payment terminal directly, which is why NDVDL keeps the two networks technically separate.

Generally yes, as long as the camera covers the till area or stockroom and changing rooms and staff rooms are excluded. NDVDL plans camera placement, signage and retention period together with the business so there is a documented basis for it.

Because the network and POS system are under the heaviest load on the busiest days, which is when an existing problem tends to surface first. Monitoring and remote support catch many of these issues before they take down the till on a high-traffic day.

Yes, through an interface between inventory management and the online shop or marketplace. NDVDL sets this up so a sale in-store updates the stock shown online, and the other way round.

Network connection to head office, separation of POS and customer Wi-Fi, and camera placement, so the branch runs on the same pattern as every other location from opening day. NDVDL plans these points before the branch opens rather than adding them afterwards.

Yes, it should be. A dedicated VLAN with a captive portal for guests stops guest devices from reaching the POS system, payment terminals or office computers, and it limits the operator's liability if something goes wrong on the guest network.

Usually it comes down to thick walls in period or listed buildings that block a single router's signal. Coverage from several well-placed access points solves this, even where cable routes are limited by heritage rules.

Technically yes, but it is not advisable. Payment terminals should sit on their own separated network segment, so they cannot be reached from guest devices or from a compromised office computer.

Generally not, without strict limits. Dining rooms and staff areas are sensitive under data protection rules, so cameras typically belong at entrances, storage areas and outdoor spaces, where a legitimate interest is easier to justify.

Access to Wi-Fi, the POS system and booking software should be granted for a set period and actively withdrawn once the season ends, rather than left active by default. NDVDL sets up network and systems so access rights can be tracked and managed.

Without separated network segments and proper network planning, a single fault can take down the POS system, bookings and guest Wi-Fi together, often on a weekend or during peak season when nobody can step in quickly. NDVDL designs networks so individual areas keep working independently and sets up ongoing support that covers hours outside the business's own opening times.

Yes, guest Wi-Fi should be built as its own isolated network with no access to practice software or patient data. This is typically done using a separate VLAN or its own internet connection, so a device in the waiting room can never reach the practice network.

Medical devices are best placed on their own network zone, separate from the practice and guest networks, because many run older operating systems that no longer receive updates. That keeps an outdated device technically isolated instead of becoming a gateway into the whole network.

Access to patient data should be assigned by role, so reception staff have different rights than treatment staff, for example. NDVDL sets up this tiered access technically and documents who can access what.

No, CCTV belongs at the entrance or reception area, not in treatment rooms. NDVDL plans camera systems only for the publicly accessible areas of a practice.

NDVDL helps document the technical side of the systems in use, which is needed for a data protection impact assessment. The legal assessment itself remains with the practice or its legal advisor; NDVDL provides the technical groundwork for it.

Without a backup and recovery plan, practice software, and with it check-in, scheduling and documentation, stops until the server is repaired or replaced. NDVDL builds backup plans that allow recovery from a current backup.

Through access rights scoped to individual client files rather than the whole practice, combined with logging of every access. Only staff working on a given engagement see the related file, and any access outside that circle can be traced afterwards.

Because they hold client funds, tax records and confidential files, which makes them a particularly attractive target. Fake invoices or emails styled as an internal request from management aim directly at that access.

Instead of emailing documents back and forth, clients and the practice upload and retrieve them through a secured channel. That prevents sensitive files sitting unencrypted in an inbox or being sent to the wrong address.

Both are workable, and the right choice depends on the size of the practice, the software in use and where the data should be hosted. We review the existing setup and show which option fits that particular practice.

It becomes secure through VPN access with multi-factor authentication, rather than exposing practice software directly to the internet. Without that layer, every laptop working from home is a potential way in.

Once NDVDL manages a practice's IT infrastructure, that involves processing personal and client-related data, which needs to be documented. We help document the technical and organisational measures involved; the legal assessment itself stays with the practice or its legal advisor.

Through secured mobile access to the office system, which NDVDL sets up with a firewall and network configuration. Crews see only the data released to them on tablet or phone, the rest of the network stays closed.

With a Wi-Fi coverage plan that places access points according to the actual footprint of the hall, storage and yard rather than a single central router. NDVDL plans coverage so outdoor areas and the back corners of halls are reached too.

That depends on what the cameras are aimed at and how recording is set up. NDVDL aims camera systems at entrances, exits, storage and the vehicle fleet and advises on the data protection limits toward staff, rather than recording everything by default.

Through system integration that technically connects the existing programs rather than replacing them with a new all-in-one system. NDVDL first checks which systems are in use, then builds the interfaces between them.

In a central, secured location that both the office and the site can access, instead of scattered across individual devices. NDVDL builds the server infrastructure for this along with secured access routes from site.

Without a backup in place, they are likely lost, since they often sit only locally or in a single system. NDVDL sets up ongoing backups so quotes, calculations and job data remain available after a failure.

Because workshop, sales and office place different demands on the same network. Diagnostic tools bound by manufacturer requirements, point-of-sale systems in the showroom and guest Wi-Fi for customers would otherwise run over the same line as accounting and customer data. NDVDL designs networks for dealerships and garages that give each of these areas its own, separated segment.

Diagnostic equipment that must run on specific, older operating systems due to manufacturer requirements is placed in its own network segment, isolated from the rest of the IT. That keeps the device usable in line with manufacturer rules without letting an outdated system become an entry point into the wider business. NDVDL handles this separation as part of network design.

Through firewall rules that limit remote access from manufacturers and diagnostic providers to the systems and time windows actually needed. Warranty processing, parts ordering and software updates stay possible without a connection being left open permanently. NDVDL sets up these rules together with the business and documents which access exists for what purpose.

Yes, within data-protection limits that distinguish between business premises, staff areas and publicly accessible customer areas. The yard, vehicle storage, parts storage and wash bay can be protected against theft and damage, while staff break rooms or pure customer walkways cannot simply be filmed without restriction. NDVDL plans camera positions and retention periods so these boundaries are respected from the start.

Appointment booking and workshop intake stop immediately, since both depend on the same running systems. That is why NDVDL provides ongoing support for the network and server infrastructure of dealerships and garages, rather than only responding once a fault is reported. The goal is for intake and scheduling to keep working even when technical problems occur.

Yes, NDVDL connects locations and branch workshops over a shared, secured network foundation, so bookings, customer data and parts management are available centrally. Each site gets the same separation of workshop, sales and guest networks as the main location. That avoids separate, disconnected setups that each need their own maintenance.

Video surveillance in residential buildings, underground car parks or bin rooms is technically possible, but it touches residents' privacy directly and needs a careful assessment of which areas actually need to be filmed. NDVDL advises on the technical options, such as field of view, retention period and access rights, but this is not legal advice on what is permissible in a specific case.

Remote access for technicians servicing heating, ventilation, lifts or other building technology is set up through a firewall so each firm can only reach its own area. NDVDL sets up such access, documents it, and removes it again once it is no longer needed.

An access request can only be answered promptly if it is already clear where tenant data is stored and who can reach it. NDVDL helps bring tenant and owner data out of scattered drives and inboxes into a structured, traceable filing system.

The connection runs through interfaces that NDVDL secures technically within the network, rather than moving credentials or exports uncontrolled between systems. This also defines who within the management team can access which payment data.

NDVDL first records what network, camera systems and access points already exist, even where documentation is missing or incomplete. From there, the IT is organised, secured and maintained going forward, rather than left running unchanged.

Property records such as plans, reports and invoices are shared through a structured, access-controlled system rather than as unencrypted email attachments. NDVDL sets up access so owners and tradespeople each see only what they are meant to see.

Because a compromised or overloaded device on a shared network can also reach administration data or course-management software. NDVDL separates administration, teaching and guests into their own networks, so an incident in one area doesn't spread to the others.

Access rights are assigned so that only authorised people and systems can reach student data, kept separate from the teaching network. NDVDL advises on technical measures such as access control and retention periods, but does not provide legal advice or guarantee legal compliance – that responsibility sits with the institution or its legal counsel.

Yes, through firewall rules and content filters that apply to the teaching network without affecting the administration network. The specific setup depends on the age of the students and the institution's own policies, which NDVDL then implements technically.

Course devices get a uniform baseline configuration that can be reset before each new course, instead of setting up every laptop by hand. This reduces the workload for instructors and ensures every course starts from the same baseline.

NDVDL plans video surveillance only for outdoor and entrance areas, not for teaching rooms. This separation is standard practice when planning education facilities and is applied from the outset.

A properly separated network with stable Wi-Fi coverage reduces the risk of a single fault taking down the whole operation, because administration, teaching and guests run on separate network segments. NDVDL also provides ongoing IT support, so disruptions are caught and fixed before they affect teaching more broadly.

Usually with a wireless bridge, a radio link with direct line of sight between buildings, combined with cable wherever a run is needed anyway. NDVDL plans the link around the actual distances and sightlines on the specific operation.

Barns need network equipment with an ingress protection rating suited to dust and moisture, not standard office hardware. NDVDL selects access points and switches to match the conditions in the specific barn.

These systems are connected as their own segment on the network so they run reliably and a problem elsewhere doesn't take them down too. The connection is planned together with the requirements of the relevant equipment manufacturer.

Access is set up so it only reaches the relevant system and can't reach the rest of the network. That keeps remote maintenance possible without an open access point becoming a risk for the rest of the operation.

Yes, camera systems can be set up for the yard entrance, machinery hall and fuel tank against theft and extended to livestock areas for monitoring barns. Both uses are accounted for when planning capture zones and the GDPR-compliant setup.

Depending on location, the available connection is assessed and backed up with a secondary link so control systems, cameras and business data don't depend entirely on one connection. Business data and subsidy documentation are also protected with backup.

Because a problem on the office network, such as a compromised workstation, would otherwise have a direct path to plant control without separation. NDVDL sets up control systems and the office network as separate segments with controlled crossover points so an incident doesn't spread.

Through a central, secured access point scoped by user and by plant, rather than running a separate isolated setup per site. That keeps access traceable even as sites and users are added.

Depending on location, a cellular or wireless link can provide a baseline connection for remote access and monitoring. Which option fits depends on the distance to the nearest network node and the sightline at the site.

Access is scoped to the specific plant and separated from the rest of the infrastructure, so the manufacturer can perform maintenance without reaching other systems. That applies regardless of how many different manufacturers are involved.

The plant is monitored on metrics such as operating status or output and actively reports deviations instead of these only surfacing at the next review. That shortens the time between a failure and the response.

Metering data is captured from the plant and passed to the existing billing system through an interface, rather than introducing a new system. Requirements for availability and logging of the data transfer depend on the specific plant and billing system.

Outdoor-rated access points are protected against rain, cold and temperature swings and are placed according to the actual size of the site. NDVDL plans coverage so the scale, hall and outdoor storage stay reliably connected on the same network.

Weighbridge software is linked to stock management or billing through an interface so a weighing event is carried through automatically. That reduces manual double entry and mismatches between the weight ticket and the invoice.

Number-plate capture at the entrance is technically possible and is often used to track deliveries. NDVDL advises on capture zones and notices toward drivers and staff, without replacing a legal assessment for the specific case.

Switches, access points and cameras are used in versions rated for dust, vibration and temperature swings instead of improvised office hardware. The server room is also planned to stay separate from the hall and yard.

Yes, mobile devices for drivers and yard staff can be connected to the same network as the scale and billing system. That requires Wi-Fi coverage that also reaches the edges of the outdoor site.

Cameras at the scale, entrance and recyclables storage inevitably also capture drivers and a company's own staff, which calls for clear limits on capture zones and signage. NDVDL advises on the technical setup; that doesn't replace a legal assessment for the specific case.

Prescription and health data need role-based access rights, traceable access logging and encrypted storage. NDVDL sets up this structure, though it doesn't replace a final legal assessment of the specific implementation.

Lab equipment is connected according to manufacturer requirements and run in its own isolated network segment instead of sitting openly on the same network as internet access or the till. That keeps the device usable without leaving it exposed.

Yes, stock management can be linked to wholesale ordering and billing through interfaces, so stock levels, orders and invoicing run from the same data. Existing systems stay in use rather than being replaced.

Temperature monitoring with alerts flags deviations in fridges and cold storage before stock becomes unusable. Monitoring runs as its own network segment, so it stays independent of other failures.

The consultation area is left out when planning video surveillance; cameras are only placed in sales and storage areas. This doesn't replace a legal review of the specific implementation.

Backup, recovery and ongoing support are set up so the till system and stock management are usable again even after an incident outside regular opening hours. Details on availability are agreed individually with the operation.

Without redundantly connected infrastructure, members at an unstaffed gym can neither get in nor out, because the system depends on a single network link. NDVDL designs access systems so they do not rely on one single component.

Yes, it should be. A dedicated network segment for guest Wi-Fi stops an overloaded training-floor network from taking down the till or access control, and it keeps member data away from guest devices.

Steel beams, grated floors and climbing walls heavily dampen radio signal, especially in tall, open halls. Coverage from several well-placed access points, matched to the hall's structure, solves this.

No, that is one of the clear limits on video surveillance in this setting. Cameras are limited to the entrance, changing room lobby and outdoor areas; changing rooms, showers and saunas always stay out of view.

Access points, cameras and displays in wet areas need a protection rating built for moisture and chlorine vapour, ordinary office-grade equipment does not hold up there. NDVDL selects and places equipment to match each area.

Through a technical connection that lets existing member management software, billing and access control talk to each other, instead of running as separate isolated systems. NDVDL integrates existing systems rather than replacing them.

Through a shared network concept that treats the office, depot, kindergarten and other sites as their own segments while keeping them centrally visible, instead of running each building as an isolated solution. NDVDL plans this structure so every site can still be secured individually.

Through access rights based on actual responsibility, and logging that makes it traceable who accessed which data and when. NDVDL sets this up technically, backed by a firewall that limits access from outside.

Yes, technically separated through its own network segment, not just a second password on the same network. Only that way is it guaranteed that visitors reach the internet only, never the administrative systems.

Only to a limited extent, and after a careful assessment of interests in each individual case, public spaces such as playgrounds are considered particularly sensitive under data protection rules. NDVDL advises on camera placement and technical implementation; the legal assessment in each case belongs with a data protection advisor or the municipality itself.

Through documentation of access, passwords and network structure that is not tied to one single person, but can be handed over whenever responsibility changes. NDVDL sets up systems so that handover stays traceable.

Usually with whatever a failure or a data leak would harm the most, such as securing administrative data and separating public Wi-Fi from the administrative network. NDVDL discusses with the municipality what the available budget allows, and proposes an order that can be implemented in stages.

No. NDVDL is based in Bratislava, Slovakia. We support businesses in Vienna and the surrounding area through on-site appointments as well as remote support and phone.

Yes, on-site appointments in Vienna are part of how we work — we schedule them directly with you.

German. Our team communicates with you in German; internally we also work in English and Slovak.

Depending on the solution, either on your own on-site server infrastructure in Vienna or in EU data centers — we clarify this concretely with you in the concept before anything is built.

We don't lock you into long flat-rate contracts — scope and term are agreed together.

No. NDVDL is based in Bratislava, Slovakia, close to the Austrian border. We support businesses in Lower Austria through on-site appointments as well as remote support.

Yes. We work with businesses across Lower Austria, from the Weinviertel to the Industrieviertel — location is not a barrier.

German. Our team communicates with you in German; internally we also work in English and Slovak.

Depending on the solution, either on your own on-site server infrastructure or in EU data centers — we clarify this concretely with you in the concept before anything is built.

We don't lock you into long flat-rate contracts — scope and term are agreed together.

NDVDL s.r.o. is registered with the Obchodný register Okresného súdu Bratislava I, IČO 52603750, seated at Rázusovo nábrežie - HUMA 6, 811 02 Bratislava.

Slovak or German — whichever suits you. Internally we also work in English.

Yes, for businesses in Slovakia on-site appointments are part of how we work, complemented by remote support for ongoing maintenance.

Depending on the solution, either on your own on-site server infrastructure or in EU data centers — we clarify this concretely with you in the concept.

We don't lock you into long flat-rate contracts — scope and term are agreed together.

Docker packages an application into a container, but says nothing about how multiple containers are managed, restarted, or scaled over time. That's exactly the job Kubernetes does as the orchestration layer above the containers.

Instead of creating servers, networks, and other AWS resources by hand in the web console, they're described in configuration files that Terraform applies automatically. Infrastructure changes then follow the same traceable process as changes to application code.

BVCC Holding doesn't keep its own infrastructure on-site. A cloud platform like AWS provides compute, network, and storage as managed building blocks that can be provisioned as needed.

The initial setup ends once the infrastructure is in place and the services are running. Ongoing operation instead includes monitoring, applying updates, and scaling the container landscape through Kubernetes so the services stay continuously available.

NDVDL works on the group's servers and operates the cloud environment its services run in: built on AWS, containerised with Docker, orchestrated via Kubernetes and infrastructure as code with Terraform. Hosting, monitoring and ongoing operations are part of it.

The engineer who knows the environment — no ticket system as a layer in between. That is what the phone number on this page is for; it applies to clients in day-to-day operation just as much as to a first conversation.

With HTTP polling, every sensor would need to be queried at fixed intervals whether or not anything changed — which creates unnecessary network and server load once many sensors are involved. MQTT works on a publish/subscribe basis: sensors send values as they occur, and the backend only subscribes to the relevant data streams. That's more bandwidth-efficient and holds up better against the short connection drops that can occur on building networks.

Building sensors often come from different manufacturers and report data in different formats and at different intervals. A platform has to map that variety onto a single, consistent interface before the data can be processed further — that's one of the core jobs of the sensor connectivity layer.

Python has a wide ecosystem of libraries for handling time-series data and adapts relatively quickly to new sensor types or data formats. For a backend that continuously prepares heterogeneous sensor data, that adaptability is a practical advantage.

Display devices in a building typically operate without continuous on-site supervision. If a device briefly drops offline or loses its connection, it needs to update its content on its own once it reconnects rather than showing outdated material. A central management system handles that control and keeps an overview of every display's status.

NDVDL supports Smartenic with IoT, networking and digital signage: connecting the sensors, transmitting readings in real time over MQTT, processing them in the Python backend, the network foundation behind it and the central management of the displays. The cooperation is ongoing.

Because every device, sensor and display needs a working connection — and because IoT devices are a risk of their own when they sit unsegmented next to workstations and servers. Planning, segmentation and coverage of the network therefore decide whether the sensor data arrives reliably and whether the devices endanger the rest of the operation.

DOOH stands for Digital Out of Home and refers to digital advertising screens in public spaces — for example, displays at locations with foot traffic. Unlike traditional printed posters, content on DOOH screens can be controlled centrally, scheduled in advance, and swapped per campaign, which is why software for managing bookings and content is needed in the first place.

Because bookings have to be mutually exclusive: a screen can't be assigned to two campaigns for the same time slot. Relational databases like PostgreSQL provide transactions that guarantee exactly that, even when several booking requests arrive at the same time — which is why campaign and booking data use a relational rather than a document-based model.

Go's goroutines give it a lightweight concurrency model built for backend services handling many parallel requests — such as simultaneous booking and analytics queries. It also compiles to a single, efficient binary, which simplifies operating each service.

It means hosting, scaling, and monitoring for the whole application — frontend, backend services, and database — run on AWS infrastructure. That covers things like handling traffic spikes, network security, and ongoing monitoring of each service in production.

NDVDL. We are the development partner behind the platform: the interface, the backend services, the data layer and the operation on AWS come from us. Adyoutiser remains an independent product — NDVDL is responsible for the technology and its ongoing development, not for selling the advertising space.

Yes. Bringing booking, management and reporting into one application is not specific to DOOH — the same problem appears wherever resources, appointments or spaces are allocated. It starts with a free first conversation in which we look at how you handle things today; from that comes a concept with a clear scope, before a single line of code is written.

For us, going live is not the end of the project. What follows is operating and monitoring the services, rolling out updates and developing the platform further along what real usage shows. With Adyoutiser exactly that part — operations on AWS and ongoing development — stays with NDVDL.

That depends on your company's size and the type of processing — a legal assessment we don't make. We recommend a lawyer or data protection officer for that, and implement whatever follows from it technically.

That's a legal question with no blanket answer — we deliberately give no period here. Your legal counsel determines what retention is lawful for you; we configure automatic deletion to match technically.

That's also a legal question we don't answer. Technically, we implement whatever is specified — including the areas that must be deliberately excluded from the camera view.

The storage location is within Europe and traceable for you — exactly where, we determine together with you.

We assign access rights by role, not as a blanket grant — and document who can access what.

Nothing about our role: we implement whatever your legal counsel specifies technically, and coordinate with them directly instead of sending you back and forth between two points of contact.

Yes. It queries only DNS records and the publicly served TLS certificate — the same data every mail server and every browser reads during normal operation. No port scan takes place and nothing is altered on any external system. That is precisely why the check is deliberately limited to these tests.

SPF and DKIM establish whether a message is genuine. DMARC is the only one of the three that tells the recipient what to do with a message that is not. Without DMARC a message can fail both checks and still be delivered — the recipient simply has no instruction.

It is the observation setting: DMARC is evaluated and optionally reported on, but nothing is blocked. It is meant as a transition lasting a few weeks, so you can see who is sending in your name. In practice it often stays for years and gives a false sense of security.

Not necessarily. The selector a DKIM key sits under is freely chosen and cannot be enumerated from outside. The check tries the common names. Finding nothing is an indication, not proof — which is why this item is not counted as a fault.

The DNS records themselves are a matter of minutes. The effort sits before that: working out which services actually send in your name — ERP, newsletter tool, accounting, point-of-sale. Anyone who enforces DMARC before that list is complete will block their own invoices. That is why it is done in stages.

No. The result appears right after the last question. We only need an address if you would like us to go through the result with you.

They stay in your browser for as long as the page is open. They are transmitted only if you explicitly submit the form at the end — then as text in the email to us, so we know what we are talking about.

No, and it does not pretend to be. It rests entirely on your own answers to eleven situations. What it does: it makes visible where a real review would have to begin, and in what order.

For companies that depend on IT but have no IT department of their own — roughly between a handful and a few hundred workplaces. The questions are worded so that a managing director can answer them without asking anyone technical.