How is m.me?

Looks fine risk 0/100

Registered 16 years ago, on no blocklists we checked, valid HTTPS, the site answered 200 in 412 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

412 ms · ends at www.messenger.com

HTTPS

7 d

left on a DigiCert Inc certificate

Age

16 years

registered 2010-05-20

Blocklists

listings across 5 lists

Everything we looked at

DNS records5 record types

A	57.144.230.141
AAAA	2a03:2880:f373:8d:face:b00c:0:2
NS	a.ns.facebook.com d.ns.facebook.com c.ns.facebook.com b.ns.facebook.com
TXT	v=spf1 a ~all
CAA	{'type': 'CAA', 'issue': 'digicert.com; account=271b0beda0771d006aa3a6c11b05187d456d6c239b46cb5241196095b09c92af', 'critical': 0}

RegistrationRegistrarSafe, LLC

registrar	RegistrarSafe, LLC
registered	2010-05-20
expires	2034-05-20
last changed	2026-08-12
owner	Meta Platforms, Inc.
nameservers	b.ns.facebook.com a.ns.facebook.com c.ns.facebook.com d.ns.facebook.com
status	client delete prohibited server delete prohibited client transfer prohibited server transfer prohibited client update prohibited server update prohibited

registered 2010-05-20expires 2034-05-20

HTTPS certificate7 days left

valid	yes
issuer	DigiCert Inc
covers	*.m.me, m.me
protocol	TLSv1.3

issued 2026-08-10expires 2026-11-08

DNSSECinsecure

Domain is not signed with DNSSEC

. → me → m.me

Email authenticationpoor

SPF	pass `v=spf1 a ~all`
DMARC	none
DKIM	none of 20 common selectors

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: DMARC Record, DKIM Presence

Advanced Security

15/25missing: Mail Server Configuration

Domain Reputation

50/50

Threat Detection

45/45missing: Domain Age Check

Blocklists0 listings · 5 lookups

SURBL MultidomainURIBL MultidomainSpamCop57.144.230.141Barracuda57.144.230.141UCEPROTECT Level 157.144.230.141

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=m.me" \ -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=m.me"

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

IPv6. Does m.me work over IPv6? See the live check on aaaa.bot — website, mail and nameservers, graded A–F.

Watch m.me. 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