stspg-customer.com

Name: stspg-customer.com Email Security Posture Assessment
Creator: RacterMX
License: https://creativecommons.org/licenses/by-nc/4.0/

Posture Score: 80/100

Scanned May 30, 2026 at 12:07 AM UTC

Identity

Attack Surface

Reputation

Identity Findings

External report destination not authorized: abuse.atlassian.com

The rua= URI sends reports to abuse.atlassian.com, but no authorization record exists at stspg-customer.com._report._dmarc.abuse.atlassian.com. Reports will be silently dropped by compliant receivers.

💡 Ask the owner of abuse.atlassian.com to publish a TXT record at stspg-customer.com._report._dmarc.abuse.atlassian.com containing 'v=DMARC1'.

high

External report destination not authorized: abuse.atlassian.com

The ruf= URI sends reports to abuse.atlassian.com, but no authorization record exists at stspg-customer.com._report._dmarc.abuse.atlassian.com. Reports will be silently dropped by compliant receivers.

💡 Ask the owner of abuse.atlassian.com to publish a TXT record at stspg-customer.com._report._dmarc.abuse.atlassian.com containing 'v=DMARC1'.

high

SPF record is 566 bytes (UDP truncation risk)

SPF records exceeding ~450 bytes risk UDP truncation, causing TCP fallback failures on some resolvers. This can lead to intermittent SPF failures.

💡 Consolidate SPF mechanisms, remove unused includes, or use an SPF flattening service to reduce record size.

medium

No DKIM records found

No DKIM records were found after probing 56 common selectors. The domain may use a custom selector not discoverable via external scan.

💡 Configure DKIM signing and publish the public key at <selector>._domainkey.stspg-customer.com

medium

External DMARC report destination not authorized: abuse.atlassian.com

The rua= URI points to abuse.atlassian.com but no authorization record exists at stspg-customer.com._report._dmarc.abuse.atlassian.com.

💡 Ask the owner of abuse.atlassian.com to publish a TXT record at stspg-customer.com._report._dmarc.abuse.atlassian.com with 'v=DMARC1'.

medium

No MTA-STS record found

Without MTA-STS, mail transport encryption cannot be enforced and is vulnerable to downgrade attacks.

💡 Publish a _mta-sts TXT record and host a policy file at https://mta-sts.stspg-customer.com/.well-known/mta-sts.txt

medium

STARTTLS without MTA-STS or DANE protection

STARTTLS alone is vulnerable to downgrade attacks. Neither MTA-STS nor DANE is configured to enforce encryption.

💡 Deploy MTA-STS and/or DANE to protect against STARTTLS stripping attacks.

medium

No TLS-RPT record found

Without TLS-RPT, you will not receive reports about TLS negotiation failures.

💡 Publish a _smtp._tls TXT record (e.g. "v=TLSRPTv1; rua=mailto:tls-reports@stspg-customer.com").

low

SPF has ip4 mechanisms but no ip6

The SPF record authorizes IPv4 addresses but not IPv6. Your MX servers have AAAA records, so IPv6 mail delivery is possible without SPF authorization.

💡 Add ip6: mechanisms to the SPF record for your IPv6 mail server addresses.

low

No CAA iodef tag configured

No iodef tag is present in the CAA records. CA policy violation reports will not be sent.

💡 Add an iodef CAA record. Example: 0 iodef "mailto:security@example.com"

low

Very low TTL on MX records: 60s

7 MX records have a TTL of 60s or less (below 300s).

💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.

low

Very low TTL on SPF record: 60s

The SPF record has a TTL of 60s or less (below 300s).

💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.

low

SPF record is valid

The SPF record is properly configured with valid syntax and within lookup limits.

pass

DKIM cryptographic configuration is compliant

No RFC 8301 compliance issues detected in DKIM key configuration.

pass

Subdomains protected (sp=reject)

DMARC subdomain policy enforces quarantine or reject on unauthenticated subdomain mail.

pass

No deprecated DMARCbis tags present

The DMARC record does not use any tags deprecated in DMARCbis (pct, rf, ri).

pass

ARC support likely available

MX server software appears to support ARC headers for authentication preservation.

pass

Meets bulk sender authentication requirements

Domain has SPF, DKIM, and DMARC — meeting Google/Yahoo 2024 bulk sender requirements for email authentication.

pass

SMTP security checks passed

No open relay, VRFY/EXPN, or banner disclosure issues detected.

pass

SMTP RFC 5321 compliance checks passed

The mail server accepts postmaster@ and abuse@ and uses a valid FQDN in EHLO.

