How is fdown.net?

Looks fine risk 0/100

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

Why

02050100

finecarefulhigh risk

·Nothing in the checks added risk.

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

The home page, rendered by how.is in a sandboxed browser. Nothing on it is clickable here.

Site

200

89 ms

HTTPS

32 d

left on a Let's Encrypt certificate

Age

21 years

registered 2005-10-24

Blocklists

listings across 5 lists

Everything we looked at

DNS records6 record types

A	172.67.70.216 104.26.7.202 104.26.6.202
AAAA	2606:4700:20::681a:7ca 2606:4700:20::ac43:46d8 2606:4700:20::681a:6ca
MX	5 alt2.aspmx.l.google.com 5 alt1.aspmx.l.google.com 1 aspmx.l.google.com 15 vlfzqkmvdaixwfmq3fa655wjvqwbezhasd6yyroecrjq27nrtdiq.mx-verification.google.com 10 alt4.aspmx.l.google.com 10 alt3.aspmx.l.google.com
NS	iris.ns.cloudflare.com brad.ns.cloudflare.com
TXT	v=spf1 include:_spf.google.com ~all google-site-verification=SjduoJDNcRPhPQwKXxtMMoFdMW2unLGKrR0t-ZNazBM
CAA	{'type': 'CAA', 'issue': 'pki.goog; cansignhttpexchanges=yes', 'critical': 0} {'type': 'CAA', 'critical': 0, 'issuewild': 'letsencrypt.org'} {'type': 'CAA', 'issue': 'letsencrypt.org', 'critical': 0} {'type': 'CAA', 'critical': 0, 'issuewild': 'digicert.com; cansignhttpexchanges=yes'} {'type': 'CAA', 'issue': 'digicert.com; cansignhttpexchanges=yes', 'critical': 0} {'type': 'CAA', 'critical': 0, 'issuewild': 'comodoca.com'} {'type': 'CAA', 'critical': 0, 'issuewild': 'pki.goog; cansignhttpexchanges=yes'} {'type': 'CAA', 'issue': 'ssl.com', 'critical': 0} {'type': 'CAA', 'issue': 'comodoca.com', 'critical': 0} {'type': 'CAA', 'critical': 0, 'issuewild': 'ssl.com'}

RegistrationGoDaddy.com, LLC

registrar	GoDaddy.com, LLC
registered	2005-10-24
expires	2027-10-24
last changed	2022-10-28
nameservers	brad.ns.cloudflare.com iris.ns.cloudflare.com
status	client delete prohibited client renew prohibited client transfer prohibited client update prohibited

registered 2005-10-24expires 2027-10-24

HTTPS certificate32 days left

valid	yes
issuer	Let's Encrypt
covers	*.fdown.net, fdown.net
protocol	TLSv1.3

issued 2026-09-02expires 2026-12-01

DNSSECinsecure

Domain is not signed with DNSSEC

. → net → fdown.net

Email authenticationfair

SPF	pass `v=spf1 include:_spf.google.com ~all`
DMARC	none
DKIM	found: google

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

Security scoregrade B · 160/205

Basic Security

10/40missing: DNSSEC Enabled, Nameserver Diversity

Record Security

30/45missing: DMARC Record, DKIM Presence

Advanced Security

25/25

Domain Reputation

50/50

Threat Detection

45/45missing: Domain Age Check

Blocklists0 listings · 11 lookups

SURBL MultidomainURIBL MultidomainSpamCop104.26.6.202Barracuda104.26.6.202UCEPROTECT Level 1104.26.6.202SpamCop104.26.7.202Barracuda104.26.7.202UCEPROTECT Level 1104.26.7.202SpamCop172.67.70.216Barracuda172.67.70.216UCEPROTECT Level 1172.67.70.216

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=fdown.net" \ -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=fdown.net"

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

Watch fdown.net. 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