Website profiles · Technology insights · Alternatives

sites.utexas.edu

Genomics and Epigenetics of Polyploidy and Heterosis

No paid content found
Visit website
Profile views 13 Outbound visits 4 Normal
The Chen Lab – Genomics and Epigenetics of Polyploidy and Heterosis Full homepage screenshot

At a glance

Category
Education & Learning
Language
English
Paid-content signal
No paid content foundObserved
Registered
Unknown
Hosting
University of Texas at AustinInferred
HTTPS certificate trusted
PassedObserved
Last updated

Website review

This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.

What is The Chen Lab?

The Chen Lab is a research group at the University of Texas at Austin studying the genomics and epigenetics of polyploidy and heterosis — that is, how whole-genome duplication and hybrid vigor work at the DNA and gene-regulation level. Its site is hosted on the university's blog service at The Chen Lab.

H3: What you'll actually find there The page evidence shows the site's visible content is dominated by release notes for the university's WordPress platform — version numbers, dependency updates (WordPress core, Akismet, Yoast SEO, TablePress, Really Simple SSL), plugin additions and removals, and occasional hotfixes blocking bad IP ranges. In other words, the public-facing material captured here is site maintenance logging, not lab science.

Who it's for

  • Lab members and collaborators looking for publications, people, or project descriptions — though those sections aren't reflected in the captured content.
  • Prospective students or postdocs evaluating whether the lab's focus on polyploidy and heterosis matches their interests.
  • Anyone who lands here expecting research output and instead finds changelog entries; that mismatch is worth knowing before you spend time scrolling.

H3: A practical next step If you want the science, look for the lab's own pages rather than the release log: check for a Publications or Research tab, or search the lab name alongside "polyploidy" or "heterosis" to find papers and profiles. If you're instead trying to understand the UT Austin blog platform itself, the release notes are genuinely useful — they show how often the platform updates and which plugins it standardizes on.

What polyploidy and heterosis research does the Chen Lab conduct?

The Chen Lab at the University of Texas at Austin studies the genomics and epigenetics of polyploidy and heterosis — two related phenomena in plant genetics. Polyploidy is the condition of having more than two complete sets of chromosomes, common in crops and flowering plants; heterosis, or hybrid vigor, is the tendency of crosses to outperform their parents. The lab's focus sits at the intersection: how genome duplication and hybridization reshape gene regulation, and what that means for plant performance.

The public-facing site, The Chen Lab, functions mainly as a lab homepage and news log rather than a deep publication archive. Its recent posts are release notes for the university's WordPress platform (dependency updates, plugin version bumps, security hotfixes), so anyone looking for protocols, datasets or papers will need to look elsewhere — typically the lab's publication list or the corresponding author's faculty page.

Who this is for: graduate students and postdocs evaluating labs, collaborators in plant genomics, and science writers seeking a quick orientation to the lab's themes.

Practical next step: if you are considering the lab, read two or three recent papers on polyploid epigenetics and hybrid vigor, then email the principal investigator with a specific question about methods — for example, how the group handles allele-specific expression in a newly formed polyploid. That is a more useful first contact than a generic inquiry.

Can I join the Chen Lab as a graduate student or researcher?

The page you shared does not contain graduate admissions or researcher hiring information. The Chen Lab site at The Chen Lab – Genomics and Epigenetics of Polyploidy and Heterosis currently shows a news/release log for the lab's WordPress platform (dependency updates, plugin versions, and security hotfixes), not a "Join Us" or openings page. So there is no stated answer on this page about whether you can join as a graduate student or researcher.

What to do next

Contact the lab directly and ask about current openings. In your email, include:

  • Your current stage (incoming PhD applicant, current UT student, postdoc, visiting researcher)
  • Research interests tied to polyploidy, heterosis, or epigenetics
  • Your CV and a short statement of what you'd like to work on
  • Whether you are asking about a funded position or an unpaid/visiting arrangement

How to decide where to apply

