mmsa.com was registered with whois.verisign-grs.com on 16 Feb 1995. We couldn't read an SSL certificate for it when we last analysed it.
What security vendors and the WOT community say about this domain.
What loads and tracks visitors when the homepage opens.
Running a full browser scan of the homepage… This takes about a minute.
We couldn't read an SSL certificate on port 443 when we last analysed mmsa.com. Refresh the analysis to check again.
320 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| mms4.shop | Look-alike characters | 13 Oct 2026 | Checking… | Report → |
| mms4.cc | Look-alike characters | 5 Oct 2026 | Checking… | Report → |
| msma.my | Typo | 8 Nov 2026 | Checking… | Report → |
| msma.space | Typo | 5 Nov 2026 | Checking… | Report → |
| mmas.online | Typo | 22 Sept 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is mmsa.com’s name taken on other extensions?
| Host | Mail server | TTL |
|---|---|---|
| mmsa.com | 5 us-smtp-inbound-1.mimecast.com | 3600 |
| mmsa.com | 5 us-smtp-inbound-2.mimecast.com | 3600 |
| Host | Name server | TTL |
|---|---|---|
| mmsa.com | ns1-05.azure-dns.com | 21600 |
| mmsa.com | ns2-05.azure-dns.net | 21600 |
| mmsa.com | ns3-05.azure-dns.org | 21600 |
| mmsa.com | ns4-05.azure-dns.info | 21600 |
| Host | Text | TTL |
|---|---|---|
| mmsa.com | "70jmgy88pyvqtcfj4s0w6dx3kcghp0cg" | 3600 |
| mmsa.com | "MS=ms22537162" | 3600 |
| mmsa.com | "v=spf1 include:spf.protection.outlook.com include:us._netblocks.mimecast.com mx ip4:72.18.22.16 ip4:72.18.22.19 ip4:72.18.23.20 ip4:72.18.23.21 ip4:72.18.22.23 ip4:72.18.22.24 ~all" | 3600 |
| Host | Start of authority | TTL |
|---|---|---|
| mmsa.com | ns1-05.azure-dns.com sysop.mmsa.com 20001166 3600 600 432000 1800 | 3600 |
No reviews yet. Used mmsa.com? Be the first to say how it went.
Reviews are from CubDomain users and are separate from the security verdicts above.
Common questions, answered from this report's data.
mmsa.com has no community safety rating yet. We couldn't read an SSL certificate on it when we last analysed it. See Security →
mmsa.com is registered through whois.verisign-grs.com. See WHOIS →
The registration expired on 17 Feb 2026. See Overview →
mmsa.com was registered on 16 Feb 1995, making it 31 years old. See Overview →
Raw registry data for mmsa.com. May be redacted by privacy services.
{"objectClassName":"domain","handle":"99217_DOMAIN_COM-VRSN","ldhName":"MMSA.COM","links":[{"value":"https:\/\/rdap.verisign.com\/com\/v1\/domain\/MMSA.COM","rel":"self","href":"https:\/\/rdap.verisign.com\/com\/v1\/domain\/MMSA.COM","type":"application\/rdap+json"},{"value":"https:\/\/rdap.networksolutions.com\/rdap\/domain\/MMSA.COM","rel":"related","href":"https:\/\/rdap.networksolutions.com\/rdap\/domain\/MMSA.COM","type":"application\/rdap+json"}],"status":["client transfer prohibited"],"entities":[{"objectClassName":"entity","handle":"2","roles":["registrar"],"publicIds":[{"type":"IANA Registrar ID","identifier":"2"}],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text","Network Solutions, LLC"]]],"entities":[{"objectClassName":"entity","roles":["abuse"],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text",""],["tel",{"type":"voice"},"uri","tel:+1.8777228662"],["email",{},"text","[email protected]"]]]}]}],"events":[{"eventAction":"registration","eventDate":"1995-02-16T05:00:00Z"},{"eventAction":"expiration","eventDate":"2026-02-17T05:00:00Z"},{"eventAction":"last changed","eventDate":"2021-02-19T15:47:07Z"},{"eventAction":"last update of RDAP database","eventDate":"2023-10-26T03:38:57Z"}],"secureDNS":{"delegationSigned":false},"nameservers":[{"objectClassName":"nameserver","ldhName":"NS1-05.AZURE-DNS.COM"},{"objectClassName":"nameserver","ldhName":"NS2-05.AZURE-DNS.NET"},{"objectClassName":"nameserver","ldhName":"NS3-05.AZURE-DNS.ORG"},{"objectClassName":"nameserver","ldhName":"NS4-05.AZURE-DNS.INFO"}],"rdapConformance":["rdap_level_0","icann_rdap_technical_implementation_guide_0","icann_rdap_response_profile_0"],"notices":[{"title":"Terms of Use","description":["Service subject to Terms of Use."],"links":[{"href":"https:\/\/www.verisign.com\/domain-names\/registration-data-access-protocol\/terms-service\/index.xhtml","type":"text\/html"}]},{"title":"Status Codes","description":["For more information on domain status codes, please visit https:\/\/icann.org\/epp"],"links":[{"href":"https:\/\/icann.org\/epp","type":"text\/html"}]},{"title":"RDDS Inaccuracy Complaint Form","description":["URL of the ICANN RDDS Inaccuracy Complaint Form: https:\/\/icann.org\/wicf"],"links":[{"href":"https:\/\/icann.org\/wicf","type":"text\/html"}]}]}Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with mmsa.com. Data is collected independently from public sources and some figures are estimates, provided for information only.
Spam and malware blocklists for the site's IP and mail servers.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.
When the site first appeared, and what has changed since.
We record what changes from the next time this report is refreshed.