Hostname
code.berlin
Last fetched
code.berlin resolves to 12 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in SG. WHOIS lists iana:15 as the registrar.
Nutrition Label
Resolution chain
code.berlin 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 |
|---|---|---|---|---|
| 108.158.251.26 | 108.158.251.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | SG |
| 108.158.251.58 | 108.158.251.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | SG |
| 108.158.251.60 | 108.158.251.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | SG |
| 108.158.251.88 | 108.158.251.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | SG |
| 18.164.96.14 | 18.164.96.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.164.96.39 | 18.164.96.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.164.96.87 | 18.164.96.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.164.96.92 | 18.164.96.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.245.46.109 | 18.245.44.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 18.245.46.64 | 18.245.44.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 18.245.46.65 | 18.245.44.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 18.245.46.72 | 18.245.44.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
WHOIS identity
- Registrar
- iana:15
- Organization
- code education
- Contact emails
Subdomains
29 observed subdomains of code.berlin.
Showing 25 of 29. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from code.berlin in the public web crawl.
294 sites link to this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
3 SPF mechanisms authorising senders for code.berlin.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | 2730872.spf04.hubspotemail.net |
| SPF_INCLUDE | _spf.atlassian.net |
| SPF_INCLUDE | _spf.google.com |
Related pages
Pivot deeper into the graph from code.berlin.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "code.berlin"})-[: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.