Identity
0
F
mgslb.com
Posture Score: 45/100
Scanned May 28, 2026 at 3:47 AM UTC
Attack Surface
39
Reputation
96
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").
No DMARC record found
The domain has no DMARC record, providing no policy for handling unauthenticated email.
💡 Publish a DMARC TXT record at _dmarc.mgslb.com (e.g. "v=DMARC1; p=reject; rua=mailto:dmarc@mgslb.com").
No NS records found
No nameserver records could be retrieved for this domain.
💡 Ensure NS records are properly configured at your registrar and in your zone file.
MX hostname resolves via CNAME: iot-ota-cdn.io.mi.com.bsgslb.cn
MX records should not point to a CNAME (RFC 2181). This can cause delivery failures.
💡 Point the MX record directly to an A/AAAA record, not a CNAME.
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.
FCrDNS failure: no PTR for 60.9.3.151 (iot-ota-cdn.io.mi.com.bsgslb.cn)
The IP 60.9.3.151 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.
FCrDNS failure: no PTR for 60.9.3.168 (iot-ota-cdn.io.mi.com.bsgslb.cn)
The IP 60.9.3.168 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.
FCrDNS failure: no PTR for 60.9.3.146 (iot-ota-cdn.io.mi.com.bsgslb.cn)
The IP 60.9.3.146 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.
FCrDNS failure: no PTR for 60.9.3.147 (iot-ota-cdn.io.mi.com.bsgslb.cn)
The IP 60.9.3.147 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.
FCrDNS failure: no PTR for 60.9.3.167 (iot-ota-cdn.io.mi.com.bsgslb.cn)
The IP 60.9.3.167 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.
FCrDNS failure: no PTR for 60.9.3.154 (iot-ota-cdn.io.mi.com.bsgslb.cn)
The IP 60.9.3.154 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.
FCrDNS failure: no PTR for 60.9.3.146 (xmrhdl.v.bsgslb.cn)
The IP 60.9.3.146 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.
FCrDNS failure: no PTR for 60.9.3.151 (xmrhdl.v.bsgslb.cn)
The IP 60.9.3.151 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.
FCrDNS failure: no PTR for 60.9.3.167 (xmrhdl.v.bsgslb.cn)
The IP 60.9.3.167 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.
FCrDNS failure: no PTR for 60.9.3.154 (xmrhdl.v.bsgslb.cn)
The IP 60.9.3.154 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.
FCrDNS failure: no PTR for 60.9.3.168 (xmrhdl.v.bsgslb.cn)
The IP 60.9.3.168 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.
FCrDNS failure: no PTR for 60.9.3.147 (xmrhdl.v.bsgslb.cn)
The IP 60.9.3.147 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.
Cannot check DNS consistency — no NS records
No nameserver records could be retrieved for consistency checking.
💡 Ensure NS records are properly configured.
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.mgslb.com
No PTR record for MX IP: 60.9.3.151
The IP 60.9.3.151 (for iot-ota-cdn.io.mi.com.bsgslb.cn) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
No PTR record for MX IP: 60.9.3.168
The IP 60.9.3.168 (for iot-ota-cdn.io.mi.com.bsgslb.cn) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
No PTR record for MX IP: 60.9.3.146
The IP 60.9.3.146 (for iot-ota-cdn.io.mi.com.bsgslb.cn) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
No PTR record for MX IP: 60.9.3.147
The IP 60.9.3.147 (for iot-ota-cdn.io.mi.com.bsgslb.cn) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
No PTR record for MX IP: 60.9.3.167
The IP 60.9.3.167 (for iot-ota-cdn.io.mi.com.bsgslb.cn) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
No PTR record for MX IP: 60.9.3.154
The IP 60.9.3.154 (for iot-ota-cdn.io.mi.com.bsgslb.cn) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
No PTR record for MX IP: 60.9.3.146
The IP 60.9.3.146 (for xmrhdl.v.bsgslb.cn) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
No PTR record for MX IP: 60.9.3.151
The IP 60.9.3.151 (for xmrhdl.v.bsgslb.cn) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
No PTR record for MX IP: 60.9.3.167
The IP 60.9.3.167 (for xmrhdl.v.bsgslb.cn) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
No PTR record for MX IP: 60.9.3.154
The IP 60.9.3.154 (for xmrhdl.v.bsgslb.cn) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
No PTR record for MX IP: 60.9.3.168
The IP 60.9.3.168 (for xmrhdl.v.bsgslb.cn) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
No PTR record for MX IP: 60.9.3.147
The IP 60.9.3.147 (for xmrhdl.v.bsgslb.cn) 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.mgslb.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"
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@mgslb.com").
ARC support not detected
No evidence of ARC (Authenticated Received Chain) support on MX servers. Forwarded messages may lose authentication.
💡 Consider enabling ARC signing on your mail servers to preserve authentication through forwarding.
Shared IP 60.9.3.151 used by multiple MX servers
The IP 60.9.3.151 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
Shared IP 60.9.3.168 used by multiple MX servers
The IP 60.9.3.168 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
Shared IP 60.9.3.146 used by multiple MX servers
The IP 60.9.3.146 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
Shared IP 60.9.3.147 used by multiple MX servers
The IP 60.9.3.147 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
Shared IP 60.9.3.167 used by multiple MX servers
The IP 60.9.3.167 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
Shared IP 60.9.3.154 used by multiple MX servers
The IP 60.9.3.154 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
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.
Mail server port configuration is acceptable
No concerning port exposure detected.
DNS TTL values follow best practices
All critical DNS record TTLs are within recommended ranges.
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.
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.
Domain is IPv4-only
No AAAA records found for the domain, MX servers, or nameservers. The domain operates on IPv4 only.
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: 1779863359, Refresh: 3600s, Retry: 180s, Expire: 1209600s, Min TTL: 180s
Attack Surface Findings
AXFR zone transfer allowed on ns4.dnsv5.com
The nameserver ns4.dnsv5.com allows AXFR zone transfers, exposing the complete zone contents to anyone. This is the most severe enumerability issue.
💡 Restrict AXFR transfers on ns4.dnsv5.com to authorized secondary nameservers only using allow-transfer ACLs.
AXFR zone transfer allowed on ns3.dnsv5.com
The nameserver ns3.dnsv5.com allows AXFR zone transfers, exposing the complete zone contents to anyone. This is the most severe enumerability issue.
💡 Restrict AXFR transfers on ns3.dnsv5.com to authorized secondary nameservers only using allow-transfer ACLs.
NSEC records enable zone walking
The domain uses NSEC records for DNSSEC authenticated denial of existence. NSEC records can be walked to enumerate all names in the zone, effectively disclosing the entire zone contents.
💡 Switch from NSEC to NSEC3 with opt-out to prevent zone enumeration. Use NSEC3 with a random salt and sufficient iterations.
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.
Non-mail domain has no SPF record
This domain has no MX records (does not receive mail) but also has no SPF record. Without "v=spf1 -all", attackers can spoof this domain in phishing emails.
💡 Publish "v=spf1 -all" to explicitly declare this domain sends no mail.
HINFO record exposes system information
An HINFO record for mgslb.com reveals hardware/OS details: CPU=, OS=. This aids attacker reconnaissance.
💡 Remove the HINFO record from public DNS. HINFO records are rarely needed and expose unnecessary system details.
LOC record exposes geographic location
A LOC record for mgslb.com reveals the physical location of infrastructure. This aids targeted attacks.
💡 Remove the LOC record from public DNS unless geographic information is intentionally published.
No MX records — A-record fallback active
The domain has no MX records but has an A record. Per RFC 5321, mail servers will attempt delivery to the A record IP. This domain may be silently accepting mail without SPF/DKIM/DMARC protection.
💡 If this domain should not receive mail, publish a Null MX record (RFC 7505): "0 ." as the MX. If it should receive mail, add proper MX records.
DNS ANY query returns 6 record(s)
The DNS server responds to ANY queries with 6 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.
RP record exposes responsible person
An RP (Responsible Person) record for mgslb.com reveals contact information: iot-ota-cdn.io.mi.com.bsgslb.cn.
xmrhdl.v.bsgslb.cn.. This can be used for social engineering.
💡 Remove the RP record if the contact information is not intended to be public.
No subdomain takeover risks detected
All checked subdomains have valid, responsive targets.
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.
0 subdomain(s) discovered for mgslb.com
Subdomains were enumerated via Certificate Transparency logs, DNS wordlist brute-forcing, and DNS record analysis.
0 certificate(s) found in CT logs
Certificate Transparency logs contain 0 certificate(s) for mgslb.com and its subdomains. Each certificate reveals subdomain names.
NSEC3 authenticated denial of existence
The domain uses NSEC3 with -1 iteration(s) and salt '-'.
DNSSEC is enabled
DNSKEY and/or DS records are present, indicating DNSSEC is configured.
Reputation Findings
Missing Strict-Transport-Security on mgslb.com
The Strict-Transport-Security header is not set on https://mgslb.com.
💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.
Not listed on any DNS blacklists
Domain and MX IPs checked against 55 DNSBLs — no listings found.
security.txt present
Found security.txt at https://mgslb.com/.well-known/security.txt.
TLS certificate valid for 35 days
Certificate for mgslb.com expires on 2026-07-02.
Certificate issued by GeoTrust TLS RSA CA G1
The certificate for mgslb.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for mgslb.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for mgslb.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for mgslb.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on mgslb.com.
Domain valid for 322 days
Domain mgslb.com expires on 2027-04-16.
Domain transfer and delete locks enabled
Domain mgslb.com has clientTransferProhibited and clientDeleteProhibited locks.
No disposable email provider MX records
MX records for mgslb.com do not match known disposable email provider patterns.
Domain is 4790 days old
Domain mgslb.com was registered 2013-04-16.
No wildcard MX records
No wildcard MX records detected for mgslb.com.
TLD has good reputation
The .com TLD is not on known abuse watchlists.
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 contacts found for MX IPs
Abuse contact information retrieved via abusix.org DNS lookup.
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.mgslb.com
HTTPS request to https://webmail.mgslb.com failed or timed out.
WHOIS registration data
Registrar: eName Technology Co., Ltd. | Created: 2013-04-16 | Expires: 2027-04-16 | Updated: 2026-03-18
WHOIS privacy protection not detected
Domain mgslb.com does not appear to have WHOIS privacy protection. Registrant details may be publicly visible.
Bulletproof Hosting Detection — API key required
Checking IPs against known bulletproof hosting providers requires a threat intelligence API key.
Threat Intelligence Feeds — API key required
Checking domain against threat intelligence feeds requires API keys (e.g., VirusTotal, AbuseIPDB).
Typosquat detected: mgsl.com (has MX!), mtslb.com (has MX!), mgspb.com (has MX!), gslb.com, mslb.com
11 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 11. Domains with MX records can send and receive email, making them high-risk phishing vectors.
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 missing
→
DMARC Policy
DMARC policy missing
⚠️ 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: iot-ota-cdn.io.mi.com.bsgslb.cn
PTR record proves mail server legitimacy
MX: iot-ota-cdn.io.mi.com.bsgslb.cn
Mail server at xmrhdl.v.bsgslb.cn
→
PTR Record
No PTR record
⚠️ Mail server iot-ota-cdn.io.mi.com.bsgslb.cn (xmrhdl.v.bsgslb.cn) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Identity: xmrhdl.v.bsgslb.cn
PTR record proves mail server legitimacy
MX: xmrhdl.v.bsgslb.cn
Mail server at 60.9.3.146
→
PTR Record
No PTR record
⚠️ Mail server xmrhdl.v.bsgslb.cn (60.9.3.146) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Reputation: iot-ota-cdn.io.mi.com.bsgslb.cn
RBL check ensures server is not blacklisted
MX: iot-ota-cdn.io.mi.com.bsgslb.cn
Mail server at xmrhdl.v.bsgslb.cn
→
RBL Status
Not blacklisted
Mail Server Reputation: xmrhdl.v.bsgslb.cn
RBL check ensures server is not blacklisted
MX: xmrhdl.v.bsgslb.cn
Mail server at 60.9.3.146
→
RBL Status
Not blacklisted
Enforced Encryption Chain
MTA-STS enforces TLS encryption to prevent man-in-the-middle attacks
TLS Support
TLS not verified or unsupported
→
MTA-STS Policy
MTA-STS not configured
⚠️ TLS support could not be verified. MTA-STS requires TLS to enforce encrypted connections. Without TLS, MTA-STS cannot function.
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
TLS not verified or unsupported
→
TLS-RPT Reporting
TLS-RPT not configured
⚠️ TLS support could not be verified. TLS-RPT reports on TLS connection failures, but without TLS support, there's nothing to monitor. You need working TLS encryption before TLS-RPT can provide value.
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/mgslb.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan mgslb.com Again