67.207.76.236
Reputation · trust score
A transparent 0–100 signal. Every entity starts at a neutral baseline of 65; threat-intel blocklists, exposure, reverse-DNS, routing and allocation each adjust it up or down. Higher is more trustworthy.
- Baseline (neutral) 65
- Datacenter — common VPN/proxy host −6
- Not on any threat blocklist +5
- Has a reverse-DNS (PTR) record +5
- Established allocation (10y) +3
- Trust score 72 / 100
Experimental · trust-vectors model v1.1.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- humbl.ai
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 1800 s
- Reverse DNS last checked
- 2026-07-19 13:49 UTC
- Forward DNS last checked
- 2026-07-19 13:49 UTC
Forward DNS records for humbl.ai
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 104.21.94.59 | — | 172800s |
| A | 172.67.220.78 | — | 172800s |
| AAAA | 2606:4700:3033::6815:5e3b | — | 172800s |
| AAAA | 2606:4700:3037::6815:5e3b | — | 172800s |
| AAAA | 2606:4700:3037::ac43:dc4e | — | 172800s |
| MX | alt1.aspmx.l.google.com | 5 | — |
| MX | alt2.aspmx.l.google.com | 5 | — |
| MX | aspmx.l.google.com | 1 | — |
| MX | aspmx2.googlemail.com | 10 | — |
| MX | aspmx3.googlemail.com | 10 | — |
| NS | aspen.ns.cloudflare.com | — | — |
| NS | greg.ns.cloudflare.com | — | — |
| TXT | google-site-verification=U27LZjpuui6-JteZoovp6NdefBAkIgmz5azow5KE4q8 | — | — |
| TXT | v=DMARC1; p=none; rua=mailto:alen@humbl.ai | — | — |
| TXT | v=spf1 ip4:46.101.179.84 ip6:2a03:b0c0:3:d0::1736:1001 ip4:67.207.76.236 include:_spf.google.com ~all | — | — |
| TXT | v=spf1 ip4:46.101.179.84 ip6:2a03:b0c0:3:d0::1736:1001 ip4:67.207.76.236 include:humble.ai include:www.humble.ai +all | — | — |
| CAA | iodef mailto:info@humbl.ai | 0 | — |
| CAA | issue amazon.com | 0 | — |
| CAA | issue comodoca.com | 0 | — |
| CAA | issue digicert.com; cansignhttpexchanges=yes | 0 | — |
| CAA | issue letsencrypt.org | 0 | — |
| CAA | issue pki.goog; cansignhttpexchanges=yes | 0 | — |
| CAA | issue sectigo.com | 0 | — |
| CAA | issue ssl.com | 0 | — |
| CAA | issuewild amazon.com | 0 | — |
| CAA | issuewild comodoca.com | 0 | — |
| CAA | issuewild digicert.com; cansignhttpexchanges=yes | 0 | — |
| CAA | issuewild letsencrypt.org | 0 | — |
| CAA | issuewild pki.goog; cansignhttpexchanges=yes | 0 | — |
| CAA | issuewild sectigo.com | 0 | — |
| CAA | issuewild ssl.com | 0 | — |
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Network Allocation for 67.207.76.236
- CIDR range
- 67.207.72.0/21
- IP range (int)
- 1,137,657,856 — 1,137,659,903
- Prefix length
- /21
- Organization
- DigitalOcean, LLC
- ASN
- AS14061
- ASN name
- DigitalOcean, LLC
- Location
- Frankfurt am Main, Hesse, Germany
- Coordinates
- 50.116900, 8.683700
- Accuracy radius
- 20 km
- Postal code
- 60313
- Regional Internet Registry
- ARIN
- Allocated
- 2016-04-12
- Data source(s)
- maxmind_city, maxmind_asn, maxmind_country, ipinfo_lite
- Last updated
- 2026-07-11 09:20:50
BGP Routing
Live BGP anomalies →Origin AS announcing the most-specific prefix that covers this IP, observed across our RIPE RIS collectors.
RIR Ownership History
Atom feed ⇲Allocation changes captured weekly from regional internet registry (RIR) delegation files for ranges that have contained this IP.
| Date | Event | From | To |
|---|---|---|---|
| 2026-05-10 | New Allocation | — | US |
See the full history for 67.207.0.0/16.
Frequently Asked Questions
Who owns 67.207.76.236?
67.207.76.236 is allocated to DigitalOcean, LLC (AS14061), registered in Frankfurt am Main, Germany.
Where is 67.207.76.236 located?
The geolocation for 67.207.76.236 maps to Frankfurt am Main, Germany based on MaxMind GeoLite2 data. Accuracy depends on the provider and may represent the ISP's regional hub rather than the exact endpoint.
What network is 67.207.76.236 on?
67.207.76.236 belongs to the 67.207.72.0/21 network block announced by AS14061. This range contains 2,048 addresses.
Does 67.207.76.236 have a reverse DNS record?
Reverse DNS (PTR) records are resolved live when you visit this page. If a PTR record exists, it appears in the Reverse DNS field above. PTR records map IP addresses back to hostnames and are commonly used for email authentication and network diagnostics.
Neighbors
Other addresses in the same /24.
