telangana.gov.in
What our own request to this host returned, over the last 30 days. Nothing here was tested for weaknesses and nothing was captured from anyone else's traffic.
Last status
no response — tcp connection
Answered
29% of 21 probes
Refused
none of 21 probes over 30 days
Median open time
8005 ms
Last seen
2026-11-01 07:04:48 UTC
“Answered” is how often our own request got a response, from one region at one probe per day. It is not an uptime figure and must not be read as one. A refusal is a response, so a refused probe counts as answered. "Refused" counts the probes whose answer was 403 or 429.
Our last request stopped at: TCP connection
The name resolved, but the connection to that address did not complete.
This is what happened to one request from one region at one moment. A refusal aimed at our bot, a problem on our own egress and a fault at the host all end at the same stage, and nothing we record separates them — so this is not a claim that the site is down.
Transport
TLS
not measured
Certificate expiry
no certificate inspected
Issuer
not measured
Chain valid
not measured
Name matches
not measured
HTTP version
not measured
Cipher
not measured
Address family
v4
Headers and cookies
Header grade
not measured
HSTS
not measured
Mixed content
not measured
Cookie flags
not measured
Redirect hops
0
Exposure check
not measured
The request ended at http://telangana.gov.in/. 6 of the 6 probes that got a response ended on a different host, so the fields above may describe that host rather than this one.
Where the time went
5001 ms in total, from one request. Transfer is the remainder after the first byte rather than a separately measured phase.
Registration and published DNS
Domain registration
180 days left
Registrar
National Informatics Centre
Registered
2014-05-01
DNSSEC
not signed
SPF
softfail
DMARC
reject
Accepts mail
MX published
Registry record read over RDAP on 2026-10-26. SPF and DMARC read from public DNS on 2026-10-31. Neither involves a request to this host, and neither is a test: we read what the registry and the domain’s own DNS publish. A published policy is not evidence about what a mail receiver would actually do.
By observer region
Measured from one region. The per-region comparison §5.5 describes needs more than one, and the deployment has one today.