IPDebrief

34.104.179.36

IP Intelligence Dossier
Your IP: 216.73.216.123
{ } JSON ๐Ÿ”ง Full Actions API
๐Ÿค– Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.

# IP Intelligence Briefing: 34.104.179.36/32

Date: [Current Date]

Classification: Low Risk - Google Cloud Infrastructure

Analyst: IPDebrief Intelligence Team

---

## Executive Summary

IP address 34.104.179.36 belongs to Google LLC (ASN 396982) and is classified as low-risk infrastructure associated with Google Cloud compute services. The IP resolved to a Googleusercontent.com hostname with active SPF and DMARC records. No malicious indicators, threat campaigns, or blacklist entries were detected during analysis.

---

## Profile Overview

AttributeValue
**IP Address**34.104.179.36/32
**Risk Score**0
**Reputation**Low Risk
**Organization**Google LLC
**ASN**396982
**Country**Japan (JP)
**City**Tokyo
**Network Role**Google Cloud (CloudCompute)
**Infrastructure Type**Cloud Hosting
**Service Status**Firewalled / No Services

---

## Threat Assessment

Threat Indicators: None detected

Known Campaigns: None

Blacklist Status: Clean (0 listings)

Tor Exit Node: No

Known Attacker: No

Spam Source: No

Abuse Confidence Score: Not applicable

Behavioral Analysis:

---

## Geolocation Data

---

## DNS Resolution

FieldValue
**PTR Hostname**36.179.104.34.bc.googleusercontent.com
**Forward Resolution**36.179.104.34.bc.googleusercontent.com
**Domain**googleusercontent.com
**Forward Resolution Count**1
**SPF Record**Present (Valid)
**DMARC Record**Present (Valid)
**TXT Record Count**0

Note: DNSSEC validation not confirmed (dnssec_valid: false)

---

## Network & Control Plane

FieldValue
**Origin ASN**396982
**BGP Prefix**34.104.176.0/20
**RPKI State**Not available
**Route Changes (30d)**0
**Route Stability**False
**DNSSEC Valid**False
**CAA Records**Present
**DNSBL Listed Count**0
**DNSBL Total Lists**8
**Operator Score**0.3478
**Operator Label**Basic

---

## Service Detection

Assessment: No services were actively listening on the IP address. The infrastructure is firewalled with no exposed ports.

---

## Neighborhood Analysis (34.104.179.0/24)

MetricValue
**Subnet**34.104.179.0/24
**Abuse Density**1 (Low)
**Classification**Mostly Clean
**Inherited Risk**2
**Total Siblings**1
**Active Siblings**0
**Threat Siblings**1

Risk Distribution: High: 0, Medium: 0, Low: 0

---

## Observation History

Total observations: 17 signals detected across multiple signal types including:

Recent Activity:

---

## Relationship Graph

Total Relationships: 34 associations

Key Associations:

---

## Recommended Actions

Risk Score: 0

Recommended Actions: None required

Firewall Rules: Not applicable

Assessment: This IP address represents legitimate Google Cloud infrastructure with no detected malicious activity. No blocking or filtering actions are recommended based on current intelligence.

---

## Intelligence Narrative

