Identity
38
C
tvg.com
Posture Score: 71/100
Scanned May 8, 2026 at 6:51 PM UTC
Attack Surface
87
Reputation
88
Identity Findings
Open recursion on nameserver: ns-39.awsdns-04.com
The nameserver ns-39.awsdns-04.com allows recursive queries from external sources, making it vulnerable to DNS amplification attacks.
💡 Disable recursion on ns-39.awsdns-04.com or restrict it to trusted networks only.
No DKIM records found
No DKIM records were found for any common selector. Email may not be authenticated.
💡 Configure DKIM signing and publish the public key at <selector>._domainkey.tvg.com
FCrDNS failure: no PTR for 52.101.9.17 (tvg-com.mail.protection.outlook.com)
The IP 52.101.9.17 has no PTR record. Forward-confirmed reverse DNS requires a PTR that resolves back to the IP.
💡 Configure a PTR record for the IP that matches the mail server hostname.
DMARC policy is monitoring-only (p=none)
The p=none policy only monitors; it does not instruct receivers to quarantine or reject unauthenticated mail.
💡 Upgrade to p=quarantine or p=reject after reviewing aggregate reports.
No PTR record for MX IP: 52.101.9.17
The IP 52.101.9.17 (for tvg-com.mail.protection.outlook.com) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
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.tvg.com/.well-known/mta-sts.txt
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.
No CAA records found
No CAA records are configured. Any certificate authority can issue certificates for this domain.
💡 Add CAA records to restrict certificate issuance. Example: 0 issue "letsencrypt.org"
Void lookup: mx:maila.tvg.com
The mechanism mx:maila.tvg.com returns no records, wasting a DNS lookup.
💡 Remove mechanisms that reference non-existent domains.
Void lookup: mx:mailb.tvg.com
The mechanism mx:mailb.tvg.com returns no records, wasting a DNS lookup.
💡 Remove mechanisms that reference non-existent domains.
Void lookup: include:xmail.paddypowerbetfair.com
The mechanism include:xmail.paddypowerbetfair.com returns no records, wasting a DNS lookup.
💡 Remove mechanisms that reference non-existent domains.
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@tvg.com").
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.
Slow DNS response from ns-39.awsdns-04.com: 2078.5ms
The nameserver ns-39.awsdns-04.com responded in 2078.5ms, exceeding the 500ms threshold.
💡 Investigate network latency or performance issues on ns-39.awsdns-04.com.
Very low TTL on MX record: 88s
The MX record has a TTL of 88s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on A records: 60s
4 A records have a TTL of 60s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on TXT records: 28s
7 TXT records have a TTL of 28s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on SPF record: 28s
The SPF record has a TTL of 28s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
NS TTL mismatch between parent and authoritative zone
The NS record TTL in the parent zone (~7187s) differs significantly from the authoritative zone (~172800s).
💡 Align NS record TTLs between the parent zone delegation and the authoritative zone.
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
No deprecated DMARCbis tags present
The DMARC record does not use any tags deprecated in DMARCbis (pct, rf, ri).
ARC support likely available
MX server software appears to support ARC headers for authentication preservation.
SMTP security checks passed
No open relay, VRFY/EXPN, or banner disclosure issues detected.
SMTP RFC 5321 compliance checks passed
The mail server accepts postmaster@ and abuse@ and uses a valid FQDN in EHLO.
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.
DMARC alignment: adkim=r, aspf=r
DKIM alignment is relaxed, SPF alignment is relaxed.
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.
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.
No DANE/TLSA records found
DANE is not configured for any MX server. This is optional but provides strong certificate binding.
No BIMI record found
BIMI is not configured. Your brand logo will not display in supporting email clients.
Open mail ports on tvg-com.mail.protection.outlook.com
Detected open mail-related ports: 25
RFC 8058 one-click unsubscribe assessment
No DKIM signing detected. RFC 8058 one-click unsubscribe requires DKIM-signed List-Unsubscribe headers.
MX IP network diversity
All MX IPs are in the same /16 network. Consider diversifying across networks for resilience.
SOA record parameters
Serial: 1, Refresh: 7200s, Retry: 900s, Expire: 1209600s, Min TTL: 86400s
Attack Surface Findings
Domain enumerability: high
The domain is highly enumerable. Zone transfers, NSEC zone walking, or a combination of factors make it easy to discover all DNS records.
💡 Restrict zone transfers, use NSEC3 instead of NSEC, consider wildcard certificates to reduce CT log exposure, and implement rate limiting on DNS queries.
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.
DNS ANY query returns 18 record(s)
The DNS server responds to ANY queries with 18 record(s). The low record count limits amplification risk, but ANY responses still aid reconnaissance.
💡 Configure the DNS server to refuse or minimize ANY query responses per RFC 8482.
No internal information leakage detected
No non-routable IP addresses or internal references were found in public DNS records.
No email autodiscovery endpoints detected
No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.
127 subdomain(s) discovered for tvg.com
Subdomains were enumerated via Certificate Transparency logs, DNS wordlist brute-forcing, and DNS record analysis.
1055 certificate(s) found in CT logs
Certificate Transparency logs contain 1055 certificate(s) for tvg.com and its subdomains. Each certificate reveals subdomain names.
Reputation Findings
Missing domain locks: clientDeleteProhibited
Domain tvg.com is missing protective locks: clientDeleteProhibited.
💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.
Missing Strict-Transport-Security on tvg.com
The Strict-Transport-Security header is not set on https://tvg.com.
💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.
security.txt present
Found security.txt at https://tvg.com/.well-known/security.txt.
TLS certificate valid for 195 days
Certificate for tvg.com expires on 2026-11-19.
Certificate issued by Amazon RSA 2048 M01
The certificate for tvg.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for tvg.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for tvg.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for tvg.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on tvg.com.
Domain valid for 1601 days
Domain tvg.com expires on 2030-09-26.
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.
Abuse contact lookup failed
Could not query abuse contact information.
PhishTank — API key required
PhishTank phishing database check requires an API key.
Sender Score — API key required
Sender Score reputation check requires an API key.
Cisco Talos — API key required
Cisco Talos IP reputation check requires an API key.
Could not connect to webmail.tvg.com
HTTPS request to https://webmail.tvg.com failed or timed out.
WHOIS registration data
Registrar: Network Solutions, LLC | Created: 1997-09-27 | Expires: 2030-09-26 | Updated: 2025-07-28
WHOIS privacy protection not detected
Domain tvg.com does not appear to have WHOIS privacy protection. Registrant details may be publicly visible.
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: none
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: none
⚠️ 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: tvg-com.mail.protection.outlook.com
PTR record proves mail server legitimacy
MX: tvg-com.mail.protection.outlook.com
Mail server at 52.101.40.6
→
PTR Record
Reverse DNS: mail-cy1pr03cu00106.inbound.protection.outlook.com
Mail Server Reputation: tvg-com.mail.protection.outlook.com
RBL check ensures server is not blacklisted
MX: tvg-com.mail.protection.outlook.com
Mail server at 52.101.40.6
→
RBL Status
Not blacklisted
Enforced Encryption Chain
MTA-STS enforces TLS encryption to prevent man-in-the-middle attacks
TLS Support
Mail servers support TLS encryption
→
MTA-STS Policy
MTA-STS not configured
⚠️ MTA-STS policy is missing. Even with TLS support, you lack the enforcement layer that prevents attackers from stripping encryption (downgrade attacks).
Brand Identity Chain
BIMI displays your logo in email clients, but requires DMARC enforcement
DMARC Enforcement
DMARC not enforced (p=none or missing)
→
BIMI Record
BIMI not configured
⚠️ DMARC is not enforced. BIMI requires a DMARC policy of "quarantine" or "reject" to prove you have strong email authentication. Without enforcement, email clients will not display your logo.
TLS Monitoring Chain
TLS-RPT provides reports about TLS connection failures
TLS Support
Mail servers support TLS encryption
→
TLS-RPT Reporting
TLS-RPT not configured
⚠️ TLS-RPT is not configured. Without TLS reporting, you have no visibility into TLS connection failures that may be impacting email delivery.
Security Checks
MX Records
✓
SPF Record
✓
DKIM Record
✗
DMARC Policy
✓
BIMI Record
✗
CAA Records
✗
DNSSEC
✗
MTA-STS
✗
TLS-RPT
✗
Embed Badge
Display your domain's security grade on your website or README:
<img src="https://scan.ractermx.com/badge/tvg.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan tvg.com Again