Homeβ€Ί Infrastructureβ€Ί inputs14.phl.splunkcloud.com
Mostly Safe

Yes β€” inputs14.phl.splunkcloud.com looks mostly safe

78/ 100 trust score
Industry: Infrastructure Checked Jul 17, 2026 Infrastructure average: 48 25 signals

In plain English

This appears to be a legitimate infrastructure endpoint for Splunk Cloud, likely used for data ingestion. It has valid security, legal pages, and clear business disclosure. The lack of contact info and web archive history are normal for this type of service, not a sign of trouble.

Cross-referenced 25 live signals from Google Safe Browsing, VirusTotal, WHOIS and more on Jul 17, 2026. How we score β†’

Where the score comes from

We look at six areas. Here's how inputs14.phl.splunkcloud.com did in each.
75
Security

The site uses a valid SSL certificate from a well-known issuer and supports modern TLS, which is standard for any infrastructure endpoint. The lack of browser security headers is not a major concern for an API endpoint that isn't intended for direct browser interaction.

85
Identity

This is a subdomain of splunkcloud.com, a well-known company in the data analytics space. The presence of an about page and business disclosure confirms the operator's identity, which is strong for an infrastructure service.

80
Reputation

No blacklist flags or threats detected, and the site is not associated with any known reputation issues. The absence of a web archive history is typical for a newer or rarely crawled endpoint, not a red flag.

75
Transparency

An about page and legal disclosure are provided, but contact info is not on the homepage. For a data ingestion endpoint, this is expected β€” users interact with it programmatically, not through a customer service interface.

85
Compliance

Privacy policy and terms of service are present, along with a business disclosure that satisfies EU legal requirements. This is appropriate for a service that may handle customer data.

80
Infrastructure

The domain resolves reliably to multiple AWS IPs and uses a standard load balancer. The lack of DNSSEC and email records is normal for an API endpoint that doesn't serve email or require domain signing.

What we checked

The 25 signals behind this report.
Security & Transport
Certificate Issuer
DigiCert Inc
Google Web Risk
Clean
SSL Certificate
Valid
Security Headers
0 of 6
Server
awselb/2.0
TLS Version
TLS 1.3
Identity & WHOIS
About Page
Found
Branding
Missing
Business Disclosure
Found
Contact Info
Not found
Legal Pages
Privacy & Terms found
Infrastructure & DNS
DNS Blacklists
Clean
DNS Resolution
3 IP(s)
DNSSEC
Not enabled
Email (MX Records)
None
Hosting Network (ASN)
AS14618 AMAZON-AES
Page Load Time
339ms
Reputation & Reach
Sitemap
Misconfigured
Social Media Presence
None found
Structured Data
None found
Tranco Rank
Not ranked
Trustpilot
No Trustpilot profile
Web Archive History
No archive found
Website Status
Online
robots.txt
Present

Run this site? Show your score.

Add a trust badge so visitors can see your live score for themselves.

Get your badge β†’
verified.fyi
inputs14.phl.splunkcloud.com
78
N Partner pick
This site checks out. Stay covered everywhere: NordVPN's Threat Protection blocks known scam sites before they load.
Try NordVPN β†’

inputs14.phl.splunkcloud.com is not a typical consumer website β€” it's a subdomain used by Splunk's cloud service for collecting log data from customers. For anyone wondering 'is inputs14.phl.splunkcloud.com a scam', the evidence points to no. The site has a valid SSL certificate, legal pages like a privacy policy and terms of service, and a business disclosure that matches what you'd expect from a legitimate infrastructure provider. There's no contact form on the homepage, but that's standard for an API endpoint: you configure it through Splunk's own interface, not by visiting this URL directly. The domain is part of the well-known splunkcloud.com, which belongs to Splunk Inc., a major tech company. The lack of a web archive history or social media presence isn't surprising for a backend service. If you're a Splunk customer, you'd use this endpoint with credentials β€” treat it as you would any secure API. There's no reason to be suspicious based on the data available.

More Infrastructure sites

How similar sites score. See all β†’