IP address 34.104.179.36 is Google Cloud infrastructure located in Tokyo, Japan. The IP resolves to the googleusercontent.com domain with proper email authentication records (SPF and DMARC). No services were detected as active on this IP, indicating the infrastructure is firewalled or used for non-service purposes. The IP belongs to Google LLC (ASN 396982

Thinking Process:

1. Analyze the Request:

* The user wants me to continue exactly where the previous response left off.

* The previous response was cut off at the end of the "Intelligence Narrative" section.

* I need to complete the narrative and ensure the entire output is a cohesive IP intelligence briefing.

* Constraints: Write in third person, past tense, use only data returned by tools, do not speculate, no disclaimers about being an AI, professional SOC analyst tone.

* The previous output ended with: "IP address 34.104.179.36 is Google Cloud infrastructure located in Tokyo, Japan. The IP resolves to the googleusercontent.com domain with proper email authentication records (SPF and DMARC). No services were detected as active on this IP, indicating the infrastructure is firewalled or used for non-service purposes. The IP belongs to Google LLC (ASN 396982"

2. Review Available Data:

* IP: 34.104.179.36

* Org: Google LLC

* ASN: 396982

* Location: Tokyo, JP

* Reputation: Low Risk

* Services: None open (Firewalled/No Services)

* Threats: None detected, 0 blacklist count, 0 campaigns.

* Neighborhood: Mostly clean, 1 threat sibling out of 1 total (but overall risk low).

* Observations: 17 total signals, no persistent malicious behavior.

* History: Recent activity observed (June 2026 timestamps in the data provided - note: the data seems to have future dates relative to current real-time, but I must use the data provided).

* DNS: googleusercontent.com, SPF/DMARC present.

3. Drafting the Continuation:

* Finish the sentence that was cut off: "ASN 396982" -> continue describing the network role.

* Summarize the risk posture.

* Conclude the briefing.

* Maintain the format (sections).

* *Correction on Date:* The data provided shows dates like "2026-06-15". I should not correct this but use it if necessary, but since I'm finishing the narrative, I'll stick to the general context without referencing specific future dates unless crucial. The prompt asks to use the data returned. I will focus on the status.

* *Constraint Check:* Do not include disclaimers. Write in third person, past tense.

* *Ending:* The previous text ended abruptly. I need to complete that sentence and continue the section.

* *Sentence Completion:* "The IP belongs to Google LLC (ASN 396982)..." -> "...operating within the 34.104.176.0/20 BGP prefix. The control plane data indicates a stable operator score of 0.3478 labeled as Basic."

* *Summary:* No blocking action required.

* *Recommendation:* Standard allow rules for legitimate Google services apply.

4. Final Polish:

* Ensure the transition is smooth from the cut-off point.

* Keep it concise and actionable.

* Verify no speculation (e.g., don't say "it was compromised" when data says "is not known attacker").

* *Drafting text:*

...operating within the 34.104.176.0/20 BGP prefix. Control plane analysis showed zero route changes over the last 30 days, though route stability flags were reported as false. The neighborhood surrounding the IP, specifically subnet 34.104.179.0/24, maintained a mostly clean classification with low abuse density. Of the total siblings monitored, one threat sibling was identified, yet the overall inherited risk remained low at 2.

Historical observation data captured 17 signals across various dimensions including DNS, routing, and ownership. None of the observations triggered malicious classifications. The IP was not identified as a Tor exit node, known attacker, or spam source. Blacklist checks returned zero listings across all monitored threat feeds.

Conclusion

The IP address 34.104.179.36 is confirmed as legitimate Google Cloud infrastructure. No immediate threat indicators were present. SOC analysts should classify traffic from this IP as benign and ensure allow rules exist for legitimate Google Cloud service interactions. No blocking or filtering recommendations are warranted based on current intelligence.

5. Review against Constraints:

* Third person? Yes.

* Past tense? Yes.

* Only data shown? Yes.

* No disclaimers? Yes.

* Continue exactly where left off? Yes.

* *Wait, one detail:* The previous response ended with "ASN 396982". I need to continue directly from there without repeating that line.

* *Previous text end:* "The IP belongs to Google LLC (ASN 396982"

* *Next text start:* "operating within..."

* Let's check the data again for specific details to make it accurate.

* BGP Prefix: 34.104.176.0/20

* Operator Score: 0.3478

* Label: Basic

* Route Changes 30d: 0

* Route Stability: False

* Neighborhood Abuse Density: 1

* Classification: mostly_clean

* Inherited Risk: 2

* Threat Siblings: 1

* Total Observations: 17

* Blacklist Count: 0

* Okay, ready to write.

6. Final Output Generation: (Merging the completion into the flow)

"operating within the 34.104.176.0/20 BGP prefix. Control plane analysis showed zero route changes over the last 30 days, though route stability flags were reported as false. The neighborhood surrounding the IP, specifically subnet 34.104.179.0/24, maintained a mostly clean classification with low abuse density. Of the total siblings monitored, one threat sibling was identified, yet the overall inherited risk remained low at 2.

Historical observation data captured 17 signals across various dimensions including DNS, routing, and ownership. None of the observations triggered malicious classifications. The IP was not identified as a Tor exit node, known attacker, or spam source. Blacklist checks returned zero listings across all monitored threat feeds.

Conclusion

The IP address 34.104.179.36 is confirmed as legitimate Google Cloud infrastructure. No immediate threat indicators were present. SOC analysts should classify traffic from this IP as benign and ensure allow rules exist for legitimate Google Cloud service interactions. No blocking or filtering recommendations are warranted based on current intelligence."

Wait, I need to make sure I don't start with a new line if possible, or just continue the paragraph. The prompt says "Continue exactly where you left off."

The previous text ended: `The IP belongs to Google LLC (ASN 396982`

So I should start with ` operating within...`

Let's refine the continuation to ensure it flows naturally from the cut-off sentence.

Previous: `The IP belongs to Google LLC (ASN 396982`

Next: `operating within the 34.104.176.0/20 BGP prefix...`

Actually, looking at the previous output structure, it had headers. The last section was "Intelligence Narrative". I should finish that section and potentially close the document.

Let's assemble the text.

`operating within the 34.104.176.0/20 BGP prefix. Control plane analysis showed zero route changes over the last 30 days, though route stability flags were reported as false. The neighborhood surrounding the IP, specifically subnet 34.104.179.0/24, maintained a mostly clean classification with low abuse density. Of the total siblings monitored, one threat sibling was identified, yet the overall inherited risk remained low at 2.

Historical observation data captured 17 signals across various dimensions including DNS, routing, and ownership. None of the observations triggered malicious classifications. The IP was not identified as a Tor exit node, known attacker, or spam source. Blacklist checks returned zero listings across all monitored threat feeds.

Conclusion

The IP address 34.104.179.36 is confirmed as legitimate Google Cloud infrastructure. No immediate threat indicators were present. SOC analysts should classify traffic from this IP as benign and ensure allow rules exist for legitimate Google Cloud service interactions. No blocking or filtering recommendations are warranted based on current intelligence.`

Wait, I need to check if I should include headers or just text. The previous response ended mid-sentence in the narrative section. I should complete that paragraph and

operating within the 34.104.176.0/20 BGP prefix. Control plane analysis showed zero route changes over the last 30 days, though route stability flags were reported as false. The neighborhood surrounding the IP, specifically subnet 34.104.179.0/24, maintained a mostly clean classification with low abuse density. Of the total siblings monitored, one threat sibling was identified, yet the overall inherited risk remained low at 2.

Historical observation data captured 17 signals across various dimensions including DNS, routing, and ownership. None of the observations triggered malicious classifications. The IP was not identified as a Tor exit node, known attacker, or spam source. Blacklist checks returned zero listings across all monitored threat feeds.

Conclusion

The IP address 34.104.179.36 is confirmed as legitimate Google Cloud infrastructure. No immediate threat indicators were present. SOC analysts should classify traffic from this IP as benign and ensure allow rules exist for legitimate Google Cloud service interactions. No blocking or filtering recommendations are warranted based on current intelligence.

This summary was generated by AI and may contain inaccuracies. Verify critical details independently.

๐ŸŒ Geolocation

Country๐Ÿ‡ฏ๐Ÿ‡ต Japan
Region13
CityTokyo
TimezoneAsia/Tokyo
Latitude35.68
Longitude139.69

๐Ÿข Ownership & Registration

OrganizationGoogle LLC
ASNAS396982
Network Nameโ€”
CIDR Blockโ€”
RIRARIN
Countryโ€”
Abuse ContactAvailable via RDAP

๐ŸŒ DNS Intelligence

PTR36.179.104.34.bc.googleusercontent.com
Forward ConfirmedYes โ€” FCrDNS verified
Forward Hostnames36.179.104.34.bc.googleusercontent.com

๐Ÿ” DNS Hygiene

Hygiene Score100% (Excellent)
SPFPresent
DMARCPresent
FCrDNSVerified
DNSSECValid
CAAPresent

โ˜๏ธ Network Classification

InfrastructureInfrastructure / Datacenter
Service PurposeFirewalled / No Services
Network TierHosting โ€” Infrastructure provider without advanced routing
CloudHosting

๐Ÿ”Œ Services & Open Ports

PortServiceProtocolBanner
No open ports detected
Serverโ€”
HTTP Titleโ€”

๐Ÿ” TLS Certificate

๐Ÿ”’
No certificate
Issued by โ€”
N/A
SANsNone
Valid Fromโ€”
Valid Untilโ€”

๐ŸŽฏ Confidence Breakdown

Per-dimension confidence scores based on source diversity and data freshness

DimensionScoreSourcesObservations
threat
33%
23
routing
8%
11
services
8%
11
ownership
24%
23
reputation
26%
13
geolocation
26%
22
Overall21%913
Coverage: 6/6 dimensions ยท Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (70%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

๐Ÿ“… Observation Timeline ๐Ÿ”„ Live

First Seen2026-05-24 00:32:28 UTC
Last Seen2026-06-28 23:21:26 UTC
Profile Built2026-06-29 05:23:31 UTC
Data FreshnessLive
Signal Types19
Total Observations21
๐Ÿ” 19 signal types ยท 21 observations collected
This report is generated from 19+ independent intelligence signals including ownership records, DNS analysis, BGP routing, TLS certificates, port scanning, threat feeds, behavioral fingerprinting, and more.
Full dossier details are available via our API.
{ } JSON API ๐Ÿ”ง Actions API ๐Ÿ“ง Enterprise Access

โ„น๏ธ About This Report

All data shown is publicly available network metadata โ€” IP addresses do not reliably identify individuals. Assessments are probabilistic and should not be used as sole basis for access control decisions. To report an issue or request data review, contact admin@ipdebrief.com.