How is pikabu.ru?

Looks fine risk 0/100

Registered 18 years ago, on no blocklists we checked, valid HTTPS, the site answered 403 in 111 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

403

111 ms

HTTPS

74 d

left on a Let's Encrypt certificate

Age

18 years

registered 2009-04-03

Blocklists

listings across 5 lists

Everything we looked at

DNS records4 record types

A	185.178.210.201
MX	10 mx.yandex.net
NS	alla.ns.cloudflare.com phil.ns.cloudflare.com
TXT	atlassian-domain-verification=pWgaf2649nfldGsE9JNFg3y0rBrGrME4quObWkJaWVCKHKK13PmJa7EfJ2AgJufz mailru-verification: 900faf338e846cbf v=spf1 include:_spf.google.com include:_spf.dashasender.ru include:_spf.yandex.net include:_spf.pikabu.ru ~all esputnik-verification=RVNQX0RWS19WMQAA2JoAAAFwyW5484ZFKrjpgrgp google-site-verification=dEMS1zAP2rTwSmGIa4yi4-45uGpN7y91OspPMimj77Y google-site-verification=lVp3ez5Y1BA5w-F91okggmXUSl-u7shz3EcajHIYaYI yandex-verification: 62877a82a5debdf5 mailru-verification: 7d4ea76bdf31bd3d yandex-verification: 5c0d34b814864290 google-site-verification=U10gGZhkN-GB66X3mYE1E2T9IFzVgqV4gh4g0KoONu8 facebook-domain-verification=6rpvsjo3a9v9zgvyu2djh9w24hk4q7 MS=9F9058F28ABBA716DA65288227B00376C128C0E4 yandex-verification=fb9a7e8303137b4c

RegistrationBEGET-RU

registrar	BEGET-RU
registered	2009-04-03
nameservers	alla.ns.cloudflare.com. phil.ns.cloudflare.com.

HTTPS certificate74 days left

valid	yes
issuer	Let's Encrypt
covers	auth.pikabu.ru, beta.pikabu.ru, m.pikabu.ru, new.pikabu.ru, old.pikabu.ru, pikabu.ru, u.pikabu.ru, www.pikabu.ru
protocol	TLSv1.3

issued 2026-10-13expires 2027-01-11

DNSSECinsecure

Domain is not signed with DNSSEC

. → ru → pikabu.ru

Email authenticationexcellent

SPF	pass `v=spf1 include:_spf.google.com include:_spf.dashasender.ru include:_spf.yandex.net include:_spf.pikabu.ru ~all`
DMARC	pass policy quarantine
DKIM	found: google, s1, s2, mail

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

Security scoregrade B · 150/205

Basic Security

10/40missing: DNSSEC Enabled, Nameserver Diversity

Record Security

30/45missing: CAA Records, DKIM Presence

Advanced Security

15/25missing: Mail Server Configuration, IPv6 Support

Domain Reputation

50/50

Threat Detection

45/45missing: Domain Age Check

Blocklists0 listings · 5 lookups

SURBL MultidomainURIBL MultidomainSpamCop185.178.210.201Barracuda185.178.210.201UCEPROTECT Level 1185.178.210.201

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=pikabu.ru" \ -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=pikabu.ru"

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

Watch pikabu.ru. 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