Report feedback, bugs, or edge cases

We welcome feedback about ThreatScope Check, especially where a result is unclear, unexpected, incomplete, or does not handle a real-world domain setup properly.

Good feedback helps us improve the service and make the results more useful.

What you can report

You can contact us about:

bugs or broken behaviour
checks that do not complete
unexpected or inconsistent results
confusing labels or explanations
missing information that you expected to see
legitimate domain configurations that are not handled well
edge cases involving parked, redirected, delegated, or non-sending domains
suggestions that would make the service clearer or more useful

What to include

Please include as much detail as you can.

1. The domain checked

Include the exact domain you entered.

Example:

example.com.au

2. What you expected

Tell us what you expected ThreatScope Check to show.

Examples:

“I expected the domain to show active DNS records.”
“I expected the domain to be recognised as a .au domain.”
“I expected the mail-related result to show configured records.”
“I expected the certificate information to appear.”
“I expected the nameserver provider to be different.”

3. What you saw

Tell us what actually happened.

Examples:

“The check did not complete.”
“The result appeared blank.”
“The DNS section looked incomplete.”
“The explanation did not match what I expected.”
“The result showed an unexpected warning.”
“The same domain gave different results a few minutes apart.”

4. Date and time

Include the approximate date and time of the check.

Please include your timezone if known.

Example:

10 May 2026, approximately 2:30pm AEST

5. Screenshot or copied result

If possible, include a screenshot or copy the relevant part of the result.

This helps us understand exactly what you saw.

6. Recent changes

Please mention whether the domain was recently:

registered
renewed
transferred
delegated to new nameservers
moved to a new DNS provider
connected to a new website or hosting platform
configured for email
changed for redirects, parking, or subdomains

Recent changes are a common reason for unexpected results.

Please do not send sensitive information

Please do not send:

passwords
private keys
API keys
internal-only system details
confidential DNS plans
private customer records
personal information that is not needed for the report

ThreatScope Check works from public signals. In most cases, the domain name and a screenshot or copied result are enough.

Suggested message format

You can copy and use this format when contacting us:

Domain checked:

example.com.au

What I expected:

I expected...

What I saw:

I saw...

Date and time of check:

Approximate date/time and timezone...

Recent domain changes:

Yes / No / Unsure

Screenshot or result details:

Attached or copied here...

What happens next

We will review the report and assess whether it appears to be:

a bug
a temporary lookup issue
an expected limitation
a confusing explanation
a third-party data issue
a domain-specific edge case
a possible improvement for a future version

We may not be able to provide detailed domain advice for every report, but clear examples are valuable and help improve ThreatScope Check over time.

Contacting us

Use the feedback or support contact path and include:

the domain
what you expected
what you saw
the approximate time of the check
any screenshot or copied result details