If you are applying to UT Austin, check the relevant graduate program's admissions page and application deadlines rather than the lab website alone. For UT Austin, the main entry point is The University of Texas at Austin. For program-specific requirements, look at the department that hosts the lab (for example, integrative biology or molecular biosciences) and follow its application instructions.

If you are already a student or researcher elsewhere, a direct email to the lab's principal investigator is usually the fastest route. Ask specifically whether they anticipate openings in the next admissions cycle, and mention any relevant skills (genomics, bioinformatics, plant or computational biology).

A practical example

A prospective PhD student might email the PI in early autumn, before the program deadline, with a one-page CV and a paragraph explaining why the lab's work on polyploidy and heterosis matches their interests. That timing gives the lab a chance to respond before applications are reviewed, and it lets you tailor your application to the lab's current direction.

If you need a definitive answer, the lab's contact page or the hosting department's faculty profile is the right place to look — not the release notes shown here.

What publications and findings has the Chen Lab released?

The page you supplied does not list the Chen Lab's publications or research findings. Its headings and excerpts are release notes for a WordPress-based university blog service—version numbers, dependency updates, plugin changes—not papers, preprints or experimental results. The lab name appears in the site title, but the visible content is software changelog material.

If you need the lab's actual science, go to its publication list or lab website rather than this feed. A practical next step: check the lab's official page at the host institution, or search a bibliographic database for the principal investigator's name plus terms like "polyploidy," "heterosis" and "epigenetics." For broader context on the university, see University of Texas at Austin.

If you were actually looking for the blog service's release history, the same page does show entries such as Release 1.29.1, 1.29.0, 1.26.0, 1.25.0 and 1.24.0, with dependency and plugin updates. That is a different question from the one asked.

How can I collaborate with or contact the Chen Lab?

The Chen Lab page you are looking at is a University of Texas at Austin lab site hosted on the university's blog service, and its visible content is a running changelog of platform releases rather than a contact or collaboration page. That means the practical answer is: don't look for contact details in the release notes — go to the lab's main site or the UT Austin directory instead.

H3. What the page actually shows The entries are dated release notes (versions 1.14.0 through 1.29.1) listing dependency updates, plugin version bumps, hotfixes blocking IP ranges, and occasional feature additions such as "Beyond Multisite" and a beta "UT Block Theme." This is infrastructure news for the site, not lab news.

A realistic path to the lab

  • Start with the lab's own homepage on the same host: The Chen Lab — look for a "People," "Contact," or "Join Us" section.
  • Check the lab's departmental home in the UT Austin College of Natural Sciences, where faculty profiles usually list an office, phone number, and email.
  • For prospective students or postdocs, use the university's graduate program pages for the relevant department; applications typically go through the program, not directly to the lab.
  • For collaboration inquiries, write a short email stating your institution, your data or system of interest, and what you propose; attach or link a one-page summary.

How to choose your approach

Goal Best first move
Join the lab as a student or postdoc Department graduate program or lab "Join Us" page
Research collaboration Direct email to the PI with a specific proposal
Media or general questions UT Austin department communications office
Reuse of data or code Check the lab site for a publications or resources page first

If you cannot find a direct address, contact the department's main office and ask them to forward your message to the Chen Lab.

What genomics methods and tools does the Chen Lab use in its studies?

The Chen Lab page you linked is a lab site on the University of Texas at Austin blog service, and its visible content is mostly WordPress release notes rather than a methods page. So the honest answer is: the supplied page does not list the lab's genomics methods or tools. What it does show is the lab's web publishing stack.

What the page evidence actually shows

The excerpts are changelog entries (releases 1.14.0 through 1.29.1) covering dependency updates and a few feature changes. Plugins named include Akismet, Google Analytics for WordPress, Really Simple SSL, TablePress, Yoast SEO, WP Mail SMTP, Redirection, Simple Social Icons, WP Accessibility, and wp-saml-auth. One release notes "Beyond Multisite," another adds a "UT Block Theme (beta)," and one removes AgentPress Pro. None of that describes sequencing, genotyping, or analysis pipelines.

