How is betking.com?

Looks fine risk 0/100

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

64 ms

HTTPS

59 d

left on a Google Trust Services certificate

Age

25 years

registered 2001-07-03

Blocklists

listings across 5 lists

Everything we looked at

DNS records5 record types

A	104.18.36.145 172.64.151.111
AAAA	2a06:98c1:3103::ac40:976f 2a06:98c1:3102::6812:2491
MX	10 betking-com.mail.protection.outlook.com
NS	damien.ns.cloudflare.com eve.ns.cloudflare.com
TXT	MS=ms76191251 atlassian-domain-verification=5VOLUp8jhocLoUaXsFkQdwOXa4IGywlnJ8gCp4aoUcIc1jEseYBeg7sat2aIH/HH docusign=eb6d9b1e-78bf-4dc3-a0d0-8be897393138 google-site-verification=Vtl506vs3eMWsNsvOyK0je2emcEjDdLlQyvl3S8g9eM google-site-verification=Fzpsv-GTkjeON30HGDEtPnbDMsYxLPYvIZ3RAwfS97c facebook-domain-verification=qk5hk8x30gpycgxvpl5cmmf6cwvioj atlassian-domain-verification=3Tnh8Ge/GeM3N04le5gCG693J1L0KwuaO6Dawk1S3JjSr4ubURkdZ2ow6XV7XezF docusign=39e46786-0836-45a0-b83b-52e8be72fe2a 2df3brr3eti5703vn970nbm41e v=spf1 mx include:spf.protection.outlook.com include:spfrerouting.xink.io ~all hibp-verify=dweb_7yhx4ph7qdqywmuco5c4qyw8 ufcc6iu28ighov6l0p2hct5si1

RegistrationSafeNames Ltd.

registrar	SafeNames Ltd.
registered	2001-07-03
expires	2028-07-03
last changed	2026-07-31
nameservers	damien.ns.cloudflare.com eve.ns.cloudflare.com
status	client delete prohibited client transfer prohibited client update prohibited ok

registered 2001-07-03expires 2028-07-03

HTTPS certificate59 days left

valid	yes
issuer	Google Trust Services
covers	betking.com, uat-shop.betking.com
protocol	TLSv1.3

issued 2026-09-29expires 2026-12-28

DNSSECinsecure

Domain is not signed with DNSSEC

. → com → betking.com

Email authenticationexcellent

SPF	pass `v=spf1 mx include:spf.protection.outlook.com include:spfrerouting.xink.io ~all`
DMARC	pass policy quarantine
DKIM	found: selector2, s1, s2

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

Security scoregrade B · 155/205

Basic Security

10/40missing: DNSSEC Enabled, Nameserver Diversity

Record Security

30/45missing: CAA Records, 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 MultidomainSpamCop172.64.151.111Barracuda172.64.151.111UCEPROTECT Level 1172.64.151.111SpamCop104.18.36.145Barracuda104.18.36.145UCEPROTECT Level 1104.18.36.145

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=betking.com" \ -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=betking.com"

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

Watch betking.com. 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