appdynamics.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
90
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
90
appdynamics.com was registered on 12 Jul 2001 via MarkMonitor Inc. and the registry expiry is 12 Jul 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/appdynamics.com.
appdynamics.com publishes 4 nameservers. DNSSEC is not signed.
appdynamics.com has 1 IPv4 address (204.107.141.160). The geolocation database places 204.107.141.160 in San Francisco (South Beach), United States.
The TLS certificate from DigiCert Global G2 TLS RSA SHA256 2020 CA1 is valid and has 19 days left (TLS 1.2). The homepage answered HTTP 200.
Tech detection named Adobe Experience Manager, Akamai, Google Tag Manager, HSTS, Java and jQuery. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for appdynamics.com in the checks that ran.
appdynamics.com was registered on 12 Jul 2001 via MarkMonitor Inc.. The registry returned 6 status values and 4 nameservers from https://rdap.verisign.com/com/v1/domain/appdynamics.com.
| Registered | since 12 Jul 2001 |
|---|---|
| Created | 12 July 2001 |
| Updated | 10 June 2026 |
| Expires | 12 July 2027 |
| Registrar | MarkMonitor Inc. |
| Status | client delete prohibited, client transfer prohibited, client update prohibited, server delete prohibited, server transfer prohibited, server update prohibited |
| Nameservers | ns-1486.awsdns-57.org, ns-1681.awsdns-18.co.uk, ns-780.awsdns-33.net, ns-82.awsdns-10.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/appdynamics.com |
appdynamics.com carries the status "client delete prohibited". The registrar has asked the registry to refuse a delete. This is an EPP status on the domain object. It does not say the website is safe, and it does not name the person who registered it.
appdynamics.com carries the status "client transfer prohibited". The registrar has asked the registry to refuse a transfer to another registrar. The status is a lock on the domain object. It is not evidence about the content of the site.
appdynamics.com carries the status "client update prohibited". The registrar has asked the registry to refuse updates to the domain object. Contact and nameserver changes wait until the lock is lifted by the registrar of record.
appdynamics.com carries the status "server delete prohibited". The registry itself is refusing deletes. This lock is not one the registrar can clear alone.
appdynamics.com carries the status "server transfer prohibited". The registry itself is refusing transfers. The name stays at the current registrar while the status remains.
appdynamics.com carries the status "server update prohibited". The registry itself is refusing updates to the domain object.
Nameserver ns-1486.awsdns-57.org is published for appdynamics.com in the registration record from https://rdap.verisign.com/com/v1/domain/appdynamics.com.
Nameserver ns-1681.awsdns-18.co.uk is published for appdynamics.com in the registration record from https://rdap.verisign.com/com/v1/domain/appdynamics.com.
Nameserver ns-780.awsdns-33.net is published for appdynamics.com in the registration record from https://rdap.verisign.com/com/v1/domain/appdynamics.com.
Nameserver ns-82.awsdns-10.com is published for appdynamics.com in the registration record from https://rdap.verisign.com/com/v1/domain/appdynamics.com.
appdynamics.com has 1 address record, 3 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 204.107.141.160 |
|---|---|
| AAAA | — |
| NS | ns-1486.awsdns-57.org, ns-1681.awsdns-18.co.uk, ns-780.awsdns-33.net, ns-82.awsdns-10.com |
| MX | alln-mx-01.cisco.com (10), rcdn-mx-01.cisco.com (20), aer-mx-01.cisco.com (30) |
| SPF | absent |
| DMARC | present |
| CAA | iodef mailto:[email protected], issue digicert.com, issue pki.goog |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The DMARC text record at _dmarc.appdynamics.com is "v=DMARC1;p=reject;rua=mailto:[email protected],mailto:[email protected];ruf=mailto:[email protected];pct=100;".
IPv4 address 204.107.141.160 answers for appdynamics.com at resolver 1.1.1.1:53.
Mail exchanger alln-mx-01.cisco.com has preference 10.
Mail exchanger rcdn-mx-01.cisco.com has preference 20.
Mail exchanger aer-mx-01.cisco.com has preference 30.
appdynamics.com is placed in San Francisco (South Beach), United States by the local geolocation database (db-ip).
| Address | 204.107.141.160 |
|---|---|
| Country | United States |
| City | San Francisco (South Beach) |
| Source | db-ip |
The certificate for appdynamics.com is valid, with 19 days left and 42 subject alternative names. Source: tls:443.
| Issuer | DigiCert Global G2 TLS RSA SHA256 2020 CA1 |
|---|---|
| Subject | splunk.org |
| Valid from | 5 May 2026 |
| Valid until | 19 November 2026 |
| Days left | 19 |
| SAN count | 42 |
| Protocol | TLS 1.2 |
| Source | tls:443 |
Subject alternative names: appdynamics.com, de-de.splunk.com, de.splunk.com, en-us.splunk.com, es-es.splunk.com, es.splunk.com, fr-fr.splunk.com, fr.splunk.com, it-it.splunk.com, it.splunk.com, ja-jp.splunk.com, ja.splunk.com, ko-kr.splunk.com, ko.splunk.com, pt-pt.splunk.com, pt.splunk.com, ru-ru.splunk.com, ru.splunk.com, splunk.cn, splunk.de, splunk.fr, splunk.hk, splunk.jp, splunk.org, splunk.tw, splunk.xn--fiqs8s, www.appdynamics.com, www.splunk.cn, www.splunk.de, www.splunk.fr, www.splunk.hk, www.splunk.jp, www.splunk.org, www.splunk.tw, www.splunk.xn--fiqs8s, zh-cn.splunk.com, zh-hans.splunk.com, zh-hk.splunk.com, zh-mo.splunk.com, zh-my.splunk.com, zh-sg.splunk.com, zh-tw.splunk.com.
Tech detection checked the fetched homepage and named 6 products. Source: wappalyzergo.
Adobe Experience Manager is filed under CMS.
Akamai is filed under CDN.
Google Tag Manager is filed under Tag managers.
HSTS is filed under Security.
Java is filed under Programming languages.
jQuery is filed under JavaScript libraries.
The homepage returned HTTP 200 in 149 ms. The target title is 61 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 149 ms |
| Title length | 61 no |
| Quoted title | "AppDynamics joins the Splunk Observability portfolio | Splunk" |
| Meta description | "Get unified observability across any environment, any stack. Ensure resilience of digital systems, identify problems proactively, find root causes, and resolve them fast." yes |
| H1 count | 1 |
| HSTS | yes yes |
| CSP | yes |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | INDEX,FOLLOW |
| Canonical | https://www.splunk.com/en_us/appdynamics-joins-splunk.html |
| Language | en |
| Links | 165 |
| Images | 79 |
| Favicon | yes |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Family DNS for appdynamics.com is clear, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | clear |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | yes |
| CSP | yes |
Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.
Availability 25 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 20 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 10 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 15 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.
Safety lists 15 of 15. Points only when the checks ran and came back clean. Unknown is not clean.
Domain age 5 of 5. Five points at one year, two points at 30 days.
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
appdynamics.com is placed in San Francisco (South Beach), United States.
appdynamics.com expires on 12 July 2027 according to https://rdap.verisign.com/com/v1/domain/appdynamics.com.
The registry did not return a person or a company for appdynamics.com. RDAP often redacts the registrant. The registrar on file is MarkMonitor Inc..
No other indexable reports share this TLD, host, or registrar yet.
Ask for a correction or for the report to be removed from search. Public DNS facts stay on the page. An optional badge is not inserted for you.
The sentences under each heading are filled from the latest snapshot. If a collector had nothing to say, that sentence is left out. The target site's own title and meta description, when shown, are quoted as measurements. They are not this page's title. Change history only lists a difference between two snapshots, so the first check starts the clock and later edits are the history. A malware blocklist is the only reason the homepage body is skipped. That fact stays on the report. It does not by itself drop the page from the sitemap or from related-report links.