How to find the methods

Genomics labs usually publish methods in peer-reviewed papers, not on the lab homepage. Practical steps:

  • Look for a "Publications," "Research," or "People" section on the lab site; the homepage changelog is not the place to look.
  • Read the Methods sections of recent papers from the lab, which name specific assays and software.
  • Check the lab's GitHub or data-availability statements for pipelines and parameter settings.
  • Email the corresponding author or a current graduate student for protocol details and reagent choices.

What to expect from a polyploidy and heterosis lab

Given the stated focus, typical approaches in this field include whole-genome and transcriptome sequencing, small RNA and methylation assays (for example bisulfite or reduced-representation methods), chromatin accessibility assays, and comparative analyses across parental and hybrid or polyploid lines. These are general expectations for the field, not confirmed features of this lab.

A concrete example

A reader comparing labs for a rotation might want to know whether a lab does its own library prep or sends samples out, and whether it favors short-read resequencing or long-read assembly. Those details determine your day-to-day bench work. You will usually find them in recent papers or by asking directly, not in a site changelog.

For a broader view of the research environment, see The University of Texas at Austin.

Related questions

More questions →
What the Release 1.x.x Posts on The Chen Lab Site Mean

The "Release 1.x.x" posts on The Chen Lab site at sites.utexas.edu are changelog entries for the University Blog Service platform itself, not research output from the lab. Each entry records a version number, a date, and the type of change made — most often dependency updates, plugin version bumps, server configuration changes, or UI adjustments. If you arrived looking for genomics or epigenetics work, these posts are not that; they are the maintenance log of the WordPress-based hosting platform the site runs on.

Why platform release notes appear on a lab site

The Chen Lab site is hosted on the University of Texas at Austin's University Blog Service, a shared WordPress environment. Because the platform is updated centrally, its release notes are published into the same blog stream that carries the lab's own content. That is why a page about polyploidy and heterosis also shows entries like "Release 1.29.1 Dependency Update."

The practical consequence: these posts tell you about the infrastructure, not the science. They are useful if you administer a site on the same service, or if you are trying to date a change in how the site behaves.

How to read a single release entry

Each entry follows a consistent pattern:

Element What it tells you Example from the log
Version number Which platform build the change belongs to Release 1.29.0
Date When the change shipped September 17, 2026
Change type The category of work done "Dependency updates," "Changed," "Added," "Removed"
Detail list Specific components and version ranges wordpress 7.0.4 → 7.1.0

When a detail list is present, it names each component and shows the before-and-after version, for example akismet: 5.7 → 5.7.2 or really-simple-ssl: 9.7.0 → 9.8.0. That arrow format means the component was upgraded from the left version to the right one.

The change categories you will see

  • Dependency updates — the most common entry. Bundled plugins and the WordPress core are bumped to newer versions.
  • Added — a new capability or component. Release 1.20.0 added "Beyond Multisite"; Release 1.14.0 added the "UT Block Theme (beta)."
  • Changed — modifications that are not purely version bumps, such as server configuration or UI changes (Release 1.23.0).
  • Removed — a component dropped from the platform. Release 1.15.0 removed AgentPress Pro.
  • Hotfix — an urgent, narrow release. Release 1.22.1 was a "hotfix to block a problematic IP address," and Release 1.18.1 "blocks an IP range used by bad actors."

What the version numbers do and do not tell you

The numbering is sequential and platform-wide: 1.14.0, 1.15.0, 1.17.0, 1.18.0, and so on, in date order. A jump in the middle number (the minor version) generally accompanies added features or broader changes, while the third number (the patch) tends to cover smaller fixes and dependency bumps.

Two cautions when interpreting the log:

  • Not every number appears. The visible sequence skips versions such as 1.16.x, so the published list is not a complete history.
  • A version number is not a security rating. A hotfix entry tells you a specific problem was addressed, but the log does not describe severity or scope beyond the short note given.

