HOW.IS
?

How is rule34.xxx?

Looks fine risk 0/100

Registered 15 years ago, on no blocklists we checked, valid HTTPS, the site answered 403 in 79 ms.

Why

02050100
finecarefulhigh risk
  • ·Nothing in the checks added risk.

Rule-based: domain age, blocklists, TLS. A heuristic, not a guarantee.

How rule34.xxx looks right now
The home page, rendered by how.is in a sandboxed browser. Nothing on it is clickable here.
Site
403
79 ms
HTTPS
57 d
left on a Google Trust Services certificate
Age
15 years
registered 2012-01-18
Blocklists
0
listings across 5 lists

Everything we looked at

DNS records6 record types
A172.66.156.23
104.20.43.5
AAAA2606:4700:10::ac42:9c17
2606:4700:10::6814:2b05
MX20 mailsec.protonmail.ch
10 mail.protonmail.ch
NSroxy.ns.cloudflare.com
will.ns.cloudflare.com
TXTgoogle-site-verification=Hhsbi2fMdFvtrPQ5tTRMTYam9FUQqxUbMrhAx1wQWtM
google-site-verification=NGNxIJD3d1TMKEXDq3cacwjqYHcmUblt8gS60OxeoH0
v=spf1 include:_spf.protonmail.ch ~all
protonmail-verification=c3169be559046535078fe3506dae089b4462c8fb
CAA{'type': 'CAA', 'critical': 0, 'issuewild': 'pki.goog; cansignhttpexchanges=yes'}
{'type': 'CAA', 'issue': 'ssl.com', 'critical': 0}
{'type': 'CAA', 'issue': 'letsencrypt.org', 'critical': 0}
{'type': 'CAA', 'issue': 'sectigo.com', 'critical': 0}
{'type': 'CAA', 'critical': 0, 'issuewild': 'comodoca.com'}
{'type': 'CAA', 'critical': 0, 'issuewild': 'digicert.com; cansignhttpexchanges=yes'}
{'type': 'CAA', 'critical': 0, 'issuewild': 'ssl.com'}
{'type': 'CAA', 'critical': 0, 'issuewild': 'letsencrypt.org'}
{'type': 'CAA', 'issue': 'comodoca.com', 'critical': 0}
{'type': 'CAA', 'issue': 'pki.goog; cansignhttpexchanges=yes', 'critical': 0}
{'type': 'CAA', 'issue': 'digicert.com; cansignhttpexchanges=yes', 'critical': 0}
{'type': 'CAA', 'critical': 0, 'issuewild': 'sectigo.com'}
RegistrationNameCheap, Inc.
registrarNameCheap, Inc.
registered2012-01-18
expires2033-01-18
last changed2025-09-20
nameserverswill.ns.cloudflare.com
roxy.ns.cloudflare.com
statusclient transfer prohibited
registered 2012-01-18expires 2033-01-18
HTTPS certificate57 days left
validyes
issuerGoogle Trust Services
coversrule34.xxx, *.rule34.xxx
protocolTLSv1.3
issued 2026-09-26expires 2026-12-25
DNSSECsecure

Domain is properly signed — chain validated by an independent validating resolver

. → xxx → rule34.xxx
Email authenticationexcellent
SPFpass v=spf1 include:_spf.protonmail.ch ~all
DMARCpass policy quarantine
DKIMfound: protonmail, protonmail2

Whether mail claiming to be from this domain can be checked as genuine.

Security scoregrade A · 175/205
Basic Security
10/40missing: DNSSEC Enabled, Nameserver Diversity
Record Security
45/45missing: DKIM Presence
Advanced Security
25/25
Domain Reputation
50/50
Threat Detection
45/45missing: Domain Age Check
Blocklists0 listings · 8 lookups
SURBL MultidomainURIBL MultidomainSpamCop172.66.156.23Barracuda172.66.156.23UCEPROTECT Level 1172.66.156.23SpamCop104.20.43.5Barracuda104.20.43.5UCEPROTECT Level 1104.20.43.5

Green: clean. Red: listed. Grey: the list did not answer.

Ask it yourself

Agents get this as data. Bought through the API, the checks behind this page cost $0.070: profile $0.025 + trust $0.020 + screenshot $0.020 + site status $0.005.

curl "https://how.is/v1/domain/trust?domain=rule34.xxx" \ -H "Authorization: Bearer $HOWIS_KEY" # or pay per call in USDC (x402), no key: the 402 tells your agent the price curl -i "https://how.is/v1/domain/profile?domain=rule34.xxx"

MCP: add https://how.is/mcp to Claude, Codex or Cursor (one-line install) and ask for domain_trust on rule34.xxx. Reference: /llms.txt.

Watch rule34.xxx. DNS read at the source every 5 minutes; certificate, blocklists and expiry every 6 hours. You get an email only when something changes.

Watch — $1 / 30 days