pass

NS delegation is properly configured

All nameservers are responsive, consistent, and properly secured.

pass

DNS responses are consistent across all nameservers

All authoritative nameservers return consistent answers with proper AA flags.

pass

DKIM2 not detected

No DKIM key record with v=2 was found across common selectors. DKIM2 is an emerging standard and not yet widely deployed.

informational

DMARC alignment: adkim=s, aspf=s

DKIM alignment is strict, SPF alignment is strict.

informational

DMARC failure reporting: fo=1

Failure reports generated when any authentication mechanism fails.

informational

DMARCbis np tag absent

The DMARC record does not include the np (non-existent subdomain policy) tag. Consider adding np=reject to protect non-existent subdomains under DMARCbis.

informational

DMARCbis psd tag absent

The DMARC record does not include the psd (public suffix domain) indicator. Consider adding psd=n to explicitly identify this as an organizational domain.

informational

Shared/free email hosting detected: aspmx.l.google.com

The MX record points to a known shared or free email hosting provider.

informational

Shared/free email hosting detected: alt1.aspmx.l.google.com

The MX record points to a known shared or free email hosting provider.

informational

Shared/free email hosting detected: alt2.aspmx.l.google.com

The MX record points to a known shared or free email hosting provider.

informational

REQUIRETLS not advertised

The primary MX does not advertise REQUIRETLS (RFC 8689). This is an emerging standard — MTA-STS and DANE provide adequate TLS enforcement for most deployments.

informational

No DANE/TLSA records found

DANE is not configured for any MX server. This is optional but provides strong certificate binding.

informational

No BIMI record found

BIMI is not configured. Your brand logo will not display in supporting email clients.

informational

Open mail ports on aspmx.l.google.com

Detected open mail-related ports: 25

informational

RFC 8058 one-click unsubscribe assessment

No DKIM signing detected. RFC 8058 one-click unsubscribe requires DKIM-signed List-Unsubscribe headers.

informational

MX IP network diversity

MX IPs span 5 different /16 networks, providing good diversity.

informational

SOA record parameters

Serial: 1, Refresh: 7200s, Retry: 900s, Expire: 1209600s, Min TTL: 86400s

informational

Authorized certificate authorities

CAA records restrict certificate issuance to: letsencrypt.org, digicert.com, amazon.com, globalsign.com

informational

Attack Surface Findings

DNSSEC is not enabled

No DNSKEY or DS records were found. DNS responses are not cryptographically authenticated.

💡 Enable DNSSEC by generating DNSKEY records and publishing DS records at the registrar.

medium

Domain enumerability: low

The domain has low enumerability. Proper NSEC3 configuration and limited CT exposure reduce the attack surface.

low

No subdomain takeover risks detected

All checked subdomains have valid, responsive targets.

pass

All MX records resolve correctly

No dangling MX records detected — all MX hostnames resolve to valid IP addresses.

pass

Explicit MX records present

The domain has explicit MX records — no implicit A-record fallback delivery.

pass

No internal information leakage detected

No non-routable IP addresses or internal references were found in public DNS records.

pass

No excessive DNS information exposure detected

No HINFO, LOC, RP records, version disclosures, or zone walking vulnerabilities were found.

pass

0 subdomain(s) discovered for stspg-customer.com

Subdomains were enumerated via Certificate Transparency logs, DNS wordlist brute-forcing, and DNS record analysis.

informational

19 certificate(s) found in CT logs

Certificate Transparency logs contain 19 certificate(s) for stspg-customer.com and its subdomains. Each certificate reveals subdomain names.

informational

Wildcard DNS record detected

A wildcard DNS record exists for *.stspg-customer.com, resolving to 104.192.142.23, 104.192.142.21, 104.192.142.22. Wildcard records make subdomain brute-forcing less effective but may mask misconfigurations.

informational

Microsoft Autodiscover endpoint detected

The Autodiscover endpoint at autodiscover.stspg-customer.com responded with HTTP 404.

informational

Reputation Findings

Could not retrieve TLS certificate

Failed to connect to stspg-customer.com:443 or retrieve the peer certificate.

💡 Ensure the domain has a valid TLS certificate installed and port 443 is accessible.

critical

Not listed on any DNS blacklists

Domain and MX IPs checked against 55 DNSBLs — no listings found.

pass

HSTS enabled with preload on webmail.stspg-customer.com

Strict-Transport-Security: max-age=63072000; preload

pass

Domain valid for 273 days

Domain stspg-customer.com expires on 2027-02-27.

pass

Domain transfer and delete locks enabled