When these posts are actually useful to you

  • You run a site on the same service. The dependency lists show which plugin versions the platform has moved to, which helps you anticipate compatibility.
  • You are troubleshooting a behavior change. If something on the site shifted around a given date, the matching release entry may name the cause — for instance a UI change or a plugin upgrade.
  • You need to cite platform state at a point in time. The dated entries give you a verifiable record of what version was live when.

If your interest is the lab's research rather than the hosting platform, skip the "Filed Under: News" release posts and look for the lab's own pages and publications instead.

What platform powers The Chen Lab site on sites.utexas.edu?

The Chen Lab site runs on WordPress, hosted through the University of Texas at Austin's University Blog Service. The release notes published on the site are not research updates from the lab — they are platform maintenance logs for that WordPress instance, covering dependency updates, plugin version bumps, and occasional security fixes.

How the platform is structured

The site sits on sites.utexas.edu, a subdomain the university uses for its centrally managed blog service. That service provides the hosting, the WordPress core, and a shared set of plugins and themes. Individual sites like The Chen Lab's get their own content and configuration on top of that shared base.

The release notes confirm this arrangement in several ways:

  • Entries are tagged "Filed Under: News" and titled with version numbers (Release 1.29.1, Release 1.29.0, and so on), which is typical of a managed platform publishing changelogs rather than a single lab's own software.
  • Updates list WordPress core alongside third-party plugins, meaning the platform maintainers control both.
  • Some releases mention server configuration and UI changes, which a lab would not normally manage for its own research site.

What the release notes actually contain

The changelog entries fall into a few recurring categories:

Category Examples from the notes
Dependency updates Version bumps for akismet, really-simple-ssl, tablepress, wordpress-seo, wp-mail-smtp
Feature additions "Beyond Multisite," "UT Block Theme (beta)"
Removals AgentPress Pro removed in Release 1.15.0
Security / hotfixes Release 1.22.1 blocked a problematic IP address; Release 1.18.1 blocked an IP range used by bad actors

The plugin list is a useful signal of what the platform supports: SEO (wordpress-seo), analytics (google-analytics-for-wordpress), SSL (really-simple-ssl), tables (tablepress), email (wp-mail-smtp), accessibility (wp-accessibility), and SSO authentication (wp-saml-auth). The presence of wp-saml-auth points to university single sign-on, consistent with a centrally administered service.

Why there are so many version releases

The cadence — roughly every two to four weeks across 2025 and 2026 — reflects an automated maintenance pipeline rather than manual one-off edits. Several entries say so directly:

  • Release 1.26.0 is described as an "Automated plugin update run."
  • Many releases are labeled simply "Dependency updates" or "Changed."

This means the version numbers track the platform's update cycle, not the lab's research output. A reader landing on the release notes page should read them as infrastructure history, not scientific content.

What this means if you are looking for the lab's work

If your goal is the Chen Lab's genomics and epigenetics research on polyploidy and heterosis, the release notes are the wrong section. They document the WordPress platform that hosts the site. The lab's actual content — publications, people, projects — lives elsewhere on the same domain.

If your goal is to understand the hosting setup, the notes are a reliable record: WordPress core, a fixed plugin set, SAML-based login, and periodic security blocks, all managed by UT Austin's University Blog Service.

What kinds of updates are listed in The Chen Lab site's release notes?

The release notes on The Chen Lab site (sites.utexas.edu) are maintenance logs for a WordPress-based university blog platform, and they list four recurring categories of changes: WordPress core version upgrades, third-party plugin updates, feature and theme additions or removals, and security-related changes such as blocking malicious IP ranges. If you are trying to understand what a specific release number changed, the entry usually names the affected component and, for plugins, shows the version transition.

WordPress core version upgrades

The most consequential item in any release is a change to the WordPress core version, because it affects the whole platform rather than a single feature.

  • Release 1.26.0 (August 27, 2026) records wordpress 7.0.4 → 7.1.0 as part of an automated plugin update run.
  • Core upgrades appear less often than plugin updates, so when one shows up it is worth reading the full entry rather than skimming.

