HTTP Status Code
Why do we need it?
As we want to determine the availability of a domain, IP, or URL; one of our testing method is the gathering of the HTTP status code.
How does it work?
Note
We never send a generic User-Agent. You can define your own or let PyFunceble choose one of the latest one of one of the major browser for you.
When it is the turn of the HTTP status code lookup tool to try to gather a status for the given subject, an HTTP query is made to the given IP, domain or subject.
When testing for a domain, a successful HTTP response is considered as
ACTIVE
.
Otherwise, the following default classification applies.
Note
The classification can be changed by end-user through their configuration file.
As ACTIVE
Please note that the following HTTP status codes are considered as ACTIVE.
If you are using the CLI with the analytic files generated, you will get any matching subject flagged as ACTIVE officially and into your analytic files.
100
: Continue101
: Switching Protocols102
: Processing200
: OK201
: Created202
: Accepted203
: Non-Authoritative Information204
: No Content205
: Reset Content206
: Partial Content207
: Multi-Status208
: Already Reported226
: IM User429
: Too Many Request.
As potentially ACTIVE
Please note that the following HTTP status codes are considered as potentially ACTIVE but still officially reported as ACTIVE when caught.
If you are using the CLI with the analytic files generated, you will get any matching subject flagged as ACTIVE officially and into your analytic files as potentially ACTIVE.
300
: Multiple Choices301
: Moved Permanently302
: Found303
: See Other304
: Not Modified305
: Use Proxy307
: Temporary Redirect308
: Permanent Redirect403
: Forbidden405
: Method Not Allowed406
: Not Acceptable407
: Proxy Authentication Required408
: Request Timeout411
: Length Required413
: Payload Too Large417
: Expectation Failed418
: I’m a teapot421
: Misdirect Request422
: Unprocessable Entity423
: Locked424
: Failed Dependency426
: Upgrade Required428
: Precondition Required431
: Request Header Fields Too Large500
: Internal Server Error501
: Not Implemented502
: Bad Gateway503
: Service Unavailable504
: Gateway Timeout505
: HTTP Version Not Supported506
: Variant Also Negotiates507
: Insufficient Storage508
: Loop Detected510
: Not Extended511
: Network Authentication Required
As INACTIVE or potentially INACTIVE
Please note that the following HTTP status codes are considered as INACTIVE or potentially INACTIVE. Therefore officially reported as INACTIVE when caught.
If you are using the CLI with the analytic files generated, you will get any matching subject flagged as INACTIVE officially and into your analytic files as potentially INACTIVE.
400
: Bad Request402
: Payment Required404
: Not Found409
: Conflict410
: Gone412
: Precondition Failed414
: Request-URI Too Long415
: Unsupported Media Type416
: Request Range Not Satisfiable451
: Unavailable For Legal Reasons
How to use it?
You can simply allow the usage of the HTTP status code lookup through:
the (Python) API,
the CLI argument,
or, your configuration file.