FEATURE: Special rule: Wordpress.com

[spirillen]

Description

At wordpress.com they it seems like they uses the HTTP 410 code for no longer active subdomains like katiaescorts.wordpress.com

curl -I https://katiaescorts.wordpress.com
HTTP/2 410
server: nginx
date: Wed, 23 Nov 2022 11:10:11 GMT
content-type: text/html; charset=utf-8
vary: Cookie
x-hacker: If you're reading this, you should visit automattic.com/jobs and apply to join the fun, mention this header.
host-header: WordPress.com
x-ac: 1.arn _dca BYPASS
strict-transport-security: max-age=15552000

curl -I https://luckyaida.wordpress.com/
HTTP/2 410
server: nginx
date: Wed, 23 Nov 2022 11:12:35 GMT
content-type: text/html; charset=utf-8
vary: Cookie
x-hacker: If you're reading this, you should visit automattic.com/jobs and apply to join the fun, mention this header.
host-header: WordPress.com
x-ac: 1.arn _dca BYPASS
strict-transport-security: max-age=15552000

curl -I https://kalyluxe.wordpress.com
HTTP/2 410
server: nginx
date: Wed, 23 Nov 2022 11:14:04 GMT
content-type: text/html; charset=utf-8
vary: Cookie
x-hacker: If you're reading this, you should visit automattic.com/jobs and apply to join the fun, mention this header.
host-header: WordPress.com
x-ac: 1.arn _dca BYPASS
strict-transport-security: max-age=15552000

The alternative option is to fetch the h2 html line

<h2>katiaescorts.wordpress.com is no longer available.</h2>

Possible Solution

Considered Alternative

Additional context