If you administer a site on this platform, a core version jump is the item most likely to change behavior you rely on, so check it before assuming a plugin is responsible for something breaking.

Third-party plugin updates

Most release entries are plugin version bumps. The notes list the plugin name and the "from → to" versions, which lets you tell a patch-level change from a larger jump.

Plugin Example transition Release
Akismet 5.7 → 5.7.2 1.26.0
Google Analytics for WordPress 11.1.2 → 11.1.3 1.26.0
Really Simple SSL 9.7.0 → 9.8.0 1.26.0
TablePress 3.3.3 → 3.3.4 1.26.0
Yoast SEO (wordpress-seo) 28.2 → 28.3 1.26.0
wp-saml-auth 2.3.1 → 2.3.2 1.21.1

Earlier releases follow the same pattern with different plugins, including add-to-any, genesis-simple-hooks, wp-accessibility, wp-mail-smtp, redirection, google-calendar-events, simple-social-icons, team-members, wp-native-php-sessions, ns-cloner-site-copier, and wordpress-importer.

Two things are worth noting about how these are presented:

  • Patch-level bumps (for example 5.7 → 5.7.2) are typically bug or compatibility fixes and rarely change how a plugin behaves.
  • Larger jumps (for example simple-social-icons 3.2.5 → 4.0.0) can include breaking changes, so a major-version increase is the one to look at more carefully.

Feature, theme, and plugin additions or removals

Some releases are not just version bumps. These entries tell you when something new became available or when an option disappeared.

  • Release 1.14.0 (December 4, 2025) added the UT Block Theme (beta).
  • Release 1.20.0 (April 30, 2026) added Beyond Multisite.
  • Release 1.15.0 (January 8, 2026) removed AgentPress Pro.

If a theme or plugin you were using stops appearing, a removal entry like the AgentPress Pro one is the likely explanation. Beta additions such as the UT Block Theme are flagged as beta, which signals they are still subject to change.

Security-related changes

Security items appear as their own releases, separate from routine dependency updates.

  • Release 1.18.1 (March 18, 2026) is described as a hotfix that "blocks an IP range used by bad actors."
  • Release 1.22.1 (July 16, 2026) is a hotfix to block a problematic IP address.

These are the entries to read if legitimate traffic or access suddenly stops working, since an IP block can affect users as well as attackers.

How to read a release entry

  1. Check the release number and date first. Higher numbers are newer, and the date confirms the sequence.
  2. Look for a core version change. If wordpress appears with a version transition, that is the headline change.
  3. Scan the plugin list for major-version jumps. A move like 3.x → 4.x deserves more attention than a patch bump.
  4. Note any Added or Removed lines. These tell you about features or themes appearing or disappearing, not just version numbers.
  5. Treat security hotfixes separately. A block on an IP range or address is a deliberate action, not a routine update.

The release notes themselves do not explain why a change was made or what it affects on your specific site; they record what changed and when. For anything beyond that, the entry is a starting point rather than a full explanation.

What is The Chen Lab website at sites.utexas.edu?

sites.utexas.edu is the University Blog Service hosted by the University of Texas at Austin, and The Chen Lab site on that domain is a lab website for a research group working on the genomics and epigenetics of polyploidy and heterosis. If you are trying to identify who runs the site, what it covers, or whether it is an official university resource, the short answer is: it is a UT Austin-hosted lab site, and the page evidence available here shows it functioning mainly as a news and release-log page rather than a general lab directory.

Who operates the site

The site sits under sites.utexas.edu, which the source identifies as the University Blog Service of the University of Texas at Austin. That means the hosting and platform belong to UT Austin, while the individual site belongs to The Chen Lab.

The site name given in the source is "The Chen Lab – Genomics and Epigenetics of Polyploidy and Heterosis." That tells you the research focus directly: polyploidy (having more than two sets of chromosomes) and heterosis (hybrid vigor), studied through genomic and epigenomic methods.

What the page actually contains