Domain stspg-customer.com has clientTransferProhibited and clientDeleteProhibited locks.

pass

No disposable email provider MX records

MX records for stspg-customer.com do not match known disposable email provider patterns.

pass

Domain is 4109 days old

Domain stspg-customer.com was registered 2015-02-27.

pass

No wildcard MX records

No wildcard MX records detected for stspg-customer.com.

pass

TLD has good reputation

The .com TLD is not on known abuse watchlists.

pass

DMARC reporting destinations look legitimate

DMARC rua/ruf addresses do not point to known URL shortener services.

pass

MX records point to stable infrastructure

No MX records point to known dynamic DNS service domains.

pass

Strong TLS configuration on primary MX

Primary MX (aspmx.l.google.com) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.

pass

SMTP banner from hosted mail provider

The MX (aspmx.l.google.com) is a hosted mail service. Banner alignment is managed by the provider and not actionable by the domain owner.

pass

No registered typosquat domains detected

None of the common typosquat mutations of this domain appear to be registered by third parties.

pass

Google Safe Browsing DNS check — no flag detected

DNS-based Safe Browsing lookup returned no results. Full verification requires the Google Safe Browsing API key.

informational

Abuse contacts found for MX IPs

Abuse contact information retrieved via abusix.org DNS lookup.

informational

PhishTank — API key required

PhishTank phishing database check requires an API key.

informational

Sender Score — API key required

Sender Score reputation check requires an API key.

informational

Cisco Talos — API key required

Cisco Talos IP reputation check requires an API key.

informational

Could not connect to stspg-customer.com

HTTPS request to https://stspg-customer.com failed or timed out.

informational

WHOIS registration data

Registrar: MarkMonitor Inc. | Created: 2015-02-27 | Expires: 2027-02-27 | Updated: 2025-01-26

informational

WHOIS privacy protection not detected

Domain stspg-customer.com does not appear to have WHOIS privacy protection. Registrant details may be publicly visible.

informational

Bulletproof Hosting Detection — API key required

Checking IPs against known bulletproof hosting providers requires a threat intelligence API key.

informational

Threat Intelligence Feeds — API key required

Checking domain against threat intelligence feeds requires API keys (e.g., VirusTotal, AbuseIPDB).

informational

Dependency Chains

DMARC Authentication Chain (SPF)

DMARC uses SPF to verify that emails come from authorized servers

SPF Record SPF record found and configured → DMARC Policy DMARC policy: reject

DMARC Authentication Chain (DKIM)

DMARC uses DKIM to verify that emails have not been tampered with

DKIM Signature DKIM signature missing → DMARC Policy DMARC policy: reject

⚠️ DKIM signature is missing. DMARC relies on DKIM to verify email integrity and prevent tampering. Without DKIM, DMARC alignment will fail for cryptographic verification.

Mail Server Identity: aspmx.l.google.com

PTR record proves mail server legitimacy

MX: aspmx.l.google.com Mail server at 74.125.193.27 → PTR Record Reverse DNS: ig-in-f27.1e100.net

Mail Server Identity: alt1.aspmx.l.google.com

PTR record proves mail server legitimacy

MX: alt1.aspmx.l.google.com Mail server at 173.194.76.26 → PTR Record Reverse DNS: ws-in-f26.1e100.net

Mail Server Identity: alt2.aspmx.l.google.com

PTR record proves mail server legitimacy

MX: alt2.aspmx.l.google.com Mail server at 142.250.102.27 → PTR Record Reverse DNS: rb-in-f27.1e100.net

Mail Server Identity: aspmx2.googlemail.com

PTR record proves mail server legitimacy

MX: aspmx2.googlemail.com Mail server at 173.194.76.26 → PTR Record Reverse DNS: ws-in-f26.1e100.net

Mail Server Identity: aspmx3.googlemail.com

PTR record proves mail server legitimacy

MX: aspmx3.googlemail.com Mail server at 142.250.102.27 → PTR Record Reverse DNS: rb-in-f27.1e100.net

Mail Server Identity: aspmx4.googlemail.com

PTR record proves mail server legitimacy

MX: aspmx4.googlemail.com Mail server at 192.178.213.27 → PTR Record Reverse DNS: yugrqzs-in-f27.1e100.net

Mail Server Identity: aspmx5.googlemail.com

PTR record proves mail server legitimacy

MX: aspmx5.googlemail.com Mail server at 142.251.127.26 → PTR Record Reverse DNS: lcfrai-in-f26.1e100.net

Mail Server Reputation: aspmx.l.google.com