Hostname
geechs.com
Last fetched
geechs.com resolves to 5 IPv4 addresses operated by NCJ-NET NHN Cloud Japan Corporation in JP. WHOIS lists iana:49 as the registrar.
Nutrition Label
Resolution chain
geechs.com resolves to 5 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 133.223.67.57 | 133.223.67.0/24 | AS151386 | NCJ-NET NHN Cloud Japan Corporation | JP |
| 18.244.179.108 | 18.244.176.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | GB |
| 18.244.179.112 | 18.244.176.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | GB |
| 18.244.179.31 | 18.244.176.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | GB |
| 18.244.179.4 | 18.244.176.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | GB |
WHOIS identity
- Registrar
- iana:49
- Organization
- geechs
- Contact emails
Subdomains
2 observed subdomains of geechs.com.
| Subdomain |
|---|
| recruit.geechs.com |
| www.geechs.com |
Web-graph footprint
Distinct hostnames that link to or from geechs.com in the public web crawl.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
12 SPF mechanisms authorising senders for geechs.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | _spf.google.com |
| SPF_INCLUDE | _spf.mxhero.com |
| SPF_INCLUDE | _spf.salesforce.com |
| SPF_INCLUDE | aspmx.pardot.com |
| SPF_INCLUDE | mktomail.com |
| SPF_IP | 210.149.144.41 |
| SPF_IP | 52.68.253.249 |
| SPF_IP | 54.199.135.68 |
| SPF_IP | 54.64.198.17 |
| SPF_IP | 54.65.124.47 |
| SPF_IP | 54.65.173.41 |
| SPF_IP | 54.65.62.85 |
Related pages
Pivot deeper into the graph from geechs.com.
- IP · 133.223.67.57
- ASN · AS151386NCJ-NET NHN Cloud Japan Corporation
- Registrar · iana:49
- Country · JP
- Email · sysinfo@geechs.com
- TLD · .com
- Browse hostnames · ge…
- Glossary · What is a hostname?
- Whisper Internet Directory — home
- Live MOAS conflicts feed
- Threat feed · Spamhaus DROP
- United States internet infrastructure
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "geechs.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
-[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.