The call
GET https://kollen.lumrait.se/api/v1/check?domain=example.com
The response is the same ScoreReport the result page is built on: grade, score, three groups (email, DNS, web) with every check, the spoofing verdict, SPF services and DMARC interpretation. Add &lang=en for English texts.
Example with curl:
curl -s "https://kollen.lumrait.se/api/v1/check?domain=example.com&raw=1&lang=en" | jq .
Raw data with raw=1
With &raw=1 every check gets a raw field with the records verbatim (name, type, value, TTL where the resolver provides it), which resolver answered and the timestamp. It is the same evidence shown under "Show technical details" on the result page. Without raw=1 the fields are omitted so the response is smaller.
Limits and errors
30 calls per hour per IP address. The response is cached for 10 minutes (Cache-Control: public, max-age=600). The X-RateLimit-Remaining and X-RateLimit-Reset headers show where you stand.
Errors respond with JSON and status 400 (invalid domain), 429 (too many calls, with Retry-After) or 502 (the check could not run). The check runs live against public DNS, web and certificate data, so a response normally takes a few seconds.
What it is not
The API performs exactly the same check as the result page, no more and no less. It does not look inside your Microsoft 365 environment. If you want that picture, PIANOLA is the next step.