Who’s knocking? Profiling recursive resolvers at authoritative name servers
Guest Post: Knowing which DNS resolvers are serving key clients would allow operators to optimize server infrastructure.
| CARVIEW |
Select Language
HTTP/2 200
date: Mon, 14 Jul 2025 00:50:49 GMT
content-type: text/html; charset=UTF-8
content-length: 36795
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: 1701
strict-transport-security: max-age=15552000; preload
last-modified: Mon, 14 Jul 2025 00:50:49 GMT
cf-cache-status: MISS
expires: Mon, 14 Jul 2025 01:50:49 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: 95ed0728ae8b9ac4-BLR
Metin Açıkalın, Author at APNIC Blog
Skip to content
