Hostname
s1gateway.com
Last fetched
s1gateway.com resolves to 50.31.176.53, announced in 50.31.176.0/24 by SERVERCENTRAL - DEFT.COM in US. s1gateway.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
- 50.31.176.53
50.31.176.0/24 · SERVERCENTRAL - DEFT.COM · Chicago, US
IPv6 resolution
No AAAA record for s1gateway.com is recorded in WhisperGraph.
Attribution
servercentral deft com
ORIGIN_AS
WHOIS identity
- Registrar
- iana:468
- Registrant organisation
- - oscar
- Contact emails
- s1gateway.com@secretregistration.com, oscartorres@gmail.com, noc@slot1.io, 15289147-ca2e-4d38-8a78-654190f761fe@identity-protect.org, dc7e31e0-7945-473b-9cad-851cdae1e152@identity-protect.org, owner-10158954@s1gateway.com.whoisprivacyservice.org, owner-10428903@s1gateway.com.whoisprivacyservice.org, owner-11117172@s1gateway.com.whoisprivacyservice.org, owner-11749956@s1gateway.com.whoisprivacyservice.org, owner-11836770@s1gateway.com.whoisprivacyservice.org, owner-4686019@s1gateway.com.whoisprivacyservice.org, owner-5600362@s1gateway.com.whoisprivacyservice.org, owner-5693248@s1gateway.com.whoisprivacyservice.org, owner@s1gateway.com.whoisprivacyservice.org
Subdomains
Showing 12 of 65. View all subdomains →
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
Mail and authentication
Nameservers
- ns-215.awsdns-26.com
- ns-774.awsdns-32.net
- ns-1516.awsdns-61.org
- ns-1920.awsdns-48.co.uk
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- aspmx2.googlemail.com
- aspmx3.googlemail.com
SPF policy
- include: _spf.google.com
- include: 2991420.spf04.hubspotemail.net
- ip: 34.217.180.231
- ip: 54.68.56.155
Threat-feed evidence
History
Related pages
Pivot from s1gateway.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: "s1gateway.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.