Hostname
gingertproject.co.kr
Last fetched
gingertproject.co.kr resolves to 12 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in ES.
Nutrition Label
Resolution chain
gingertproject.co.kr resolves to 12 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 18.172.213.128 | 18.172.208.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | ES |
| 18.172.213.62 | 18.172.208.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | ES |
| 18.172.213.85 | 18.172.208.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | ES |
| 18.172.213.94 | 18.172.208.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | ES |
| 18.173.166.101 | 18.173.166.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.173.166.33 | 18.173.166.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.173.166.57 | 18.173.166.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.173.166.83 | 18.173.166.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.162.163.69 | 3.162.160.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.162.163.71 | 3.162.160.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.162.163.88 | 3.162.160.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.162.163.94 | 3.162.160.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
WHOIS identity
No WHOIS records are currently associated with gingertproject.co.kr in WhisperGraph.
Subdomains
1 observed subdomain of gingertproject.co.kr.
| Subdomain |
|---|
| www.gingertproject.co.kr |
Web-graph footprint
Distinct hostnames that link to or from gingertproject.co.kr in the public web crawl.
9 sites link to this hostname.
112 sites linked to from this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
1 SPF mechanism authorising senders for gingertproject.co.kr.
| Mechanism | Target |
|---|---|
| SPF_IP | 183.111.161.86 |
Related pages
Pivot deeper into the graph from gingertproject.co.kr.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "gingertproject.co.kr"})-[: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.