How is tbs.co.jp?

Looks fine risk 0/100

Registered 18 years ago, on no blocklists we checked, valid HTTPS, the site answered HTTP 404.

Why

02050100

finecarefulhigh risk

·Nothing in the checks added risk.

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

Site

404

900 ms

HTTPS

79 d

left on a DigiCert Inc certificate

Age

18 years

registered 2009-03-30

Blocklists

listings across 5 lists

Everything we looked at

DNS records4 record types

A	163.45.126.1 163.45.254.1
MX	5 alt2.aspmx.l.google.com 10 alt4.aspmx.l.google.com 5 alt1.aspmx.l.google.com 10 alt3.aspmx.l.google.com 1 aspmx.l.google.com
NS	ns.spin.ad.jp ns01.tbs.co.jp ns.tokyo.spin.ad.jp ns02.tbs.co.jp
TXT	MS=F2F840FA533B113DBC4E987FB5C3102DA089FF37 v=spf1 include:_spf.google.com include:spfcm.cybermail.jp ip4:163.45.100.13 ip4:163.45.200.13 ip4:163.45.100.215 ip4:113.39.72.92 ip4:210.128.220.104 ip4:150.195.209.104 ip4:150.195.208.45 ip4:150.195.210.153 -all miro-verification=3b41b07d556607357d985ba9cb6cd0d137f5dc77 workplace-domain-verification=E8wOs7AWpINW1BU0OighWfBMPXPBWl adobe-idp-site-verification=248d2e629db17d3448476f6bb3ee59d09fb2231ec0779a72b2003fdb8f64baa9 google-site-verification=S_9ipjvavgXY0vAu-D_B5lwoebsdxLs9tSTC-oSwlTo google-site-verification=SQs-Fp5ScR6cg_FgpunTQ-_dJ1hnpV26BfLmYCiFytI notion-domain-verification=syoS0zFk63xfCLFT1fyjc7MYxJT1oUMhw4tmPfjVTQX google-site-verification=_QVd4Ejnbo4g408EpS7jcHJL-T9pGZEf7ttZX2s-5D0 google-site-verification=vNvtAI6LwO_GiX78ctNvQOzyB2wNBmIR1bVrExFJUjo google-site-verification=rqHVWIcJrAuhLdXz7e-lKDZwsicQTteqGcdiCRwvRg8 google-site-verification=75fQoX1P1tQWLGeXBkfO5z-71muFEakM68p8szrmXWE google-site-verification=r3J0IkI-H_GzpZw6VRU3seEU3SSKGrNbUlpkuaE2g_8

Registrationregistrar not reported

registered	2009-03-30
expires	2027-03-31
last changed	2026-06-26
owner	TOKYO BROADCASTING SYSTEM TELEVISION, INC.
nameservers	ns01.tbs.co.jp ns00.vips.ne.jp ns01.vips.ne.jp ns02.tbs.co.jp
status	Connected (2027/03/31)

registered 2009-03-30expires 2027-03-31

HTTPS certificate79 days left

valid	yes
issuer	DigiCert Inc
covers	*.tbs.co.jp, tbs.co.jp
protocol	TLSv1.2

issued 2026-07-02expires 2027-01-16

DNSSECinsecure

Domain is not signed with DNSSEC

. → jp → co.jp → tbs.co.jp

Email authenticationgood

SPF	pass `v=spf1 include:_spf.google.com include:spfcm.cybermail.jp ip4:163.45.100.13 ip4:163.45.200.13 ip4:163.45.100.215 ip4:113.39.72.92 ip4:210.128.220.104 ip4:150.195.209.104 ip4:150.195.208.45 ip4:150.195.210.153 -all`
DMARC	warning policy none
DKIM	found: google, s1, s2

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

Security scoregrade B · 153/205

Basic Security

20/40missing: DNSSEC Enabled

Record Security

23/45missing: CAA Records, DMARC Record, DKIM Presence

Advanced Security

15/25missing: SOA Record Configuration, IPv6 Support

Domain Reputation

50/50

Threat Detection

45/45missing: Domain Age Check

Blocklists0 listings · 8 lookups

SURBL MultidomainURIBL MultidomainSpamCop163.45.254.1Barracuda163.45.254.1UCEPROTECT Level 1163.45.254.1SpamCop163.45.126.1Barracuda163.45.126.1UCEPROTECT Level 1163.45.126.1

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=tbs.co.jp" \ -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=tbs.co.jp"

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

Watch tbs.co.jp. 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