What Django is
Django is a Python web framework that renders server-side and ships no identifying response header. Its cross-site request forgery protection sets a cookie with a fixed default name, and that cookie is the practical public signal.
How DNSTrace.dev detects it
Detection reads the final HTTPS response and the first bytes of its markup. One matching signal is reported as strong evidence; two or more independent signals are reported as confirmed.
csrftoken cookie— Django's default cross-site request forgery cookie name.sessionid cookie— The default session cookie, supporting evidence when it appears alongside csrftoken.server naming Gunicorn— A common Django application server, reported separately as the runtime rather than the framework.
What a detection proves
The response was produced by a Django application.
What it does not prove
The Django version, the Python version or the hosting platform. The cookie name is configurable, so a hardened deployment can hide it.
Common questions
Does a csrftoken cookie always mean Django?
It is the Django default and rare elsewhere, so DNSTrace.dev treats it as strong evidence. A single cookie match is reported as strong rather than confirmed for exactly this reason.
Is Gunicorn part of Django?
No. Gunicorn is a Python application server frequently used to run Django, and DNSTrace.dev reports it as its own runtime signal.
Compare with
Open source, Laravel Holdings Inc.
Application frameworkOpen source, Rails Foundation
Application frameworkOpen source, OpenJS Foundation
Server languageOpen source, the PHP Group
Check a domain
Run a full lookup to see the delivery layer, the detected application stack, live TLS and the announcing network side by side.