The visible content is not a lab overview, a people page, or a publications list. It is a chronological feed of release notes, each filed under "News." The headings and excerpt show entries such as:

  • Release 1.29.1 – Dependency Update (September 18, 2026)
  • Release 1.29.0 – Changed, Dependency updates (September 17, 2026)
  • Release 1.26.0 – Automated plugin update run (August 27, 2026)
  • Release 1.25.0 – Changed, Dependency updates (August 13, 2026)
  • Release 1.24.0 – Dependency Updates (July 16, 2026)

The entries describe platform maintenance rather than research. For example, Release 1.26.0 lists plugin version changes:

Plugin From To
wordpress 7.0.4 7.1.0
akismet 5.7 5.7.2
google-analytics-for-wordpress 11.1.2 11.1.3
really-simple-ssl 9.7.0 9.8.0
tablepress 3.3.3 3.3.4
wordpress-seo 28.2 28.3

Other entries follow the same pattern: dependency updates, a hotfix blocking a problematic IP address or IP range, server configuration changes, UI changes, and occasional feature additions such as "Beyond Multisite" (Release 1.20.0) and "UT Block Theme (beta)" (Release 1.14.0). One entry, Release 1.15.0, records a removal (AgentPress Pro) alongside dependency updates.

What this tells you about the site

Two things follow from that content.

First, the site is actively maintained. The release log runs from at least December 2025 through September 2026, with entries appearing roughly every two to four weeks. Releases are versioned (1.14.0, 1.15.0, 1.17.0, 1.18.0, 1.19.0, 1.20.0, 1.21.0, 1.22.0, 1.23.0, 1.24.0, 1.25.0, 1.26.0, 1.29.0, 1.29.1), and hotfixes get their own point releases, such as 1.18.1 and 1.22.1.

Second, the page you are looking at is the site's news stream, not its research content. If your goal is to learn about the lab's science, this particular page will not give you that. If your goal is to track what changed on the site or confirm it is a live, maintained UT Austin property, the release log is exactly the right place.

Practical points to keep in mind

  • The domain is shared. sites.utexas.edu hosts many UT Austin blogs and lab sites, so a URL on this domain indicates university hosting, not necessarily a single central site.
  • The lab name and research topic come from the site title, not from the release notes. The release notes themselves are platform-level, not lab-level.
  • Dates in the source run into 2026, so treat the log as the site's own record of its update history rather than a fixed snapshot.
  • No pricing, login, or access-restriction information appears in the available evidence, so nothing here should be read as indicating the site is free, open, or gated.

If you need the lab's research output, look for its publications or people pages elsewhere on the same site. If you need to know whether the site is current and maintained, the release feed answers that directly.

Website Overview

The available information shows a mix of normal operation and configuration gaps. Depending on how the website is used, these gaps may affect secure access or the consistency of its public presentation.

Domain and Registration

Unknown

DNS and Email

Nameservers are provided by utexas.edu, indicating managed DNS hosting. MX records point to the utexas.edu email service. CAA records restrict which certificate authorities are authorized to issue certificates. No CNAME was found; the observed records resolve directly to addresses. SPF and DMARC are configured. DKIM status is unknown.

TLS and Certificates

The certificate includes the organization field The University of Texas at Austin. The certificate uses an RSA 2048-bit public key, offering broad client compatibility. The server supplied a complete certificate chain. The certificate is valid for about 198 days in total, with 127 days remaining. The certificate covers the main domain and its usual www hostname.

HTTP and Browser Security

X-Powered-By exposes backend information: PHP/8.3.33. The response lacks these common security headers: CSP, Referrer-Policy, Permissions-Policy, clickjacking protection. No obvious internal addresses or debug information were found in the headers. The Server header identifies Apache without an exact version. No explicit CDN or WAF marker was found in the response headers.

Technology Stack Analysis

The public page identifies WordPress, jQuery, Apache, PHP without precise versions, leaving fewer clues for version-specific scanning.

Search and Social Sharing

No Open Graph metadata was detected, so social previews may depend on platform inference. The title has 55 characters, within a common display range. A meta description is present, with 29 characters. No Generator meta tag is publicly exposed. A viewport declaration is present, providing a basis for mobile layout.

