Hostname
massgate.net
Last fetched
massgate.net resolves to 176.34.163.104, announced in 176.34.160.0/19 by AMAZON-02 - Amazon.com, Inc. in IE. massgate.net 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
- 176.34.163.104
176.34.160.0/19 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 52.209.25.174
52.208.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 52.214.206.240
52.208.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 52.30.112.245
52.30.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 54.216.201.248
54.216.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 63.33.156.68
63.32.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
IPv6 resolution
No AAAA record for massgate.net is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:81
- Registrant organisation
- daniel ljungberg
- Contact emails
- 29c1a5bc1d37ceeca803d95b6e8c64db-913767@contact.gandi.net, 36ebc20832525517d5bd7afe81c2deb5-913767@contact.gandi.net
Subdomains
Showing 4 of 4 subdomains (4 per page).
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Sample outbound links
Mail and authentication
Nameservers
- ns-16-a.gandi.net
- ns-214-c.gandi.net
- ns-99-b.gandi.net
- ns1.gandi.net
- 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
- ubisoftaad.mail.protection.outlook.com
SPF policy
- redirect: _spf.ubisoft.com
Threat-feed evidence
History
Related pages
Pivot from massgate.net 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: "massgate.net"})-[: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.