SurfaceMap › s › screenconnect.com

screenconnect.com

Checked 2026-10-22 10:35 UTC · first added 2026-10-21

✗Problems found Score 69 of 100

Domain & DNS

warn

24 passed 3 warn 0 failed

Areas

iRegistration iDelegation ✓Nameservers !SOA !DNSSEC !Records

Problems

!

Unusual SOA timers

SOA · negative caching TTL (minimum) 30s is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 2h, retry 15m, expire 14d, negative TTL 30s.

#23
!

Not signed

DNSSEC · The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.

#27
!

Very low TTLs

Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (1m). Low TTLs are useful just before a planned change.

#32

Recent checks

!

Full report

Domain & DNS report for screenconnect.com ›

Mail

fail

24 passed 4 warn 1 failed

Areas

✓SPF !DMARC ✗DKIM !DNSSEC !MX !TLS ✓BIMI

Problems

✗

No DKIM keys published

DKIM · _domainkey.screenconnect.com does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.

#7
!

Policy: quarantine

DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.

#4
!

Not enabled

DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.

#8
!

Hosts without IPv6

MX · The following MX hosts could not be resolved to IPv6 addresses: mxa-005c1903.gslb.pphosted.com, mxb-005c1903.gslb.pphosted.com

#11
!

Not configured

TLS · MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.

#32

Recent checks

✗

Full report

Mail report for screenconnect.com ›