HOW.IS
?

How is gmx.net?

Looks fine risk 0/100

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

Why

02050100
finecarefulhigh risk
  • ·Nothing in the checks added risk.

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

How gmx.net looks right now
The home page, rendered by how.is in a sandboxed browser. Nothing on it is clickable here.
Site
200
1091 ms · ends at www.gmx.net
HTTPS
116 d
left on a Deutsche Telekom Security GmbH certificate
Age
28 years
registered 1998-12-09
Blocklists
0
listings across 5 lists

Everything we looked at

DNS records5 record types
A217.72.199.108
217.72.199.107
MX10 mx01.emig.gmx.net
10 mx00.emig.gmx.net
NSns-gmx.ui-dns.org
ns-gmx.ui-dns.de
ns-gmx.ui-dns.biz
ns-gmx.ui-dns.com
TXTv=spf1 redirect=_spf.gmx.net
179gjz475x3lvxbtsv2mn24vc1l1q9tb
_y2d5dltm3p20lx7wcyricp3kznhs9h8
vxxrjnnhhz1vd8r51zps6swntc43k2j1
w7v6rl78mskdw1fk8t8cllpj5fv39ngc
_y2d5dltm3p20lx7wcyricp3kznhs9h8
facebook-domain-verification=scdn4fwr0on3j97l5py9vp9raerciu
Trustpilot-Verification-kqvVskCm6JQ9Vg1qAmahpBSJ5tvZORbriFyVIk4E
google-site-verification=-X7cUj6mlDVPON6zf57-7HVItFAApOOxjv5HMcGO_qQ
google-site-verification=J0NZ2F6kdhXzsguHSKZTm3CWujnrImftkDG3zhz14g0
google-site-verification=hfRWhDjYh9zG3LL_izYa1DCJQQgm3oqyn3Tn_hDr59Q
CAA{'type': 'CAA', 'critical': 0, 'issuewild': 'telesec.de'}
{'type': 'CAA', 'issue': 'sectigo.com', 'critical': 0}
{'type': 'CAA', 'issue': 'telesec.de', 'critical': 0}
{'type': 'CAA', 'issue': 'Digicert.com', 'critical': 0}
{'type': 'CAA', 'critical': 0, 'issuewild': 'digicert.com'}
{'type': 'CAA', 'critical': 0, 'issuewild': 'sectigo.com'}
RegistrationWorld4You Internet Services GmbH
registrarWorld4You Internet Services GmbH
registered1998-12-09
expires2026-12-08
last changed2025-12-09
nameserversns-gmx.ui-dns.biz
ns-gmx.ui-dns.com
ns-gmx.ui-dns.de
ns-gmx.ui-dns.org
statusclient transfer prohibited
registered 1998-12-09expires 2026-12-08
HTTPS certificate116 days left
validyes
issuerDeutsche Telekom Security GmbH
covers*.gmx.net, gmx.net
protocolTLSv1.3
issued 2026-08-12expires 2027-02-25
DNSSECsecure

Domain is properly signed — chain validated by an independent validating resolver

. → net → gmx.net
Email authenticationfair
SPFwarning v=spf1 redirect=_spf.gmx.net
DMARCpass policy quarantine
DKIMnone of 1 common selectors

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

Security scoregrade B · 168/205
Basic Security
20/40missing: DNSSEC Enabled
Record Security
38/45missing: SPF 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 MultidomainSpamCop217.72.199.108Barracuda217.72.199.108UCEPROTECT Level 1217.72.199.108SpamCop217.72.199.107Barracuda217.72.199.107UCEPROTECT Level 1217.72.199.107

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

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

IPv6. IPv6 readiness grade for gmx.net Does gmx.net work over IPv6? See the live check on aaaa.bot — website, mail and nameservers, graded A–F.

Watch gmx.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