playfabapi.com

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

Posture Score: 71/100

Scanned May 28, 2026 at 12:16 AM UTC

Identity

Attack Surface

Reputation

Identity Findings

No SPF record found

The domain has no SPF record, allowing anyone to send email as this domain.

💡 Publish an SPF TXT record (e.g. "v=spf1 include:_spf.google.com -all").

critical

No DMARC record found

The domain has no DMARC record, providing no policy for handling unauthenticated email.

💡 Publish a DMARC TXT record at _dmarc.playfabapi.com (e.g. "v=DMARC1; p=reject; rua=mailto:dmarc@playfabapi.com").

critical

Does not meet bulk sender requirements

Google and Yahoo require all bulk senders to have SPF+DKIM, DMARC, and one-click unsubscribe. Issues: Neither SPF nor DKIM is configured (at least one required); No DMARC record published (required since Feb 2024); SPF not published (recommended alongside DKIM)

💡 Publish SPF, DKIM, and DMARC records. Implement RFC 8058 one-click unsubscribe for marketing mail.

high

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.playfabapi.com

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.playfabapi.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@playfabapi.com").

low

Very low TTL on TXT record: 60s

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

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

low

DKIM cryptographic configuration is compliant

No RFC 8301 compliance issues detected in DKIM key configuration.

pass

ARC support likely available

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

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

IPv6 readiness is good

IPv6 records are present and properly configured.

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

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 3 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: microsoft.com, amazon.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

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

21 subdomain(s) discovered for playfabapi.com

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

informational

0 certificate(s) found in CT logs

Certificate Transparency logs contain 0 certificate(s) for playfabapi.com and its subdomains. Each certificate reveals subdomain names.

informational

Wildcard DNS record detected

A wildcard DNS record exists for *.playfabapi.com, resolving to 150.171.109.241. Wildcard records make subdomain brute-forcing less effective but may mask misconfigurations.

informational

Microsoft Autodiscover endpoint detected (authenticated)

The Autodiscover endpoint at autodiscover.playfabapi.com is active and requires authentication.

informational

Reputation Findings

Could not retrieve TLS certificate

Failed to connect to playfabapi.com:443 or retrieve the peer certificate.

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

critical

Domain expires in 56 days

Domain playfabapi.com expires on 2026-07-23 (56 days).

💡 Renew the domain registration soon — it expires within 60 days. Enable auto-renewal if available.

high

Missing Strict-Transport-Security on webmail.playfabapi.com

The Strict-Transport-Security header is not set on https://webmail.playfabapi.com.

💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.

medium

Wildcard MX records detected

Domain playfabapi.com has wildcard MX records, which can be abused for spam or phishing.

💡 Remove wildcard MX records and configure explicit MX entries only for legitimate mail-handling subdomains.

medium

Not listed on any DNS blacklists

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

pass

Domain transfer and delete locks enabled

Domain playfabapi.com has clientTransferProhibited and clientDeleteProhibited locks.

pass

No disposable email provider MX records

MX records for playfabapi.com do not match known disposable email provider patterns.

pass

Domain is 4326 days old

Domain playfabapi.com was registered 2014-07-23.

pass

TLD has good reputation

The .com TLD is not on known abuse watchlists.

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 playfabapi.com

HTTPS request to https://playfabapi.com failed or timed out.

informational

WHOIS registration data

Registrar: Nom-iq Ltd. dba COM LAUDE | Created: 2014-07-23 | Expires: 2026-07-23 | Updated: 2025-06-23

informational

WHOIS privacy protection not detected

Domain playfabapi.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 missing → DMARC Policy DMARC policy missing

⚠️ SPF record is missing. DMARC relies on SPF to verify sender authorization. Without SPF, DMARC alignment will fail, reducing email deliverability and brand protection.

DMARC Authentication Chain (DKIM)

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

DKIM Signature DKIM signature configured → DMARC Policy DMARC policy missing

⚠️ DMARC policy is missing. Even with DKIM configured, you lack the policy layer that tells receiving servers what to do with authentication failures.

Mail Server Identity: aspmx.l.google.com

PTR record proves mail server legitimacy

MX: aspmx.l.google.com Mail server at 74.125.193.26 → PTR Record Reverse DNS: di-in-f26.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.26 → PTR Record Reverse DNS: rb-in-f26.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.26 → PTR Record Reverse DNS: rb-in-f26.1e100.net

Mail Server Reputation: aspmx.l.google.com