Hostname
buk.co
Last fetched
buk.co resolves to 12 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in US.
Nutrition Label
Resolution chain
buk.co 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.138.85.111 | 108.138.80.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 108.138.85.45 | 108.138.80.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 108.138.85.52 | 108.138.80.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 108.138.85.54 | 108.138.80.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.245.60.103 | 18.245.60.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 18.245.60.12 | 18.245.60.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 18.245.60.126 | 18.245.60.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 18.245.60.60 | 18.245.60.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 3.168.122.100 | 3.168.122.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.168.122.107 | 3.168.122.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.168.122.11 | 3.168.122.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.168.122.43 | 3.168.122.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
WHOIS identity
WHOIS data is temporarily unavailable. Refresh in a moment to retry.
Subdomains
Subdomain count is temporarily unavailable. Refresh in a moment to retry.
Web-graph footprint
Distinct hostnames that link to or from buk.co in the public web crawl.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
6 SPF mechanisms authorising senders for buk.co.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | 3790458.spf07.hubspotemail.net |
| SPF_INCLUDE | _spf.google.com |
| SPF_INCLUDE | amazonses.com |
| SPF_INCLUDE | mail.zendesk.com |
| SPF_INCLUDE | sendgrid.net |
| SPF_INCLUDE | spf.mandrillapp.com |
Related pages
Pivot deeper into the graph from buk.co.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "buk.co"})-[: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.