Skip to main content
Back

DNSensese

From blind spots to visibility into your network.

Schedule a consultation Schedule a consultation

Three situations we encounter every day.

Why choose a DNSense partner?

  • One wrong click and you’re in

    You can train your colleagues, but someone will still click on a link that looks legitimate. Then the question isn’t whether it will happen, but what happens next. A network-level filter blocks the connection before the page loads.

  • Not every device can run software

    Laptops, phones, printers, cameras, and devices that can’t run software: these fall outside your endpoint security. At the DNS level, however, they’re all covered—without you having to install anything.

  • You can’t see what’s leaving your network

    You don’t know which device is accessing which domains, so in the event of an incident, the investigation starts from scratch. With per-device visibility, you can immediately see where traffic is coming from, which saves hours during an audit.

DNSense as the engine of your network security

Virtually every attack begins with a connection to a domain: a phishing link, an infected attachment that sends data back to the attacker, or a device attempting to contact a server that shouldn’t be there. That connection always passes through your DNS.

DNSense is the engine that applies the filter there. Every outbound request is checked, and connections to malicious domains are blocked before anything loads. This happens at the network level, so it requires no software on the devices and goes completely unnoticed by your users.

You stay in control. The reports show you which device is accessing which domains and what has been blocked, so security isn’t a black box.

What We Do with DNSense

We start by looking at what’s currently happening: which domains are being accessed, by which devices, and which of those are suspicious. That baseline assessment usually reveals traffic that nobody knew was there.

Next, we set up the profiles. A development team needs different permissions than an administrative team, and filtering too strictly hurts productivity. Striking that balance is the real work, and we fine-tune it based on what’s actually being blocked in practice.

Finally, we integrate with your existing IT infrastructure: user groups, device policies, and alerts sent to wherever your team is already monitoring. Every month, we review what’s been blocked and where we need to make adjustments.

Three things you’ll notice in our collaboration.

Why choose Redkiwi as your DNSense partner?

  • You can see for yourself what’s being blocked

    You can see for yourself which traffic has been blocked and why, by device and by profile. Every month, we review this together, and you decide how strictly to filter. The policy remains yours; we ensure the technology implements it.

  • Honest about what it doesn’t cover

    A DNS filter does not replace endpoint security or backups; it’s an additional layer of protection. We’re transparent about what it doesn’t cover, because security whose limitations you don’t understand provides a false sense of security.

  • Security and management under one roof

    We also manage the hosting and the underlying systems, so if a block causes an issue, it takes just one phone call with us instead of three. You’ll work with a dedicated specialist who knows your environment.

Frequently Asked Questions About DNS Security

01/ What is a DNS firewall?
A filter that monitors every domain name your network accesses and blocks connections to known malicious domains. If someone clicks on a phishing link, they won’t be able to get through. It works at the network level, so no software is required on the devices themselves.
02/ Do I need to install software on every device?
No, and that’s exactly the point. It runs at the network level, so laptops, phones, printers, and devices you can’t install software on are all covered. That simplifies management and also covers anything you might forget.
03/ Can I set different rules for each department?
Yes, using profiles for each department or role. A development team has different space requirements than an administrative department. We set up those profiles and adjust them based on what is actually being blocked in practice.
04/ What if a domain is blocked by mistake?
In that case, please report it, and we’ll add the domain to the exceptions list. This happens a few times at first and then hardly ever after that. Overly strict filtering reduces productivity, so we adjust the settings based on what’s actually being blocked.