Why don’t we have DNS-security policy for context-full threat protection?
Guest Post: Expecting firewalls and gateways to secure DNS traffic is folly in today’s Internet. Instead, we need a more resilient approach.
| CARVIEW |
Select Language
HTTP/2 200
date: Tue, 15 Jul 2025 02:47:23 GMT
content-type: text/html; charset=UTF-8
content-length: 36768
x-xss-protection: 1; mode=block
referrer-policy: no-referrer, same-origin, strict-origin-when-cross-origin
x-frame-options: SAMEORIGIN
x-frame-options: SAMEORIGIN
x-content-type-options: nosniff
access-control-allow-origin: https://www.apnic.net
cf-edge-cache: cache,platform=wordpress
link: ; rel="alternate"; title="JSON"; type="application/json"
vary: Accept-Encoding
content-encoding: gzip
x-envoy-upstream-service-time: 1859
strict-transport-security: max-age=15552000; preload
last-modified: Tue, 15 Jul 2025 02:47:23 GMT
cf-cache-status: MISS
expires: Tue, 15 Jul 2025 03:47:23 GMT
cache-control: public, max-age=3600
accept-ranges: bytes
access-control-allow-headers: cache-control, pragma, user-agent
access-control-allow-methods: GET, OPTIONS
server: cloudflare
cf-ray: 95f5ef46bc778a2a-BLR
Asad Ali, Author at APNIC Blog
Skip to content
