HOW.IS
?

How is rfc-editor.org?

Looks fine risk 0/100

Registered 28 years ago, on no blocklists we checked, valid HTTPS, the site answered 200 in 118 ms.

Why

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

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

How rfc-editor.org looks right now
The home page, rendered by how.is in a sandboxed browser. Nothing on it is clickable here.
Site
200
118 ms · ends at www.rfc-editor.org
HTTPS
84 d
left on a Google Trust Services certificate
Age
28 years
registered 1998-05-15
Blocklists
0
listings across 5 lists

Everything we looked at

DNS records5 record types
A104.18.20.81
104.18.21.81
AAAA2606:4700::6812:1551
2606:4700::6812:1451
MX0 mx.ietf.org
NSken.ns.cloudflare.com
jill.ns.cloudflare.com
TXTgoogle-site-verification=S7F2LDRmYAIwFs4JZtnDdmZH23mNreKn8qKn2qkBcHs
v=spf1 ip4:166.84.6.31 ip4:166.84.7.238 ip6:2602:f977:800:f7f6::/64 ip4:166.84.7.34 ip6:2602:f977:800::e276:63ff:fe66:3400 include:_spf.google.com include:spf.hostedrt.com ~all
RegistrationCloudflare, Inc.
registrarCloudflare, Inc.
registered1998-05-15
expires2031-05-14
last changed2026-08-12
ownerDATA REDACTED
nameserversjill.ns.cloudflare.com
ken.ns.cloudflare.com
statusserver delete prohibited
client transfer prohibited
registered 1998-05-15expires 2031-05-14
HTTPS certificate84 days left
validyes
issuerGoogle Trust Services
coversrfc-editor.org, diff.staging.rfc-editor.org
protocolTLSv1.3
issued 2026-10-22expires 2027-01-20
DNSSECsecure

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

. → org → rfc-editor.org
Email authenticationgood
SPFpass v=spf1 ip4:166.84.6.31 ip4:166.84.7.238 ip6:2602:f977:800:f7f6::/64 ip4:166.84.7.34 ip6:2602:f977:800::e276:63ff:fe66:3400 include:_spf.google.com include:spf.hostedrt.com ~all
DMARCwarning policy none
DKIMfound: mail

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

Security scoregrade B · 148/205
Basic Security
10/40missing: DNSSEC Enabled, Nameserver Diversity
Record Security
23/45missing: CAA Records, DMARC Record, DKIM Presence
Advanced Security
20/25missing: Mail Server Configuration
Domain Reputation
50/50
Threat Detection
45/45missing: Domain Age Check
Blocklists0 listings · 8 lookups
SURBL MultidomainURIBL MultidomainSpamCop104.18.20.81Barracuda104.18.20.81UCEPROTECT Level 1104.18.20.81SpamCop104.18.21.81Barracuda104.18.21.81UCEPROTECT Level 1104.18.21.81

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=rfc-editor.org" \ -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=rfc-editor.org"

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

Watch rfc-editor.org. 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