Hostname
gammis.com
Last fetched
gammis.com resolves to 173.227.153.120, announced in 173.227.153.64/26 by LVLT-3549 - Level 3 Parent, LLC in US. gammis.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
- 173.227.153.120
173.227.153.64/26 · LVLT-3549 - Level 3 Parent, LLC · New York, US
IPv6 resolution
No AAAA record for gammis.com is recorded in WhisperGraph.
Attribution
level parent
ORIGIN_AS
WHOIS identity
- Registrar
- iana:1387
- Registrant organisation
- c/o whoisproxy.com
- Contact emails
- gammis.com@domainsbyproxy.com, 194fea4bd8@gammis.com.whoistrustee.com, 04d86959453bbc9024d1e30dbc4b825b8b235521aff96ec3541c5279ea70863e@gammis.com.whoisproxy.org, 6605ebc335c82cad15d33687b7d14d7f554c457cb3958a9ee7d89a1a4ac3c6c3@gammis.com.whoisproxy.org, 77980c39a24032b87195347a71bb696818731e54ee0167c2de6ba3beb278816d@gammis.com.whoisproxy.org, b826ccaabb86f109c0a5bff005c73e4413b3bc7666c2f18f25928b31387a1205@gammis.com.whoisproxy.org, c8a03c498e2b11b2b95a373ad99fa15cea2e7fb529d0371b29f4cf68560a774b@gammis.com.whoisproxy.org, f0d7d03da97d49c93578cb3b845b58bafc30016b753d71ef90134e31a4c1f9cd@gammis.com.whoisproxy.org, ff4e6e6a03dfa019f88305c3af8b4a6b2beee66ae6696305b4092bca7227c1c3@gammis.com.whoisproxy.org
Subdomains
| Subdomain |
|---|
| documentum.gammis.com |
| home.gammis.com |
| mail.gammis.com |
| mapira.gammis.com |
| mapirb.gammis.com |
| public.gammis.com |
| sme.gammis.com |
| sso.gammis.com |
| uservpn.gammis.com |
Showing 9 of 9 subdomains (9 per page).
Mail and authentication
Nameservers
- ns1.dnsimple.com
- ns3.dnsimple.com
- ns1.dnsimple-edge.com
- ns3.dnsimple-edge.io
- ns2.dnsimple-edge.net
- ns4.dnsimple-edge.org
MX records
- mail.gammis.com
SPF policy
- a: gammis.com
- mx: gammis.com
- include: spf.mtasv.net
- ip: 173.227.153.107
Threat-feed evidence
History
Related pages
Pivot from gammis.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: "gammis.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.