Hosting and Email

DNSutexas.edu
HostingUniversity of Texas at Austin
Emailutexas.edu
Approximate IP geolocation (inferred; a CDN or proxy may differ from the origin server) United States flagAustin, Texas, United States Inferred 146.6.219.59

Registration details

RDAP / WHOIS

Unknown

DNS records

DNS

TypeNameValueTTLPriority
Asites.utexas.edu146.6.219.59600—
MXutexas.eduinbound.mail.utexas.edu60010
NSutexas.educhisos.ots.utexas.edu600—
NSutexas.eduglass.its.utexas.edu600—
NSutexas.edumarianas.its.utexas.edu600—
TXTutexas.edu975172592F8531BEAFC17ADF471CC1A9600—
TXTutexas.eduMS=ms80175920600—
TXTutexas.edu_globalsign-domain-verification=AmgTovmK8NOFj6S848ssOdeA5Bd3_iMnjIqO-PlLlh600—
TXTutexas.edua8LYUGVubXGV5T3o+qN2/w==600—
TXTutexas.educoursera-domain-verification=1JEi4zxbmn5JIG6hxViDbViDgsxv7bwl5vIaOPCWMd26Tlw2PoFUBLKkrT5hm3dg600—
TXTutexas.edudocusign=18aab780-e4ba-4f25-bd82-4fd000223e23600—
TXTutexas.edudocusign=70ecfb87-f7cc-4f07-8b5b-5f3fb9627fd2600—
TXTutexas.edue2ma-verification=0r7eb600—
TXTutexas.edue2ma-verification=77veb600—
TXTutexas.edufastly-domain-delegation-FeZhCxeLqx-311421-2020-11-11600—
TXTutexas.edufastly-domain-delegation-aX3Cv1R0n0jutdbKIYiu-08192020600—
TXTutexas.eduopenai-domain-verification=dv-V9eTgezTwIm82UoEoJwtJrWY600—
TXTutexas.edupuybXBnQlfP7zU5AkBfAOxyd7AtVbW0V7le/PLDTDFjAn0vCwsku+yphyGvHnsOPRDPoOCIvSWMpKbCVfqpsZw==600—
TXTutexas.eduv=spf1 include:_spf-m365-gmail.mail.utexas.edu include:utexas-edu.spf.smtp25.com include:_spf.qualtrics.com -all600—
CAAutexas.edu0 contactemail "[email protected]"600—
DMARCcommon._dmarc.austin.utexas.eduv=DMARC1; p=none; fo=1; rua=mailto:[email protected]; ruf=mailto:[email protected];208—

TLS and certificates

TLS / SSL

AssessmentNormal configuration
Supported protocolsTLSv1.2、TLSv1.3
Negotiated protocolTLSv1.3
Certificate subjectsites.utexas.edu
IssuerInCommon, LLC
Valid until2027-01-28T23:59 · Remaining when checked: 127 days
Verification detailsCertificate trust: Passed · Hostname match: Passed

HTTP response headers

HTTP

HeaderValue
content-typetext/html; charset=UTF-8
cache-controlmax-age=1800
serverApache
strict-transport-securitymax-age=31536000
x-content-type-optionsnosniff

Identified technologies

WordPressjQueryApachePHP

Pages, Search and Sharing

Meta descriptionUniversity of Texas at Austin
Canonical URLhttps://sites.utexas.edu/
LanguageEnglish (default)
Twitter CardNot detected

Unknown

All bots 0 allowed · 0 disallowed
  • IntervalCrawl delay 60 seconds
twitterbot 0 allowed · 0 disallowed
  • IntervalCrawl delay 0 seconds
mozilla/4.0 (compatible; ics) 0 allowed · 1 disallowed
  • Disallow/
monsidobot 0 allowed · 0 disallowed
  • IntervalCrawl delay 60 seconds

Recent Updates

  • Website profile

User reviews (0)

  • No reviews yet.