Hostname
bmssn.com
Last fetched
bmssn.com resolves to 195.110.35.214, announced in 195.110.35.0/24 by LWS - Groupe LWS SARL in FR. bmssn.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 195.110.35.214
195.110.35.0/24 · LWS - Groupe LWS SARL · Paris, FR
IPv6 resolution
No AAAA record for bmssn.com is recorded in WhisperGraph.
Attribution
groupe lws sarl
ORIGIN_AS
WHOIS identity
- Registrar
- iana:1630
- Registrant organisation
- alternetis
- Contact emails
- reg_15489863@whoisprotection.cc, 13904514090@qq.com, 3aa3bf7e510ee0ca47c3ae34b893f14e@whois-anonymous.com, 52158d6f6f2a8228033b2dd5924de7f7@whois-anonymous.com, 63809ef069a504dc8fbd66fd1f408229@whois-anonymous.com, 674bfc5f6b72706fb769f5e93667bd23@whois-anonymous.com, a79eb1040b0ea4b55f7f436d6a3d0444@whois-anonymous.com, admin@newvcorp.com, domain@jinmail.com, f2217062e9a397a1dca429e7d70bc6ca@whois-anonymous.com
Subdomains
| Subdomain |
|---|
| autodiscover.bmssn.com |
| cpanel.bmssn.com |
| cpcalendars.bmssn.com |
| cpcontacts.bmssn.com |
| ipv6.bmssn.com |
| mail.bmssn.com |
| webdisk.bmssn.com |
| webmail.bmssn.com |
| www.bmssn.com |
Showing 9 of 9 subdomains (9 per page).
Mail and authentication
Nameservers
- ns1.dnshostservices.com
- ns2.dnshostservices.com
- ns3.dnshostservices.com
- ns4.dnshostservices.com
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
MX records
- mail.bmssn.com
SPF policy
- a: bmssn.com
- mx: bmssn.com
- include: premiumsmtp.dnshostservices.com
- ip: 195.110.35.214
- ip: 91.234.194.106
- ip: 91.234.194.11
- ip: 91.234.194.232
Threat-feed evidence
History
Related pages
Pivot from bmssn.com into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "bmssn.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.